@Bkmcwd For SEDNA matrix, i speak only for PAL support, HBR 25p, FSH 50i... 24p mode is a killer on GH2!!! But i live and work in a Pal country ;-(
You are welcome and thanks for using and praising my setting. :-) It seems that especially the Sedna version of GOLGOP3-13 is used only for 24p in my friend's case. There are various evaluations and it is interesting.
Hi Bkmcwd. I'm a (too much) silent user of your patch for some week, very good work, thanks.
I like driftwood's Intra patch but since it don't drive very well for PAL version, i stick with yours.
In HBR PAL, GopZilla 2.12: good all around image, motion not so bad, average bitrate near 50Mb/s and good recording time. (1H = 32 Gb).
For me, it's the best HBR/FSH PAL all around Patch at the moment. Don't use 720 50p, so id'ont know..
I agree with Towi and Lpowell, i find Stock matrix version of Gopzilla and Golgop better than Sedna version.
I don't post so much so Big thanks too at VK, NDriftwood, LPowell, Cbrandin. Special Thanks to you Bkmcwd and Towi for your work on PAL version!
Thanks
Thanks for testing my setting and feedback! :-)
@bkmcwd just wanted to let you know that i have been testing your GOP3ZILLA SednaAQ1C Vers 2.1Beta and i am getting great results in day to day use. very good detial; no visible banding or blocks; good noise rendition; and all at reasonable bit rates.
i am no expert with Streamparser but it also gives me good results whatever i throw at it with this setting (high detail or high movement, etc.) QP range is consistent between 1-5, and DC always at 4 or 5.
many thanks for your great work.
Many thanks for the detailed description! :-)
I know that low qp cannot be used on the high definition scene, if Sedna is used. After understanding it, it is my Sedna version of GOLGOP3-13 setting which was designed so that low qp could be used under Lowlight. If low qp is used within the frame size restricted to the size, a codec will waver and many level lines of high qp macroblocks will also appear as you know. Especially this is remarkable in Intra settings. In order that I may avoid it, the range is kept from spreading in to some extent high qp macroblocks on a high definition scene.
Honestly, my eyes hardly understand the difference of the image quality by the difference in some matrix.
However, since some users are pleased with the Sedna version, I am improving in order to stabilize it.
I myself do not know whether the setting is good or not.
Anyway, it is difficult to use Q13 and I understand that it is restrictive.
@bkmcwd With the Quantizer level manually set to 13 in your patch, the encoder will initially attempt to use 13 as the QP value for each frame. If that level of quantization requires too much bitrate, the encoder will try higher QP values until it produces a low enough bitrate. As we can see in your Stream Parser screenshot, the encoder is actually using QP values that range from 19-21 (in 24H mode). Combined with the Sedna Scaling Tables, that produces DC quantizers in the 5-6 range. With the GH2's max frame size limits, I think this is probably optimal, since as cbrandin points out, DC quantizers below 4 are counterproductive anyway.
This would all be fine if the patch produced DC quantizers in the 5-6 range in all video modes with a wide range of subject matter. Unfortunately, my tests showed that it could only do this in 24H mode with static subjects. When shooting in other modes, QP typically rose to around 25, producing DC quantizers in the 7-8 range, a few steps short of optimal performance.
If you examine the Sedna Scaling Tables, you'll find the intra quantizers range from 5-10 (except for the finest details, which are completely suppressed). This is very flat scaling and will require considerably more bitrate than the encoder's default scaling tables. That's why I suspect the Sedna tables aren't well suited to the low QP levels you designed the patch to work with.
@towi Since P-frames aren't generated in 3-frame GOP's that use B-frames, I don't think the Scaling P Tables are actually used by the encoder in this case. The one exception is the lone P-frame that the encoder inserts in the first GOP, immediately following the first I-frame. I suspect this unusual P-frame may be used by the encoder to determine bitrate control for the stream. If so, I'd think it would produce more consistent results to set the Scaling P Table the same as the Scaling B Table.
I have also tried the same matrix before. I was also able to obtain the good result. However, since there was an opinion whether the matrix for the P frames should also be used, due to interlace processing then at FSH or HBR, I stopped using the matrix. Though 1080p24 is good with it, how do you think in 1080i?
Since I am confused, please teach.
http://www.personal-view.com/faqs/streamparser#streamparser-26
"DC. This is the lowest effective QP value used for DC coefficients in the frame calculated by combining QP with the Quantization Scaling Matrix. A DC value below 4 is wasted in 8-bit codecs and just results in extra processing and no gain in quality. If values below 4 appear it is probably appropriate to raise the Q parameter value (or lower the AQ value) until no value under 4 appears."
Is "DC quantizers of 7-8" which you have described "DC" currently written on the description of Chris @cbrandin? If it is the meaning, is 7-8 satisfactory? Aside from it, if low Q value of Q13 is used, I am also understanding that a codec wavers slightly in principle. However, since a codec wavers more in Intra settings, I think it unavoidable that a codec wavers, when using low Q value in Low GOP.
Honestly, except 24p, I also think that Q13 is too low. At least in 720p, Q value is due to be raised in the next version. However, is it satisfactory in 24p at this result?
Attached Streamparser are results of GOLGOP3-13_SednaAQ1 C_V2.1_BETA2. http://www.personal-view.com/talks/discussion/comment/56753#Comment_56753
Many thanks! :-)
What Stray described is almost the same as my understanding. :-)
Thanks always, mate. :-)
agreed.
I've discovered a technique to completely knock out P-Frames. Bitrate distribution takes P-Frames into account even in 3GOP settings. So we are waisting bitrate for P-Frames that are actually not used in a 3GOP setting.
When you turn off P-Frames with appropriate scaling tables it opens up a completly new world of setting-design for 3GOP (with I and B-Frames only). I've tested this also in your Flowmotion patch and it works. I only have to get the settings stable ... which will probably take take some time (currently I am working on modified GOP3ZILLA settings with Q15).
These scaling tables do the trick:
1080p24 Scaling P=0xFFFF, 0xFFFF, 0xFFFF, 0xFFFF, 0xFFFF, 0xFFFF, 0xFFFF, 0xFFFF, 0xFFFF, 0xFFFF, 0xFFFF, 0xFFFF, 0xFFFF, 0xFFFF, 0xFFFF, 0xFFFF, 0xFFFF, 0xFFFF, 0xFFFF, 0xFFFF, 0xFFFF, 0xFFFF, 0xFFFF, 0xFFFF, 0xFFFF, 0xFFFF, 0xFFFF, 0xFFFF, 0xFFFF, 0xFFFF, 0xFFFF, 0xFFFF, 0xFFFF, 0xFFFF, 0xFFFF, 0xFFFF, 0xFFFF, 0xFFFF, 0xFFFF, 0xFFFF, 0xFFFF, 0xFFFF, 0xFFFF, 0xFFFF, 0xFFFF, 0xFFFF, 0xFFFF, 0xFFFF
1080i Scaling P=0xFFFF, 0xFFFF, 0xFFFF, 0xFFFF, 0xFFFF, 0xFFFF, 0xFFFF, 0xFFFF, 0xFFFF, 0xFFFF, 0xFFFF, 0xFFFF, 0xFFFF, 0xFFFF, 0xFFFF, 0xFFFF, 0xFFFF, 0xFFFF, 0xFFFF, 0xFFFF, 0xFFFF, 0xFFFF, 0xFFFF, 0xFFFF, 0xFFFF, 0xFFFF, 0xFFFF, 0xFFFF, 0xFFFF, 0xFFFF, 0xFFFF, 0xFFFF, 0xFFFF, 0xFFFF, 0xFFFF, 0xFFFF, 0xFFFF, 0xFFFF, 0xFFFF, 0xFFFF, 0xFFFF, 0xFFFF, 0xFFFF, 0xFFFF, 0xFFFF, 0xFFFF, 0xFFFF, 0xFFFF
@bkmcwd I was interested in testing your latest settings to evaluate how well the Sedna Scaling Tables work with B-frames in short-GOP sequences. I used a variety of well-lit subjects - high-detail, fast-motion, and low-contrast. The videos recorded reliably and look good, but the statistics I saw in Stream Parser lead me to suspect that Sedna is not well-matched to these settings. It consistently produced QP levels in the high 20's and DC quantizers of 7-8 in all video modes. The only case where I was able to produce DC quantizers of 5-6 was in 24H mode shooting a low-contrast, static subject.
Looking over the INI settings file, I see that Q is set to 13 for all video modes, which is a far more aggressive global quantizer than the encoder was actually able to use, in spite of 24H mode's ability to produce very large I-frames over 1Mbyte in size. My hunch is that the very small quantizers used to encode fine details in the Sedna Scaling Tables are overkill for this patch, and use up so much of the available bitrate that the encoder is unable to achieve your intended QP values and DC quantizers.
@stray, thanks that was helpful. For some reason I seem to remember reading that the matrix from q20 was different and it was specifically the first sedna matrix he made when he began working on sedna. Could be wrong though. So many pages of sedna stuff. Im trying the golgop tonight.
@liquidify You can't really change the Q (AQ being a different approach to the same thing) as the Q settings are probably specific for the GOP 3 setting. What @bkmcwd has done is to incorporate the matrix from sedna C and then rebalanced everything for it to work effectively with a GOP of 3 (which probably has involved setting the Q to a different value). So setting Q20 or AQ1 is meaningless in this particular GOP3/Sedna C scenario per se. My understanding of @driftwood s settings are that the matrix of the Q20 and AQ1 versions are identical, and its just the quantizer that is being set differently (AQ1 kind of forcing a higher bitrate accross more shooting scenarios).
I think what @bkmcwd means by puzzles the codec is that it is not entirely stable, what I noticed myself was that the B-Frames would be extraordinarily large even on static shots with the A matrix. There are also versions of the GOP3 settings with the Sedna A matrix in this thread if you want to try them.
@bkmcwd, I am impressed and I think you have something good going here. I would love to see it with q20 or aq1 a though. Is this possible without much complication? And when you say it puzzles the codec too much, what tangible result have you observed due to this?
Thanks! :-)
Many thanks! :-)
Thanks for feedback! :-)
"why the c matrix was used"
Since the AQ1A matrix is too aggressive and it puzzles a codec too much, I think that the AQ1C is more stable. :-) Regarding the Q20A matrix, I have not tried yet.
@bkmcwd, wow GOLGOP3-13_SednaAQ1C_V2.1_BETA2" is amazing. It's the best yet from you. I tried 24H and it looks, wow. Great work man!
@bkmcwd just curios why the c matrix was used. My favorite sedna's have been aq1 a and q20 a. probably been answered already but i cannot find.
I loaded it up this morning (12 hours ago) and shot some daylight clips downtown and around the harbor. GOLGOP3-13_SednaAQ1C_V2.* just keeps getting better. Shot some 1 minute 'stairwell torture' clips. File size for 30p (around 311MB per minute) was a bit smaller than I expected (I'm a bandwidth hog) but it's smoother in low light (ISO 3200) than beta 1. 24p also looks 'smoother' (and cleaner) than beta 1. I had no problems with write errors or in-camera playback shooting 1 minute clips with Cinema 24p. Didn't check spanning. Thanks for doin' what ya do! much appreciate it :-)
okay thank you @bkmcwd i will try them now hopefully ad some results later!
"what did you change in this current version?"
Stability and image quality have been improved by change of GOP tables. :-)
Since there is a tendency for qp to become high rather than using stock matrix when Sedna matrix is used, I think that I optimized how depending on which qp appears in 24p.
Although this was made in 3.65d, of course, it could use also in 3.64d.
BTW, since I have improved 720p now, I will release some new settings soon again.
@bkmcwd one question are these settings for ptools 3.64d or 65? im also wondering what changed?
@bkmcwd what did you change in this current version?
It looks like you're new here. If you want to get involved, click one of these buttons!