Anyone having card speed issues, please try again without native 24p

Regardless of cards, the Native 24p patch has been shown to be buggy. That alone should invalidate any further testing of cards since you are now dealing with an unknown situation where you could be getting any number of odd I/P frame multiples or bitrates and you are now operating outside of the normal AVCHD design.

Yes it might *work* but what happens when you find yourself in the situation where it doesn't? There are plenty of people posting videos where they have gotten the "card speed" error unexpectedly while shooting something in Native 24p. While this might be OK for some folks, if that happens to me on my upcoming shoots, I'm screwed. I'm not willing to take that risk.
 
cbrandin said:
Have you reformatted the card after getting an error? I have found that if the card gets fragmented it doesn't just degrade performance - it devastates it. That might explain why you are suddenly getting so many errors in a row.

Chris
Click to expand...


UNFORTUNATLY, I am formating my card between each test.
 
Svart said:
Regardless of cards, the Native 24p patch has been shown to be buggy. That alone should invalidate any further testing of cards since you are now dealing with an unknown situation where you could be getting any number of odd I/P frame multiples or bitrates and you are now operating outside of the normal AVCHD design.
Click to expand...
IMHO, native patch is not ready for prime-time yet, that's why I recommended it is marked 'experimental' in PTool Manual thread. Just increasing bitrates to "C settings" with a decent card will increase IQ and drastically reduce mud (from stock) and be largely "problem free" for most types of scenes. For casual PTool users mostly interested in improving image quality this is the best route at the moment, in my humble opinion.

However, testing of native patch under different testing scenarios should continue by those who are comfortable with uncertainties that are brought with it. Hopefully, feedback generated will help development resolve bugs in encoder core that are the real issue here.
 
Ok surfer, I will do the same.

At list that solve the mud problem, right?

Now can someone please explain to me what is the 1440 in the mpeg setting mean for?

Or, even simple question, is it possible to shoot FHD with mpeg?

Thanks
 
adys said:
Ok surfer, I will do the same.

At list that solve the mud problem, right?

Now can someone please explain to me what is the 1440 in the mpeg setting mean for?

Or, even simple question, is it possible to shoot FHD with mpeg?

Thanks
Click to expand...

Yes increasing bitrates in AVCHD solves problems of mud and rolling.
For the moment shooting in MJPEG is HD (1280x720) and not FHD (1980x1080).
Personnally I don't like MJPEG cause it's grainy and 30 fps - weird speed for me because i'am in France and we used 25/50.
 
show the stream info also including max, avg and min bitrate of the footage.

i am finding the those values in max number based on [50,56,60], i think should be your SD card issue if your camera hanged before reach the max.
 
I've just done some experimenting with an indian throw hanging on my wall, the result is

1080p25, manual focus, static tripod - Crashes after 9 secs every time. I managed to get a 5 sec clip of this
1080p25, autofocus, static tripod - Works for over 30 secs (see clip)
1080p25, manual focus, panning - Works for over 30 secs (see clip)
1080i25, manual focus, static tripod - Works for over 30 secs (see clip)

Download the test clips from http://rapidshare.com/files/406628974/GH1_1080p_error_tests.rar.html
Settings used: 20mm @ f1.7, 1/100 sec, ISO 1600, tungsten white balance preset
p25 recorded at 28mbit, all clips report around 25,000kbps.
i25 recorded at 32mbit, 28,000kbps reported

I can reliably reproduce the problem with a high detail static scene, but only in manual focus mode. With autofocus enabled it seems to work fine, it's possible there's some periodic focus hunting causing movement but I can't see any focus hunting in the clip other than the very beginning. Panning, even very slowly, also prevents the error. If I pan around for a bit then stop it crashes after a few secs.

It seems there's something about a static screen that is breaking the 24p/25p mode. It can't be a general card speed problem because it records at a higher actual bitrate in i25 no problem. I have a feeling autofocus might be involved as I just can't see any focus hunting in the clip, which should be very obvious using the 20mm wide open.

I suspect that whatever the error is there's some internal error in the encoder and the error trapping routine in the firmware is only designed to display the write speed message. That would also explain why the camera completely locks up.

Maybe this is why Panasonic used an interlace wrapper in the first place, there could be some hardware limitation (buffer size or something) that means it can't properly handle that many pixels on a single frame while encoding (each individual progressive frame has twice as many pixels as an individual interlaced frame)

I hope these test clips are useful to anyone working on debugging the problem and let me know if you want me to try anything else.
 
Svart said:
Regardless of cards, the Native 24p patch has been shown to be buggy. That alone should invalidate any further testing of cards since you are now dealing with an unknown situation where you could be getting any number of odd I/P frame multiples or bitrates and you are now operating outside of the normal AVCHD design.

Yes it might *work* but what happens when you find yourself in the situation where it doesn't? There are plenty of people posting videos where they have gotten the "card speed" error unexpectedly while shooting something in Native 24p. While this might be OK for some folks, if that happens to me on my upcoming shoots, I'm screwed. I'm not willing to take that risk.
Click to expand...

second that it did happen to me , wish i read this before the last event :(
 
You must log in or register to reply here.
Back
Top