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

Instead of a battery pull, try just turning off the camera. It won't turn off instantly, it may take 5 or 10 seconds. If that doesn't work then battery pull may be the only option.
 
mimirsan said:
I use ptools recommended "c" settings. Very very stable for me using a sandisk class 10 and verbatim class 10. Without native 24/25p.

If I use same settings but with 24/25p ticked on I get write error on static shots. As mentioned before...seems to be a common problem with the 24/5p patch.
Click to expand...


Is yours NTSC or PAL? If anyone else is getting this error can you post up what region gh1 you have. Want to see if there is some correlation. cheers.
 
cbrandin said:
What do you mean by "rogue I frames"?
Click to expand...
I've seen them too, in StreamEye bar charts. I first noticed them immediately after I set Sharpening +2 and Noise Reduction +2 in the Smooth Film Mode. My intent was to test whether this would have an effect on the huge end-of-GOP P-frames that we've seen when filming static scenes.

I did a test run of 25 ten-second movies (using PTool C settings and Native 24p) with the camera mounted on a tripod and focused on a gray sidewalk. While I saw no Write Speed Errors or huge P-frames, three of the videos had "rogue" I-frames - a singular large I-frame with zero P-frames following it. The result was pair of adjacent I-frames, the first about twice as large as a typical I-frame, and the second smaller than normal.

The rogue I-frames are similar to the huge P-frames and occur in nearly the same location in the stream of GOP's. But they're not as large as the huge P-frames and my Class 6 and Class 10 SD cards appear to tolerate them without generating Write Speed Errors (at least so far in the tests I've done).
 
Or do you mean the following P frames were tiny? One would expect that in a totally static situation if the image wasn't changing.

Chris
 
There were no P-frames at all following the rogue I-frame. That's why there is always a pair of adjacent I-frames whenever a rogue I-frame appears.
 
You should be able to do a screen capture of the image on your monitor and save it as an image file and then post that. I would really like to see this because it runs contrary to everything I assumed about how the GH1 works and could be a very important piece of information. Do you need help with the screen capture procedure?

Chris
 
i conduct two tests of GH13 under PAL system and native 25p, "D" setting as well.

with class 4 SDHC, the first test changed to high shutter speed at 1/1600 for high detail frame. wihout any card write error and had max 51 and avg 42 at 1080p25 from streameye. this max bitrate not my record (record max is 63) but under high detail scene, my GH13 is stable to handle this bitrate or even higher, so as you all.

the second test is static shoot test, placed it at hot environment (inside car under sun light) and shoot over 40 mins until i stopped. no error at all.

my little conclusion : "D" setting, PAL system, native 25p, class 4 or higher. GH13 working stable and error free.
 
Here's a rogue I-frame that happens to be about three times the average size of a typical I-frame:

RogueIframe.jpg
 
You must log in or register to reply here.
Back
Top