euh my own settings that is......

Sure here it is.
There is a lot off info in the ini file
Because i keep in there updated what i change.

The settings are focused on 720 pal, HBR is also oké, 24p is not, i never use it.
Its not based on detail in the shadows, for what i film, its not important.
A nice clean image up to 3200 iso with high shutter speeds

DOWNLOAD the version some post lower, cant delete these one!

@towi Did a short test repeating a sequence of 4 chords on my Martin 6-stringed DCPA-4 guitar:

Looks pretty good on screen as well in streamparser! Some B & W filtering in Vegas 10 was used. Will compare your settings against Driftwoods Cluster v2. which is due to be released.... THNX!

@towi

According to your advice, I uploaded the improved versions immediately. How are these?

Thanks again. :-)

BTW, Is the GOP table in which I was before mistaken adopted in PAL66 of you? Is it satisfactory now?

@bkmcwd

"BTW, Is the GOP table in which I was before mistaken adopted in PAL66 of you? Is it satisfactory now?"

"Natural V2.0" was the satrting point for "PAL66". As 720p50 was already set to GOP=6 I've just copied its GOP table to the 1080i50 GOP table (1, 1 , 1, 0, 10, 30).

Have not yet tested your latested updated versions... but as you went back to the former GOP tables for 1080i50 I expect the patches will work fine in PAL mode.

---

@mozes

the streams you've posted look strange. As you only shoot 720p50... why not just use Ralph_B's "Sanity" patch? Or maybe bkmcwd's "natural"?

@mozes How are you planning to improve the look of the noise in your setting ? Which settings (patches) give you a noise (grain) that you do like ?

Sorry, but all of the streamparser graphs you've posted so far show that your settings are very deeply wrong so I'm not going to spend my time trying them. The graph should not flatline like it is, B and P frames should be considerably smaller than I-Frames. It is falling straight into some kind of bad fallback mode judging by the very large, by comparison, initial I-Frame. Creating settings requires a very good understanding of what each parameter does, and their relationships to other parameters. If you like the look of the Sedna matrix then use a setting that has the Sedna matrix already or spend the considerable time required to learn how to create a stable setting. Basically, keep going and post again once you've got a stable good looking cadence out of it.

Edit : Seriously, try setting your quantizer settings for 720 to something more sensible than 8.

@mozes Yep wait for the wiki. Sorry I can't be more help to you at the moment, I've never tried creating a 720p setting, But look at other Streamparser graphs that people have posted from stable settings, look at the ratios in size with those stable graphs between the I, P and B frames. They may be different sizes pedantically but they are still basically a flatline. Also use the decode elementary stream tool in Streamparser to see whats going on too. Try not setting the quantizer at all and use the AQ settings, start with the lowest AQ value. Get something stable and then tweak it up slowly until you find the limits. Frankly it may be better to not use any of the patches for tester settings other than the matrix itself.

@towi

I got it! Your PAL66 is interesting. I also think that 6GOP may be one compromise point of a motion and IQ. Therefore, I am also going to do the homework from driftwood.

BTW, Honestly, my latested updated version lacks in interest. Since, as for HBR combined with HQ matrix, frame size becomes large more, I would like to also investigate a stock matrix more.

Thanks always! :-)

@towi

Thanks for feedback always! :-)

"GOLGOP13 naturally will show its strength due to the finer noise pattern (GOP=3 vs. GOP=6)."

This is the point where I have stuck to 3GOP. Just as Nick sticking to the intra, there is a meaning to "be 3GOP".

"There's an issue with "clip duration" and "pcr duration" (the latter is always much longer) in 24p25p-NINE."

I also do the before same thing and may be warned from Chris. Stray knows well. :P Is this issue unsolvable? This issue is brought about because your "Top and Bottom Settings" are larger than the value demanded from "Video Bitrate". If you want to maintain "Top and Bottoms" in the present values, you have to carry out "Video Bitrate" more than 80M at least. Or you have to lower the value of "Top and Bottoms" conversely. And in order not to generate issue of duration, it is required to make "Video Bitrate" somewhat larger slightly than the bit rate which actually appears. It is set as bigger "Video Bitrate" than the bit rate which actually appears with my latest settings because this.

Was it transmitted? :-)

@towi

You are welcome!

"The problem is I have no clue about all the settings and values :-)"

The same for me. :-) I was helped by @driftwood and @cbrandin in such a situation repeatedly. I still have many things which are not understood. Since especially I began to touch about 60i or HBR recently, I do not understand in many cases. So, I have to test more.

@towi If you guys are talking about the issue I think you're talking about, and my memory isn't failing me, then it means that you have blocks in the file with identical timestamps to other blocks. This can on playback lead to small areas of the image either freezing or playing at slightly different speeds to the rest of the image. I noticed this with one such early setting that had this issue when shooting water and leaves, it looked beautiful to my eyes, but was obviously also very wrong.

Edit : But I guess all of this could relate to the latest fix to streamparser that chris has released, so its probably best to recheck the files where there was a difference with the new version.