75Mbps GH1 Peak Reliability Patch - V2 update

Just so you know, they're right on the edge of giving me write errors. With the "Crunchy test" I can force it if try hard, but outdoors with my "foliage of death" test, I never have a problem
 
evanflys said:
Just so you know, they're right on the edge of giving me write errors. With the "Crunchy test" I can force it if try hard, but outdoors with my "foliage of death" test, I never have a problem
Click to expand...

What's the "Crunchy Test"??
I just use my version of the foliage test with some brightly colored stuff animals and pan, and/or zoom. Just the slightest zoom, caused the original V2 patch to crash in SH.
Off to try the new settings.

EDIT; just went out and repeated my test-same exact thing-crashes on zoom. even in 23-point auto, or manual focus-doesn't matter, still crashes in SH mode.
 
Last edited:
Here's the crunchy test. I put it up on my monitor, set the camera on a tripod and start filming. I push it to the limit and then review it with Cbrandin's Stream Parser.
 

Attachments

  • Crunchy_Chart02.pdf
    11.6 KB · Views: 0
evanflys said:
Here's the crunchy test. I put it up on my monitor, set the camera on a tripod and start filming. I push it to the limit and then review it with Cbrandin's Stream Parser.
Click to expand...
Ok, thanks. I think I'm going to stick with my stuffed animals outside.
I just tried your settings, and they crashed on me in SH. I lowered down the overall to 50, and 30 in FHD/SH, and it worked fine-no crashes.
Now I'm going to try the 75mb patch, am going to leave fhd/sd the same-50, and change H to 35 and L to 30. I just realized that H, is still 1280/720-60P, it just drops the bit rate. and, I'm discovering that at around 35mb/second, that's it-it's done, and crashes. I cannot reliably get 40mb/sec in SH mode. I can get 30mb/sec in SH mode-but I wanna try and push it to 35mb/sec.
I really don't need to mess with any of the other settings, as they are working fine for me. So, if 30mb/sec is all I'm going to get at 720P/60, so be it-that's still twice as good as the stock firmware.

EDIT; Final testing-It appears that FHD/SH are linked, so you really don't want to change that from 50xxxxx. I tried setting H to 33xxxxxxx, and that worked for a little longer, but still crashed. SH crashes almost immediately upon zooming-so it's useless. Data spikes of up to 44mb/second will not work in 720/60Pmode. Even when it was set to H at 33xxxxxxx, I still saw data spikes higher than that, which caused the crash.

