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

Yes, I explicitly set the GOP to 12. Note that the GOP's before and after the rogue I-frame have the correct 12 frames. That means the rogue I-frame isn't just a huge P-frame that was somehow replaced by an I-frame.
 
Now that I think about it, perhaps the "Write Speed Error" that occurs with huge P-frames is actually an internal P-frame buffer overflow error. If the camera has sized its P-frame buffer to handle normal-sized P-frames, then an unexpectedly huge P-frame at the end of a GOP could be overflowing the buffer. But with a rogue I-frame, the camera would detect its size at the start of the one-frame GOP and allocate a large enough buffer for it, which would explain why rogue I-frames don't provoke Write Speed Errrors.
 
I'm not sure the pulses produce write errors. In fact, I've found that the write errors happen more often without the Native 24p checked. That would make sense because the wrapped mode has to send more data because the wrapped version sends 60 "interlaced" frames for every 24 non-interlaced frames. The extra 12 frames are redundant pullup (does that term exist?) frames.

Chris
 
hey lpowell,

I got involved in another thread about "pulses" and ended up confusing everybody because I was talking about the pulses that appear in EyeStream and they were talking about another kind of pulsing. Maybe we should start using the term "Spiking" instead to avoid confusion.

Anyway, I noticed that you are using EyeStream 1.1 and I am using version 3.1. I wonder - do you suppose the different versions of EyeStream are interpreting the same anomaly in different ways?

You can download a demo version of EyeStream 3.1 that works for 30 days. It might be interesting to see if it interprets your clip differently.

Chris
 
Nevermind, I figured out how to get rougue P and I frames. And you are correct - the rogue frames do seem to cause write failures.

Chris
 
Svart said:
Then I counter, counter disagree! I'll go over this again, if I set Ptool to ONLY native 24p I cannot record with the STOCK settings(bitrate changes UNCHECKED IN PTOOL) on either a class 6 card or class 10 card, both of which have worked flawlessly for as long as I've had my camera. These are the stock settings and they will NOT run with the native 24p setting when capturing a static, high detail scene:

16,000,000
18,000,000
20,000,000

How can this be my cards? You are only looking at the high bitrate numbers I posted and have not read that I stated more than once that only enabling 24p(nothing else, no bitrate changes, nothing) causes card speed errors.

The fact is that the ability of the Sandisk cards to handle bitrate spikes is totally masking the fact that the native 24p setting causes extremely high bitrate spikes at any bitrate, including the stock bitrates.

At the high bitrates that I've tried, I've noticed that I can sustain 45mbit easily with my class 6 card and not get card speed errors. This means that there are NO bitrate spikes due to the fact that I never get an error even with sustained class 6 maximum bitrates into the card and can also shoot a static scene without issue. I can also increase the bitrates to the point where the class 6 card will fail due to card speed issues but the class 10 card will record fine. This also means that the bitrate written to the class 10 card is without bitrate spikes. It's all about overhead. We should NOT need to have significant overhead. This means that there is something wrong.

THE HIGH BITRATES WERE MEANT TO TEST THE CARDS TO THEIR MAXIMUM TRANSFER RATES to test their actual limits inside the camera, nothing more.

I'm not sure what else to say here. Maybe I'm just not explaining myself correctly?

Lets not get hung up on the high bitrate settings because those are a red herring to the root cause.

Those testing the Sandisk cards at very high bitrates are attempting to simulate running a slower card.
Click to expand...


I got the same problem. Am using a PAL GH1 and Native 24/25p is not working whatever bitrate am using. It's a BUG for PAL's users and not a question of class 6 or 10 or whatever... Car3o listen to people pls... lol
 
surfer030303 said:
I got the same problem. Am using a PAL GH1 and Native 24/25p is not working whatever bitrate am using. It's a BUG for PAL's users and not a question of class 6 or 10 or whatever... Car3o listen to people pls... lol
Click to expand...
Please be more specific about failure mode: stops recording with "card too slow" error, camera freezing, etc.?
 
surfer030303 said:
I got the same problem. Am using a PAL GH1 and Native 24/25p is not working whatever bitrate am using. It's a BUG for PAL's users and not a question of class 6 or 10 or whateverl
Click to expand...


Hi surfer030303, maybe i missed, can you share what you setting in ptools. Is it a native PAL machine? i just what to figure the exact problem.

PS. i am a PAL user also and happy with ACVHD patch and error free with class 4 SDHC. go pervious page for my settings.
 
