@driftwood Just did a shoot with the new SeAquake it gave me card read errors every 30seconds, or sometimes every 1minute. Lens used Pani 20mm f1.7 not sure what's the cause, ooh almost forgot using the 45mb/s sandisk card.

Problematic card, Ive been shoting with the same lens with no probs. As a test try shooting in full manual mode and let me know if it records longer on your card.
@TrackZillas You say READ errors? Have you popped it into the computer and copied it over to HD and into NLE editor? Should be fine. In camera playback and sd card into TV or other device cannot cope with the high bitrate - ie you will get brewakup on hi detail scenes - but theyre fine in the edit :-)

@pchristoph That's great mate, thanks for testing it.

Driftwood's seAQuake (latest) + MPEG Timelapse. Thanks Driftwood - I've just loaded seAQuake, can't wait to try it.

@driftwood I tried reformating the card numerous times still does it. Gonna keep on playing around with it..

Hey, @Driftwood . . . did you ever figure out that rogue .MTS file from the other day? Also, I'm a little confused as to the max quality GOP1 settings. Is SeaQuake really the best? (I thought it was intended to span, which you thought would not be as good of quality as some other non-span patches?)

@driftwood
I tested my patch "Q18 test patch with Driftwood Tune", before readjusting.
The 1st sheet is with Stray's chart, and the 2nd sheet with Pappas chart.
Since the Stray's chart gives high stress more from Pappas, and since it is moving by hand, naturally it becomes a waveform, I think that this result is natural, but I do not know for a problem to be where of this. :-(

The way of a test is a procedure which it continues moving up and down, having a camera by hand and shooting test chart.
Setup is ISO3200 and SS800.

Thanks for your advice!

@bkmcwd Yeah, Im not too bothered whether you hand hold or tripod your test on the death charts. By the looks of it you have a unsteady hand! ;-)

But your answer is there before you in the declared bitrate in Elecard analysis. Its declaring nothing like you expected!

Although you have set GOP3 to 176M, all the other parameters you have set in the frame buffers 1 and 2s and the Hi Top Low Top / bottoms etc... total up / or in your case subtract to/from the total bitrate. Hence somewhere, something is reducing the bitrate. It could be because utilising my encoder settings and having 1080p24 encoder 1 set to 3 is not helping you. Stick it on 2 and try it. Though you probs require B frames.

You need to further tune these settings if you are going to use them and look at different multipliers or incrementals until you stabilise the bitrate back to the intended size which will in turn open up the buffers higher.

Why dont you start by rejecting Q18? Switch off IQ and Q and go back to AQ2 or AQ3. Analyse your older settings which had higher overall bitrate and see where things could possibly going wrong.

All the best with trying to sort it back out.

@FGCU It's stops the recording after about 30sec, to 1min yes the Seaquake I'm gonna recompile the patch one more time and try it again, or it might be my card..

@Hallvalla - sorry, I'm getting all of these mixed up! I meant aquamotion, not reaquainted :-).

*** NEW TerrAQuake *** This is seAQuake verB for poorer type 10 cards. Very slight drop in frame size to work on non top spec type 10 cards. TrackZillas might like this. :-)

@driftwood jajajja so much work with funny names, thank you!
it seems like you have a lot of fun by making this patches hahahah, lucky us :)