Butt Im aware of the first few frames issue but this Its not the same its almost a continuous pulsing breakup and this image is a grab from around 1 min. Will try out your new settings when I get time.
@Mimirsan Do check all your settings carefully, as many times when testing different settings I changed one little thing, the video laid down perfect while shooting but played back with the pulsing you describe.
First off your settings above for 24H are breathtaking, I couldn't break them so far. Beautiful and incredible data rates. 57900 average on very high detail. Some I-Frames reached 740kb
The FSH 1080i 60 worked also but gave me slightly lower bitrates 40838 max. I could not make it crash also which makes me very happy.
However SH Crashed every time by couldn't write to the card fast enough error but contrary to before the data was still saved till that point which previous patch attempts locked the camera leaving the files on 0.0kb. Now It crashed after 4-5 seconds on lots of detail. So 60p 720 crashes for some reason and the average bitrate is even lower than 60 i 1080. SH gives me a 37,607 average for the files. It looks very good I would say better than stock by a long shot, no visible blocks but the crash might be based on buffering/processing problems since the card can write the higher data rates of the other two no problem.
tested video at ISO 12800 - world of difference average bitrate 70.5mb
Oh yeah, take a look at second image. Grain retention was best I have ever seen from any dslr clip. Oh yeah, maybe 93.7mb is doing that. I'll upload a sample.
kae I dont touch a thing...just loaded the patch and tested in areas that have known to give me card errors I was just leaving my findings from butt's settings with 720p mode Ive been using your recent one with no problems at all...and looks great btw
@Butt I tried your 32mbit 750p50 patch and the average bitrate is 32mbit but the quality of the footages is very low, with low details and pulsing images. I think that with 50p we have to use 6 gop. Do you have any optimized setting for 50p with 6 gop and higher bitrate?
Other problems: videolan usually can stream the first seconds than it freeze, i have to use other players and streamparser also shows evident difficulties to playback the footages
Version increment=2 30min limit removal=Checked PAL<->NTSC Menu=Checked Video Bitrate FSH/SH=42000000 Video Bitrate FH/H=35000000 Video Bitrate 24H=60000000 Video Bitrate 24L=35000000 720p50 GOP Size=6 720p60 GOP Size=6 1080i50 and 1080p24 GOP Size=3 1080i60 GOP Size=6 Video Bitrate 24H ADD=60000000 Overall Bitrate=60000000 Overall Bitrate 2=48000000 Video buffer=0x3000000 Video buffer 24p=0x3600000 1080p24 High Top Setting=42418 1080p24 High Bottom Setting=29692 1080p24 Low Top Setting=31178 1080p24 Low Bottom Setting=21824
I tried kae's settings and they seems to work well, but i think that b frames are too small, then details are not excellent. 1080p is really good, 720p50 looks good too and 1080i50 is definitely worst. Good job guys!
Guys thank you all for testing! It just confirms what I am seeing on my own, my last settings (and I will attach them again) below) for 1080 24P are the best I have seen from the GH2. Please understand I did not spend ANY time tweaking or testing the other settings for FSH or SH or 720P I just included them from butt's (I think) and put the GOP for those at 6. So indeed SH may give write errors for some even though I haven't experienced that. I am hoping others will come up with much better settings for 1080i and 720p but, I reiterate, I have not spent ANY time on these as I do not use these settings.
But I have spent probably 30 hours testing 1080 24P mode from a visual director's point of view and I am totally thrilled with the "look" of the 1080 24P 3 GOP I get with these settings. The motion is amazing, it ingests perfectly into Avid, there is the 10 frame glitch in the front of each clip but I can totally live with that. I am doing a medium budget ($12 million) feature in Italy next spring and plan on using a bunch of the GH2s as B cams for action sequences (that's why I was so anal about the look of the motion). I think I will have no problem using these 1080 24p settings for eventual blow up to 35mm. I wish it was 4:2:2 but you can't have it all. I would try an I frame only version of this 1080 24P hack but so far I cannot manage to get it to work at these high data rates and GOP 2 doesn't work at all. So until someone tops these settings or manages a higher data rate at 3 GOP (Vitaliy?) I am done testing at 1080 24P. But I encourage others to make it better. Again, Vitaliy is a genius who works tirelessly on behalf of all artists in the community and we are grateful!!
Note: To anyone worried about the size of the b frames while shooting the test chart - they will be SMALL by design because there is no motion. Just go outside and shoot high detail footage and move the s**t out of the camera and trust me, you will see huge B frames.
Note #2: To all GH2 users please after you flash go out and shoot real world footage with these settings to see how you like it for the normal kind of work you do. I don't mean to be snarky, but all these guys that just go out and shoot trees or test charts or static shots with Zakuto Shootout style testing procedures are just wasting time IMHO. 99% of what you get PAID to shoot will have nothing to do with these kinds of shots. The last director who spent a lot of time shooting static trees was Antonioni in 'BlowUp' and as much as I loved that flick, it died at the boxoffice.
@kae: I'm sorry, but my eyes see no difference between the original and the hacked settings . Maybe just a placebo effect? Show me the difference between stock settings and hacked settings.
@Angry_C I cite @Ian_T: "It’s pretty much what most of us expected (and wanted). Static shots were already sharp. It’s that little bit of mud in motion that we want to get rid of (which apparently is gone). Not only will a higher bitrate help the compression artifacts in 720p but also 1080p when it comes to shadow detail. When it comes to the GH-1 (and basically most CMOS cameras...not only DSLRs) I’ve always hated the murkiness/muddy-look in the shadow areas especially in green colored leaves in trees etc. The fact that the image now looks noisier after this hack on the GH-2 means it is allowing or squeezing all of the detail it can get out of the image. Now...we have control over what we want to do with it and not leaving it up to the camera to decide internally. I remember commenting on the noise and shadow detail from some Ninja footage. If we can do that without having to buy an external HDMI recorder...then it’s gravy from here.
Another benefit I see is...less macro blocking. In Vegas, when it comes to highly compressed images (without looking at the actual image), I can see macro blocking on the scopes. The less compressed these images become the less I see macro blocking on the scopes. It will also help color correcting big time. You will be able to push the colors a little more. I’m not sure yet if 42Mbps is a significant change...but the more the merrier.
I'd much rather noise from the sensor than compression artifacts any day."
and @Angry_C: Nobody forces you to jump on this train
I really would like to jump on this train, if someone shows the evidence. Until this, in my opinion everything is subjectively. I did a lot of tests and i´m a pixelpeeper, but i did not find decisive differences.