zhaoyun said:
Hi surfer030303, maybe i missed, can you share what you setting in ptools. Is it a native PAL machine? i just what to figure the exact problem.

PS. i am a PAL user also and happy with ACVHD patch and error free with class 4 SDHC. go pervious page for my settings.
Click to expand...


Hi, my machine is a PAL GH1.

I am using these settings :

Version compare patch
3rd party battery
30mn limit removal
Video Bitrate Adjustment Simplified : 60
Overall Bitrate Adj : 62
Limiting Bitrate Adj : 70

All other boxes are not checked.
I am not fan of MJPEG because of the size and the 30 fps as I am in Europe with the PAL 25.


All working perfectly.
Excepted if I use the Native 24p/25p. If i use this camera is freezing or blocking after 1 or 2 sec.
 
May I ask the ages of the cameras for people where this is happening?

I installed the hack firmware on two GH1s, one that was purchased in the last six months, and one that was an original release model. I don't know if there are any differences in hardware or not but to my eye the newer one always looked better than my friends older one (wouldn't get the weird lines and streaks in higher isos and seemed to get less mud.)

Anyway, so far, fingers crossed, the patch with C settings and 24p native checked has worked
flawlessly in both static on a tripod scenes and hand held whip scenes on my newer camera, with both the lens stabilizer on and off with the kit lens. On a transcend 16 gig class 6 card.

With the very same card (exactly the same card not the same brand), put into the older GH1, the C settings worked handheld, but had the fail / freeze / had to pull battery reset on the older cam anytime shooting a static detailed scene on a tripod.

Strange.

Also, as others have reported, the resulting AVCHD file reports as 23.971 not 23.976 but I drop it into sony vegas as a 1920 1080 23.976 project & timeline and render out to any codec as 23.976 and all works well so far!

After reading this thread I was terrified that 24p would not work on a tripod but again it seems to be ok on my newer camera and not ok on my buddy's GH1 which he bought right when they first came out.

I have so far been overjoyed with this hack...I played some scenes out through a HD projector and almost pooped my pants. My 7D only friends are now jealous.
 
surfer030303 said:
Version compare patch
3rd party battery
30mn limit removal
Video Bitrate Adjustment Simplified : 60
Overall Bitrate Adj : 62
Limiting Bitrate Adj : 70


Excepted if I use the Native 24p/25p
Click to expand...


i think your setting of bitrate is little bit higher than camera can handle. not exact wording, please refer to thread

http://www.dvxuser.com/V6/showthread.php?t=213082

"D" setting with [50,56,60]. it is already enough, just my opinion. and of course with these settings i have no error together with native 25p. Let's try.
 
Blackout said:
I installed the hack firmware on two GH1s, one that was purchased in the last six months, and one that was an original release model. I don't know if there are any differences in hardware or not but to my eye the newer one always looked better than my friends older one (wouldn't get the weird lines and streaks in higher isos and seemed to get less mud.)

Anyway, so far, fingers crossed, the patch with C settings and 24p native checked has worked
flawlessly in both static on a tripod scenes and hand held whip scenes on my newer camera, with both the lens stabilizer on and off with the kit lens. On a transcend 16 gig class 6 card.

With the very same card (exactly the same card not the same brand), put into the older GH1, the C settings worked handheld, but had the fail / freeze / had to pull battery reset on the older cam anytime shooting a static detailed scene on a tripod.
Click to expand...


hi Blackout, may i know two have same menu settings? will you try to reset to default and test them again?

anyway, do you mean that hardware from difference places affect their performance, where did you two camera make in?

my camera was made in China.

Maybe someone can report this to vitaliy that to take a look of the hardware from difference places to see wheather affect performance or not.
 
zhaoyun said:
i think your setting of bitrate is little bit higher than camera can handle. not exact wording, please refer to thread

http://www.dvxuser.com/V6/showthread.php?t=213082

"D" setting with [50,56,60]. it is already enough, just my opinion. and of course with these settings i have no error together with native 25p. Let's try.
Click to expand...


He don't start same discussion as Car3o is doing with others... I've tryed lower bitrates first (a, b, and c) with Native24/25p and cam crashed or freeze... And you know what, I don't care about native cause the result is better with the wrapped 25/50i and especially when I am editing FHD (1980x1080) on EDIUS. However thanks.
 
My camera says is a ntsc version says made in japan I'll have to look at what his camera said, all other settings were exactly the same.
 
You must log in or register to reply here.
Back
Top