Hi guys, I just got the GH2. I used the GH1 for the past year and loved it but I needed the live view for a client monitor. I loaded cbrandin's settings and the images looks great when played back in camera and also on a 48" HDMI TV. But when I load the files into FCP 6 I get a horizontal glitch whenever the camera moves. I just want to make sure the files will be ok when I pass them on to the client for post. Any ideas?
1. STOCK 2. 66M AQ2 CHRIS AUG. 29th 3. 88M AQ2 MAX VAR STRAY
All conditions are constant: Light: Daylight Lamps f-stop: f/5.6 ISO 320 Shutter: 1/250 stock 42 Camera reports 3 stops under exposed Motion tests were done on a motorized tripod base. The speed control for motion was fixed and the same for all. _________________________________________________
Stock: min i-frame: 420K max i-frame: 476K ave p-frame: 174K ave b-frame: 47K
SUMMARY AND FINAL THREE WAY ANALYSIS IMAGE (STATIC)
Based on the amount of detail, low light images can suffer. Detail scenes such as landscape with trees and grass will ask for a higher bitrate to resolve the complex fine detail. Shadow detail will be the first to go which causes detail loss and smearing from macroblocking in the shadows. I chose to shoot this test on my bass traps front cloth. The cloth has "some" fine detail which forces a higher bitrate. Granted, the bitrate is not at it highest limits, but is reasonably high enough to show differneces between the stock 22Mb/s settings compared to 66M and 88M. Both 66M and 88M are real close in this example. The stock setting falls short here as you can see.
Check the ALL THREE COMPARE.png static image file for a quick three way comparison.
@cbrandin As has been pointed out the deathchart at the moment really needs some colour information. Quickly this morning I made this, it is modifiable if it isn't dense enough. I've made it not as repetitive as it seems too (based on how the codec looks for similarity). Is this good enough or should there be more lines at less width ? Edit : added a denser version and something a bit more random.
> Please re-read my post. Again, the camera should not crash upon any setting the user chooses in the menu. If the stock GH2 did this, not many would buy it.
Maybe you should re-read MY posts:
"I wasn't talking about reliability" & "(and of course reliability is crucial too)"
Somehow the two of you got so defensive that you simply didn't read what I wrote. Maybe you missed this as well:
"thanks a bunch for nailing these settings for the rest of us."
> We're not here to talk about settings
stonebat _asked_ me about using Chris' settings (I realise now it was only to score a point, but that wasn't obvious to me at the time).
I've been testing driftwood's 55M 1080 60i settings, and there is a unique problem I have not seen on any of the 24P patches. The noise varies in a three frame cycle - Frame 1 has high resolution noise (good), Frame 2 has blurred noise (bad), Frame 3 has blurred noise (bad), and then the cycle repeats.
Here is a Photoshop TIF with 4 layers, each layer being a consecutive frame. This is a 1:1 crop at ISO 6400. As you turn the layers on and off, you can see the changes in the noise. Look in the orange area of the far building and the greenish area of the near house.
This 3 frame cycle is not unique to driftwood's 55M. Chris's 32M 1080 60i also has it. It's obvious that interlace is a different animal. And this is definitely noticable when you watch the movie at speed. The picture really does appear smeared because the blurred frames outnumber the clean ones 2:1.
I ran these clips through stream parser and there is no indication that anything is askew. This is one of those times where real world testing is critical.
Thanks Raph. This is great information. Now, how is this happening?... hmmm strange. Ralph, can you check stock 1080 60i? Also, you are not seeing this in progressive modes?
Progressive mode is clean. This is an interlace problem only.
RE: stock mode - I examined some pre-hack nighttime shots and I do indeed see something similar, EXCEPT it's one clean frame follwed by fourteen smeared frames - in other words, the GOP 15.
What's wierd with the current problem is neither of the settings is a GOP 3 - Chris's 32M is GOP 15 and driftwood's 55M is GOP 30.
Wow.... strange indeed! Since the issue is occurring with stock settings, I wonder if it's worth mentioning this to Panasonic? Or, possibly Vitialiy, Chris, or someone may have an idea.
Can we analyze why these spans while other's dont? Has it to do with datarates, card speed, AQ, GOP settings? Or is there something that @Vitaliy_Kiselev needs to change in the next PTool release?
I use an old setting that @vitaliy suggested at the very top of this topic. I know, it probably doesn't give all the nice values as the new tweaks do, but the images look good to me and the files are spanning at 24H:
44/35 gop12 aq3
Nothing else patched.
EDIT: even 50i runs at 35mbit/s. Not as nice as 24p but better than the original setting.
@neveraholiday I can't find the @vitaliy settings you are refering to in the top of this topic. I only find a suggestion from him to try GOP 24. I understand that the only patches used are 44/35 gop12 ag3 for 25H and 24L, but what are the 50i and 50p 35mbit/s settings you are using. If you could share the ini please. I am currently mainly useing Cris 44/32 settings.
@stonebat mentions below to stay below 44. Maybe that is how I assembled this setting? Tricks of the brain?
I attach my ini. But I suggest, you stick to @cbrandin's settings, as they are all tested throughly. The ones I got are not, as I work on a mac and don't have the software to stream parse and what else. Only thing I am saying is, I like the image that is coming out and the files are spanning. i50 FSH with 44M is not working – only FH.
@Ralph_B Nice testing mate. Awesome. What would you say if I told you we just found another 14% performance increase in i frames and lower bitrate for GOP1 ?
I'll be damned if I can get 1080/60i to work on GOP1 - shame cus reading your smear test I have to agree. It seems just as soon as I fix 720p60, 1080i60 goes crud on me. Ive got every other setting working on GOP1 bar that bleeder... I'll keep trying... :-) May have to try a GOP30 on it for now just to enable people to use it and with less smears. The problem it seems is 1080i60 is remarkably underpowered - by the buffer charts that is. So I'm trying very hard to balnce out the bitrate between 720p60 and 1080i60, bloody ridiculous. 108050/720p50 is fine!
@Ralph_B Have you noticed that whenever youre testing & you press record if the lcd goes slightly green you know its going to fail. When it happens I just move on to the next setting now without even bothering to check the charts and analysis!