And it looks like the data rate is the same as with everything checked. So looks like we don't need these, right? Anyway to get the 1080P data rate higher than 60mbit????
(And leave up the chart, I think it's just a jpeg of a window screen, but it works like a charm)
@kae Big thanks for testing. Results match to my expectation, in fact. You can live without this 3 patches. As for bitrate values, such GOP results in bitrate estimator making wrong decisions (as he expect GOP to be 0.5sec total). This is why it allocates more bitrate.
I think that we'll be able to push bitrate further. Just need time.
Low light note: The above 3 GOP settings are yielding a very respectable filmic image at 3200 iso. Keep the shutter at 60 or above (50 didn't look as good to me) and the noise at 3200 iso looks a lot like film grain. It'll certainly do in a pinch.
@kae "You have I frames at 1Mb, and all else is B frames only. Each references two low compressed I frames :-)"
I think that's because in the screenshot's case I was shooting the codec crusher chart which was static and had no color info. The b frames probably didn't need to be bigger. Below, I've attached some night interior footage shot at 1080 24P 3 GOP with the same settings as above and you can see the B frames are larger as I was moving the camera a lot. The I frame didn't need to be as huge as it was a normal detail shot instead of the massively detailed codec crusher. I will try and take some higher detailed shots outside and see if I can get the 1mb I frames along with higher bit rate b frames.
Can't test anymore until Monday but wanted to post my latest 1080 24p settings. It seems just doubling the high/low-bottom/top settings provides better looking footage with bigger b frames than using a higher multiplier on those so I went back to my previous settings. These settings will give you up to 60Mb 1080 24P 3 GOP with approx. 58Mb on the death chart (little lower than the Extreme settings but I think this is because it's laying down bigger b frames so it's more efficient).
I like these settings best so far, the motion is very crisp and the autofocus with the 14-140 is snappier than with the extreme settings. There are just basic 1080i/720p settings in this file which you can change at will. 720p GOP for Pal and NTSC is 6, NTSC 1080i GOP is set to 6 and Pal 1080i has be 3 because it's tied to 1080 24p. The 24h buffer settings may be redundant as Vitaliy proved above but I left them in.
I do like these 1080 24p settings better visually than butt's latest settings but that's just a personal preference. At 60mbit the image and motion seems crisper with these and the data rate is definitely higher. Any testing would be appreciated.
@kae You can post a setting on your favorite now Gop3 (set.zip) - thanks
10:00pm have now both settings, @kae and @Butt side by side testet, result: I see no real difference - I prefer them on my setting - also because of slightly lower bit rate
Butt Sadly the 720p setting of yours gives my image lots of macroblocking mud when static,moving,anything. See pic (look at stone cats face to see total lack of detail)
I am no expert, but I am asking myself if the Gop 3 is more about bandwidth than processing power. That we could achieve more with I frames that p or b frames because perhaps the architecture has changed. That is the bottleneck is more the processing power than the speed of the I/O of the gh2. It seems that it is a fact now that the gh2 has a much better controller to write to the SD card (From what I read) as with mjpeg reaching already in the 100+ megabit. Perhaps because of this it will be easier to get higher quality with the shorter gop where the processor has to calculate less. It is a bit like the red, which just take the raw data (even if it is mildly compressed) from the sensor and send it to the media. It requires vast amount of bandwidth but the debayering and intensive processing are done latter. I am not saying the same from the gh2 as the debayering is occurring but more I frame means less work for the processing engine. This is just a theory, I might be completely off.
Yea, from my understanding, less compression (shorter GOP) should mean less processing... but more data to move.
I also suspect that most modern consumer cameras (like the GH2) probably have the ability to write compressed-RAW data for video... the companies just don't want this to happen because it'll mean the end of ALL their "professional" divisions.