So, here is what I have set now, and it is very stable in 720/60P mode; FHD/SH-leave it alone, H mode=30xxxxxx, L mode=25xxxxxxx(you can set this lower if you want-doesn't matter).
I shoot 720P in H mode, and the data rate may spike a little over 30mb/second-but rarely, and not by much, and it will not crash.
Even with the crunchy test. Whereas, the SH mode, will spike to 44mb/sec and crash almost immediately.
Everything else is stable.

I never messed with the GOP. It may still be possible for someone to figure out a higher bitrate patch, for 720/60P, but I haven't found one yet, nor have I found a whole lot of people that are even interested.
 
Last edited:
havasuphoto said:
So, here is what I have set now, and it is very stable in 720/60P mode; FHD/SH-leave it alone, H mode=30xxxxxx, L mode=25xxxxxxx(you can set this lower if you want-doesn't matter).
Click to expand...
Thanks havasuphoto, for testing out the use of H mode as a moderate bitrate alternative to SH mode. In my testing, I found the reliability of 720p60 video significantly improved with H mode bitrate set as high as 46000000. However, as you discovered, it's not completely bulletproof, even when set as low as 33000000.

Note that H mode is already set to 29000000 in the current version of the 75Mbps Peak Reliability Patch. I tweaked that setting to insure reliable recording of extended takes spanned across multiple 4GB MTS files. Since that is only a bit lower than the 30000000 setting you ended up with, other users may want to try the existing H mode patch setting first to see if it meets their needs.
 
lpowell said:
Thanks havasuphoto, for testing out the use of H mode as a moderate bitrate alternative to SH mode. In my testing, I found the reliability of 720p60 video significantly improved with H mode bitrate set as high as 46000000. However, as you discovered, it's not completely bulletproof, even when set as low as 33000000.

Note that H mode is already set to 29000000 in the current version of the 75Mbps Peak Reliability Patch. I tweaked that setting to insure reliable recording of extended takes spanned across multiple 4GB MTS files. Since that is only a bit lower than the 30000000 setting you ended up with, other users may want to try the existing H mode patch setting first to see if it meets their needs.
Click to expand...

You took the words right out of my mouth. leave the standard H setting alone-it's fine at 29xxxxx, so you don't need to mess with it. there is nothing to be gained by going any higher.
I had seen peaks as high as 46mb/sec-and it didn't crash. but, I also need to experiment with the shutter speed of 1/60th. all of my crashes were at 2x frame rate, 1/125th, which apparently stressed the codec more, and causes more detail to be rendered by the codec.
so, if I can use SH at 1/60th, in my "stuffed animal" torture test, that may work.
 
For us PAL 50p people, SH mode is much more stable than the discussion above in 60p, so don't be afraid to use the SH mode, it's 99% as reliable as the 40Mbps reliable patch.
 
The only difference between SH and H is you have different bit rates right? I always shoot in SH and have H just as a back up.

I never shoot in FHD/1080. I need 60P. I also need 1/125 shutter for the ability to give nice propeller blur on the aircraft I film. I've been really happy with the adjustments I've made to lpowells awesome patch.

Tim
 
So, I've put the new 75Mbit v2 firmware to my GH13 and everything is great. One interesting observation however is that when I bring the footage into FCPX and I check the inspector, it reveals that the clips I have brought in are 1920x1080 at 29.97fps - not 24fps!!
I'm pretty sure I had the latest version of Ptool and .ini file from Lpowell.
Anyone else experience this...or maybe I'm thinking FCPX doesn't know how to read the modified files?

paul
 
pchristoph said:
...when I bring the footage into FCPX and I check the inspector, it reveals that the clips I have brought in are 1920x1080 at 29.97fps - not 24fps!!
Click to expand...
The 75Mbps Peak Reliability Patch records 1080p as interlaced MTS files with 3:2 pulldown. That embeds the 24p frames within a 29.97fps interlaced video stream. FCPX is reporting the frame rate of the stream rather than the video.
 
I imagine you've already tested this, but, what would happen if I were to just check the "native 24P" both, with this patch??
 
lpowell said:
The 75Mbps Peak Reliability Patch records 1080p as interlaced MTS files with 3:2 pulldown. That embeds the 24p frames within a 29.97fps interlaced video stream. FCPX is reporting the frame rate of the stream rather than the video.
Click to expand...

Ah, that makes sense. I'm not used to interlaced/pulldown stuff, but now with fcpx I don't really care :)

I also wanted to personally thank you for your determination and continued efforts in testing and providing camera settings that make the images I capture for storytelling with this camera better than I could have imagined. A respectful hat tip to you sir lpowell.
 
lpowell said:
It magically turns into the 75Mbps Peak Fatality Patch!
Click to expand...
ROFLMAO!!!
I compared this patch with the blackout/powell patch, and the only difference I see in FHD/SD mode is....well, not much. Both are at 50xxxxxx. But, the blackout/powel has the 720/60 GOP set at 12 Vs. 25 for the 75mb/sec patch. and 15 vs. 12(75mb/sec patch) in 1024 mode. So, I'm thinking that if you go below 15 with native 24P checked, that's no good?
So, thinking that a GOP of 12 is better than 25, I'm going to try the blackout/powell patch again(720P/60). Only thing I changed with in H mode, I raised it from 28xxxxx to 30xxxxxx.

I hate being "late to the party", and "not studying" when you guys were creating and testing these patches. Just got kinda lost in the ether at some point, and it all started to just sound like blah-blah, to me. And, I was waiting for "new" hack for the newer models, and blah-blah.
 
With the GH1, average bitrate is typically around 40-50Mbps for all three high-bitrate patches. The peak bitrate is where the patches differ. The Blackout-Powell Patch has a peak bitrate of 55Mbps, compared to the 75Mbps of the Peak Reliability Patch. GOP-sizes are tweaked specifically for each video mode in each patch and optimized for highest reliability.
 
Sounds like this patch (75 Mbps) would be the one to use for slow-motion eh? Given that it is the highest data rate when shooting at 720/60p?
 
Yeah , actually, wouldn't this be better than the Blackout-Powell patch for slow motion? Is the only difference that 75 in FHD is interlaced? But wouldn't that be irrelevant because you're switching firmware anyway from 100 to whatever you use for slow motion. Is it that BP is a self contained patch that has both options so you don't have to change firmware?
 
Last edited:
This patch delivers poor video quality in 720/60p. The GOP is too long. The codec in the GH1 accumulates visual errors over the length of the GOP. The GOP should be less than 14 frames long to avoid noticeably degraded video quality.

Here are short clips illustrating the difference. The two clips were shot with identical camera settings: ISO 800, 1/60, sharpness=0.

lpowell_p75v2_0.MTS
my_27M_GOP10_0.MTS

Look for the pulsing in the detail on the wall. That pulsing looks really bad when I shoot skin and hair.
 
Last edited:
You must log in or register to reply here.
Back
Top