Yes, I did this but there is absolutely no indication in ptool that anything has actually happened. So I don't know if the new firmware settings have been loaded or not and I'm not willing to load unknown firmware into my GH1 in the off chance that it is actually OK. So I'll maybve go down the manual route and type each setting in individually.
The 'perfect' project
- Thread starter MarekV
- Start date
Yes, I did this but there is absolutely no indication in ptool that anything has actually happened. So I don't know if the new firmware settings have been loaded or not and I'm not willing to load unknown firmware into my GH1 in the off chance that it is actually OK. So I'll maybve go down the manual route and type each setting in individually.
This is not true. A small "settings loaded" window is displayed for a second. More importantly, settings and values are loaded - checkboxes are checked and values are populated.
It's definitely a wise precaution to manually verify every PTool patch setting after activating a downloaded settings file. Each of these settings files activates or deactivates every single patch in PTool, not simply the patches that are checked.
There is currently no way for the author of a settings file to mark any individual setting as unchanged. As a result, each settings file will revise all of the patches, both MJPEG and AVCHD, and there is no way to create a settings file that restricts itself to altering a subset of the complete list of available patches.
You are right. After many tries, I have managed to get the settings loaded - trust me, they didn't load before, there were no ticks against any boxes, and no increase in the listed video bitrates. The Version Increment and Prevent Version Compare still aren't ticked, so I've ticked them both and have entered a 1 in the version increment box ( this changes the firmware from 0x0132 to 0x0133). I've also ticked the 3rd Party Battery box as this doesn't appear to have been checked either. The 30m removal was checked so have left that alone. And I have saved out the file as GH1__133.bin - hopefully that will do it. I am off work tomorrw so will try it out and I'll let you know what happens.
I'm not sure I follow you here. Setting file only stores changes. For example, the following file:
Code:
[Information]
Comment=Test 1-2
SD_Card=Any
Camera=GH1 v1.32
[Settings]
Prevent version compare=CheckedUnfortunately, that's not all it will do. In addition to activating its checked patches, each settings file will force all of its unchecked patches to be deactivated as well.
Oh, so in "there is currently no way for the author of a settings file to mark any individual setting as unchanged." by unchanged you mean unchanged from current user selection?
Yes, that's correct. As a result, there is no way I can supply a settings file for my 35Mbps MJPEG In-Camera Playback patch that only sets the MJPEG patches in PTools 3.40d. If you apply this settings file as is, it will deactivate any AVCHD patches you may have checked in advance, and you will need to go back and manually check them again by hand.
Link to 35Mbps MJPEG In-Camera Playback patch:
http://dvxuser.com/V6/showpost.php?p=2039780&postcount=5
Last edited:
Well, this is a "hack project" after all and we should not attempt to remove all the fun
The first lesson a Gx1 hackers must learn is how to copy-paste information from two text files into one. If someone can't do that perhaps they should not be hacking their Gx1 
OK, I promised I would report back with my findings. I was able to patch the firmware without any problems - original fw was 1.2, now it reads 0.0 - so I went out filming on the west coast of Ireland (Sligo) to see how it would cope. No problems with lock-ups on either recording or playback. A variety of different shots were filmed including lakeside, countryside, a waterfall and even W.B. Yates grave - mostly taken with a tripod and using the kit lens at various focal lengths. I also use a polariser to deepen skys & give me almost 2 stops of ND, and a half black promist to take the hard digital edge of the images.
When I got home, I played back both in camera onto my Panasonic 32" LCD 720p TV and on my Dell PC with a 22" 1080p LCD monitor. Results were basically the same. There is a dramatic improvement compared to the original Panasonic firmware, but it can still be caught out if there is a lot of movement in part of the frame - like a river or reeds blowing in the wind - this was enough to mud out both foreground and background details (although the moving subject seemed to be rendered OK).
So although this "lower" high bitrate hack seems perfectly safe to use with Class 6 cards, it probably isn't high enough to eradicate the mud issue in more complicated scenes. Maybe something around the 30Mbps would do it - but that's for another day.
When I got home, I played back both in camera onto my Panasonic 32" LCD 720p TV and on my Dell PC with a 22" 1080p LCD monitor. Results were basically the same. There is a dramatic improvement compared to the original Panasonic firmware, but it can still be caught out if there is a lot of movement in part of the frame - like a river or reeds blowing in the wind - this was enough to mud out both foreground and background details (although the moving subject seemed to be rendered OK).
So although this "lower" high bitrate hack seems perfectly safe to use with Class 6 cards, it probably isn't high enough to eradicate the mud issue in more complicated scenes. Maybe something around the 30Mbps would do it - but that's for another day.
Well, this is a "hack project" after all and we should not attempt to remove all the fun
This is poited to me? I think yes... so "thank you" dude .. Thank you!!!!?? @
Forum warrior tip #1: to see who the post is addressed to check for presence of quote block, which usually starts with "Originally posted by [name]" sentence. If there is no quote block, the post is probably addressed to the whole forum.
AVCHD for 1080 - MPEG 422 for 720
AVCHD for 1080 - MPEG 422 for 720
MarekV,
Thanks for your work sorting out reliability issues.
I am trying to find a set up that gets the most out of the GH-1 - least mud / near perfect reliability.
I am thinking that shooting with the "C" settings in AVCHD for 1080 24P/60i and using your settings for MJPEG 720 30P may be the best overall solution.
720 60P would be unavailable - but the other resolutions would be as sharp as possible consistent with reliability.
AVCHD for 1080 - MPEG 422 for 720
MarekV,
Thanks for your work sorting out reliability issues.
I am trying to find a set up that gets the most out of the GH-1 - least mud / near perfect reliability.
I am thinking that shooting with the "C" settings in AVCHD for 1080 24P/60i and using your settings for MJPEG 720 30P may be the best overall solution.
720 60P would be unavailable - but the other resolutions would be as sharp as possible consistent with reliability.
After having tried Marek's settings (as posted earlier) I would like to up the bitrate a bit to see if I can get clean 1080p on detailed scenes which the 25mbps isn't quite capable of. I keep hearing of these "B" and "C" settings but don't see any list of just what bitrates they are. Could someone post here the figures for the B & C settings so that I can copy them into ptool in the same way as Marek did for his "A" settings ...
30min limit removal=Checked
720p30 420->422 color sampling=Checked
E1 Quality=150
E1 Table=86
E2 Quality=130
E2 Table=56
E3 Quality=115
E3 Table=26
E4 Quality=100
E4 Table=4
Video Bitrate FHD/SH=25300000
Overall Bitrate=25500000
Limiting Bitrate=26200000
I assume it's just the Video Bitrate / Overall Bitrate / Limiting Bitrate that I need to change and enter into the boxes in ptool, then save out as a seperate .bin file and load into the GH1?
30min limit removal=Checked
720p30 420->422 color sampling=Checked
E1 Quality=150
E1 Table=86
E2 Quality=130
E2 Table=56
E3 Quality=115
E3 Table=26
E4 Quality=100
E4 Table=4
Video Bitrate FHD/SH=25300000
Overall Bitrate=25500000
Limiting Bitrate=26200000
I assume it's just the Video Bitrate / Overall Bitrate / Limiting Bitrate that I need to change and enter into the boxes in ptool, then save out as a seperate .bin file and load into the GH1?
Oh, meant to say that the video footage I shot on Thursday in online at Vimeo now at ... http://vimeo.com/13598629
There are fewer artifacts in the original file than on this Vimeo re-encode, but they are still noticable on the scenes with running / moving water, hence the need to up the bitrate a bit more.
There are fewer artifacts in the original file than on this Vimeo re-encode, but they are still noticable on the scenes with running / moving water, hence the need to up the bitrate a bit more.
Those a,b,c settings have nothing to do with ABCD buttons. That's quite misleading.
ABCD buttons are for the Ptool settings saved beforehand. These are stored in seta.ini, setb.ini, setc.ini etc in Ptool folder.
If you click on any of the Video Bitrate lines under AVCHD compression section you will have a popup help window that has a), b) and c) suggested bitrate values. THIS is what people refer to when they speak of abc settings.
If you browse through Video Bitrate FHD/SH, Overall Bitrate and Limiting bitrate paying attention to the popup windows you will see that Vitaliy's suggested a,b and c settings are 22,24,26; 32,34,40 and 50,52,60 respectively. These are sort of basic reference points for the testers to start their experiments from.
I know, that's not very straightforward, that may take a while to figure out