@kae
i noticed that the last 4 frames are always (even the ones with normal footage) not ingested by 5dtorgb (it causes the freeze of transcoding) and most players have many difficulties to play the clips (for me it's impossible to get to the end). No issues or problems after transcoding.

@robbin You need to register/login to get them... Al

kae@ with what you look the clips to see of are fluid or stuttering occur ?
with the 30p 60i not problem on iMac 27 at 60hz but 24p 50i footage need switchResX to bring the monitor to 50hz.
Now i test on a projector in 1080p cinema 24fps.

Just ran Kae's 3 GOP setb.ini (22/07/2011) tes on an hour long recording. The first file in Streamparser shows up strange result. Look!

I think this is a bug in Streamparser. Maybe I have an overflow happening because of the high bitrate. Could you please post a picture of the time-based analysis?

Chris

Driftwood, like Chris just mentioned, switch to the time mode setting and screen capture this.
This is not a camera issue, but you sure found a bug with streamparser.

@ driftwood

If you look at the video bitrate reported it's a negative number - that usually happens because an integer variable overflowed. I suspect I need to change a variable from int32 to int64 somewhere. I wanted to see the timing analysis just to make sure that's all it is.

Chris

Testers only:

Been testing different 1080 24P 3GOP combinations for the last five hours - have tried adjusting quantizer encoding settings, encoder frame limit, frame buffer sizes for 24P, and 24P video buffer settings and nothing has given me a more stable result than my previous settings. I did manage to up the 24H video bitrate to 65Mill (max for ptools 3.61d) and it seems to be as reliable as 60mill. The advantage is a higher data rate encoding. I'm getting 64mb/s on the death chart and normal footage is encoding at a higher rate. Can I see a major visual difference? Not sure. It's all so clean at this data rate, it's hard to tell short of shooting rez charts, etc. I've attached the 65M 3 GOP settings below if someone wants to test. You WILL get 10 frames of blockies at the front, I am not getting Svart's end glitch on playback and have no problem ingesting the full clip into the Avid, but others might, so be forewarned - ROLL EARLY and CUT LATE with these settings. And please shoot the NORMAL footage you will get paid for rather than just lawn, trees and the death chart to see how you like the look.

I think I see a whisker more aliasing at 65M but this may be due to the encoder being able to salvage more detail. I've been shooting with sharpness at 0.

Still hoping others can eliminate the 10 frame glitch, I couldn't eliminate it with all the combos I used in the last 5 hours so I'm still stumped on that one. FWIW: I'm using a Dane-Elec 32G class 10 card.

EDIT: SEE MODIFIED SETTINGS PAGE 6 FOR MORE STABILITY IN OTHER 720P/1080I MODES!

@cbrandin
Defo integer prob as you can see the fifth and final file written (at around half a gig in size) reports okay.

@butt
"use this
and you have no problem
and - incam-play transfer works"

How'd you set 24H buffer to 70mill? Ptools won't let me do that? Will try your settings now. Thanks.

@cbrandin
Yep the same first file now reports fine in stream frames/bitrates. cheers!

I respect much of the work on this topic.

However I feel the bigger things are getting lost in all these distractions and I am still no the wiser over whether to adjust the GOP for better image quality or worse.

GOP 3,6 or default for low light shooting, which is the best choice?

@EOSHD
6 is closer to 3 in aesthetics, and closer to 12 in efficiency;
A simple 42mbps modification is enough w/ 6 for densely detailed shots.