Thanks. Perhaps we should start a separate Topic for this? I'll leave that up to @cbrandin as it seems he is looking into it and he knows the ropes here on the forum :-)
@driftwood Sure. If I can get to it tomorrow a.m. I will, otherwise Friday I can do a bunch of testing. I plan to do some 6GOP as well - if anyone has specific requests I'll try to incorporate them.
GREAT WORK ALL BUT BE VERY CAREFUL HOW YOU JUDGE RESULTS
First off, great work by everyone on the new 3 GOP settings. I am watching attentively from afar. Though sticking with my 65 extreme settings for now for stability's sake, I have been playing with some of Driftwood's stuff and find the AQ2 100mb + looks great but there are anomalies in streamparser with this footage. You all also must be very CAREFUL HOW YOU PLAY THIS STUFF BACK. On my new Panasonic Viera 42" screen the SDHC card reader will playback my 65 extreme stuff perfectly but will not playback Driftwood's stuff. BUT, Driftwood's settings will play back perfectly out of the HDMI of the cam or on the computer. So before judging 'cadence' or 'studder' issues make sure you have enough horsepower to play this stuff back. And by all means judge NOTHING after it's been re-encoded by Vimeo. Vimeo's encoders are pure crap for heavy motion, non-standard avchd stuff like we are testing here. I'm having pretty good luck with AQ2, 24H at 100m, and driftwood's t4-t1 fix but the file sizes are crippling. Yes, the footage is amazing and a bit better than the 65 extreme settings but it takes so damn much room to store. But you guys ARE getting somewhere and this is fantastic!
@sohus Here it is again :-) Remember: its only setup for 1080p24/H so you may want to copy on your own settings for the other recording modes. GOP3 132M AQ2
@kae I dont get any HRD parameter probs with my settings, though I have had them with your 66M GOP3 which Im trying to understand why... T4 to T1 needs confirming regarding cadence - as I have had no cadence on the footage Ive recorded with unchecking T4 = T1 - probably due to the bitrate being so high. Needs confirming.
Edit: re 100M tests: Ive been doing a lot of tests at 100M too, and have had success, indeed it forms the basis of my GOP1 testing now...
GOP1 132M MANUAL Q or AQ0 - This is totally for motion whilst trying to keep file recordings down in size. Its been hell trying to find a stable GOP1 (anyone?). Here's the latest 50% quality / and a AQ0 attempt which will need testing. Difficult trying to get high quality. AQ will not work properly with GOP1 unless some serious tuning is probaly done... So Ive inputted tried and tested IQ20 and Q 34, along with the high bit rate and higher matched frame limiter & a AQ0 version - so check it out it may lead someone to find the golden spot. Still not happy with GOP1 though...
I am not sure that there is no telling whether to become your reference, but I report after kae's 65M the setting of 66M,3GOP found somehow. Although this is only what tampered with GOP, and Quantizer value and top and bottoms based on Chris's66M, 24H and 24L(30H and 30L also) can be used now once. Since I am only looking for stable 3GOP but not high bitrate, I don't know strict evaluation, but how is this? On the other hand, in now 66M,6GOP, I have not found the good setting at all.
EDIT: To me, I think that there is no problem of span in this setting as long as I tried this in the room for a long time. I cannot understand whether it is that this set is really good. However, for me, it is convenient.
EDIT: Then, it turned out that the spanning problem occurs occasionally...
To avoid any confusion, in my HDMI vs AVCHD testing, I used Eiji's version of 132M. The only difference I can see is that Eiji's version has this line -
1080p24 T4=1080p24 T1
whereas Driftwood's version does not.
Don't know if that has any signifigance. Driftwood? Eiji?
@Ralph_B Theyre both mine ;-) I gave eiji my settings and left on T4=T1 in case of cadence. However, in my opinion the higher bitrates don't need this setting but it needs confirming by more than just myself.
Tested today with a few trees behind each other against the sky at high winds, with my sharpest lens (Minolta MD 24mm). This normally breaks any AVCHD standard codec and makes it smear and macro-block.
I have to do heavy pixel peeping to see any difference against HDMI recorded on Ninja (plus, you have to de-interlace the Ninja). Congrats!
BTW, no problems with either a Transcend card or a Sandisk Extreme, other than the 4 GB limit.
@driftwood I was just wondering how easy it would be to adapt your 132mbps gop3 settings for 720 50p? I do a lot of speed ramping and slo mo work, but I'd love to try these gorgeous settings as well.
I found somewhat better 6GOP setting following 3GOP. It seems that cadence is stable although there is a problem of spanning. Only a few changes my 3GOP setting which I stuck previously. Also when Quantizer value was 18, in 24H mode, it seemed to be OK, but in 24H80%, since the card error came out, QV was set to 20. Since the spanning problem was not lost as for QV=24 like 3GOP setting of mine, QV was set to 20 for quick-fix. Is this worthy although I have not verified about quality yet?
Since the spaning problem is not solved in this, my favorite is my stable compromise 3GOP setting, but was the problem of spanning solved by somewhere? Because I have not caught up with you in other threads recently ...
Although 3GOP stuck upwards is the same, since it is recording having a camera by hand and moving it indoors, the form of the wave is notched.
@bkmcwd Wow. Great work mate. I've shot just over half an hour with this 66M GOP6 and had absolutely no problems with it at all. Cadence is perfect. Shot static, detail, heavy motion and detail no issues at all. Defocussed, refocussed, whip pans everything I've seen in the past could cause problems and these settings are solid. Nice. Exactly the motion I'm looking for. Its been a good day to test today too, as it's very windy here so the trees outside are really being thrown around.
In lowlight indoors I think IQ does drop slightly from the 66M AQ2 GOP12 but I can live with that. My only concern is as you've set the quantizer and also AQ to 2, I'm guessing that your quantizer settings are overriding the AQ setting. Maybe driftwood, vitaliy or chris (or anyone) have more insights over what the AQ settings and the tester patches conflict with each other. Many thanks for these settings, I'll be using them a lot over the next couple of days.