@proaudio I was playing safe and following the ratios in the cbrandin 44M and 66M which work off multiples, so I multiplied the stock 24L by 4 too rather than try 66M. I don't know what the FB, FL etc settings do per se, so I played it safe. Incidentally I've found this 24L works well too, so far. It's interesting shooting a locked off low detail scene with both settings, as the average bitrate between it and the 24H 88M can get as close as only a 1Mbps difference (which is to be expected I guess as the AQ is only at 2, but does mean using your judgment a lot of shots may as well be taken with the 24L). I don't know of any reason why the 24L shouldn't be able to run at 66M though, I will give it a whirl tomorrow and see. Thing to note is the 24p video buffer, much like the 44M AQ4 and the 66M AQ2 settings are set to the stock value and things are stable.

Edit : On playing it safe although as the FBs and limit etc are giving enough room for the 24H 88M setting (and probably more than enough and maybe could be shrunk) then yeah, they should fit the 66M. But my concern is there are other things going on, in terms of how they're used, (space and overflows etc) that may be resulting in the cadence problem. Like a kinda ratio we don't know about. Its probably a dumb worry, but it's how I think after seeing such weird unexpected behaviour out of certain settings.

@driftwood I'm not attacking changing the 24p video buffer setting, I just note that chris didn't do that and instead changed the FB, FL, Frame limit and top/low settings and left the video buffer at stock. I don't know if it's an either/or thing or what, just that it works there so I carried on that model to these 88M settings and left it at 24000000 and its stable so far. Chris said it was about breaking the limit of the I-Frame size to take full use of the bandwidth, but I've never seen a really noticeable leap in I-Frame size personally (1.17M is the highest I've seen). In my ini FB, FL, Frame Limit and top/low settings are x4 for 24p.

@driftwood So what are the FBs and Frame limit for ? thanks for that info, will try to tweak the frame size up tomorrow just focussing on those hitop/bottom etc.

Edit : Hang on , if thats true then those hitop/bottom settings must have a ratio relationship to total bitrate, otherwise (as I multiplied them by 4) I would have seen larger I-Frames than I do with the 66M settings, which I haven't.

@Stray Can you do some tests for me using your 88M? Just go thru Encoder setting 1 1080i/p and change it one number increment at a time starting from 1 and go to 17 (thats 17 extra tests on your 88M setting. Let me know what happens). I'm doing the same on another few settings at the moment. record 1080p24 and 1080i/60 only for now. Is that ok? Report any anomolaties from the base setting. Just use streamparser for now but keep the mts files in case i might need them off you. is that ok?
Make sure you remember to check it. Each test 30 seconds on pappas.

I'm afraid I can't tonight cos I havent got the light to do it properly, and I'm out shooting tomorrow for a project but will happily do it on Tuesday. Also, cannot do that test on the 1080i, just can't run the 1080i at that bitrate with this setup, it won't be stable. Thats also for me a load of testing to do it properly, as I take at least 6 different shots of different types for each setting I change and run them for at least 2 minutes to get a decent sample. Happy to do it though if you can wait a while.

Heh, I was asking what the FB and FL do, in relation to everything else (especially the video buffer). Is the FB the space where the frame is actually encoded, and then its shifted to the video buffer for example ? Also as I said in my edit above, if hi top/bottom etc directly relate to the possible size of I-Frames then the fact that I multiplied them by 4 suggests that I would have seen larger frames than I did for the 66M AQ 2 settings (where they are multiplied by 3). I didn't, which suggest that if that is the function of those settings that they work on a ratio relationship to bitrate, as they are constant in comparison to the 66M where the multiple on them is 3. So, will check tomorrow quickly before I head out by multiplying them by much higher values.

Stray,
I tried your 88M AQ2 settings file on a static shot using pappas death chart.
1/16000 / ISO3200 / around 2 stops under exposed
Smooth 0,-2,/0,-2
Streamparser shows a cadence issue.

True, these are exteme conditions, but this is what we need to determine our limitations.

@all can someone recommend a good enough card to work with Driftwoods 132MB's hack. I think that card I got at the mo isn't fast enough. Is UHS 1 Memory cards really going to be supported by the GH2?

@Stray Check yours.

@Stray and @proaudio4 - try these out for cadence if you havent already. 88M/66M AQ2 plus 55M/48M 720p AQ2 in one setting file.

Stray,
Remember that I mentioned 66 AQ2 passed my extreme test. It's the tuned version from Chris.
Based on this, I'm willing to believe there are 88M AQ2 settings that would also pass.

@Stray Your 88M/64M Buffer charts you requested. Not good on the buffer sorry to say. Try using 36000000 and c what happens. Good testing. Keep going.

Please point me to this?