Thanks @johnnymossville i will, i just hope i can hack it

@adventsam Filming a live plasma monitor can be challenging. You may need to do some research to determine its native refresh rate, and set your GH2 accordingly.

Trying to decide which framerate to shoot at, i'm testing various settings including FM 2.0.. Except stability,are there any quality differences between pal hbr 25p and ntsc hbr 30p ? If not,i'll save some time from testing both(pal &ntsc modes) in each setting.. same goes for 720 50p and 60p...

Thanks for quick and informative response! I'm also leaning towards 30p (although i'm in a pal country) because i'm shooting for personal use (viewed on a pc monitor or TV with blu ray) and i like the more smooth motion of it...

concerning the VMM 80% and speeding it up in post...is it 20% or 25% in order to have final 30p? also,will the final 30p from speeding up have the same smooth motion as if i have recorded in hbr 30p but with better quality because it shares the 24p settings?

PS sorry for my english..

Ok now it's almost clear for me!does this happen even if i have set my camera in pal mode?80% VMM still records at 30p? As to my initial question,regarding quality differneces between hbr 25p and 30p,isn't this dependant on the each settings/patch we use? cause i see that many patches use different parameters for hbr pal and ntsc modes (3gop and 6gop respectively,for example).. Does this happen with FM too? and a last one..when you announced FM 2.01 you wrote that it has stability improvements and no or very small quality decrease..is there any quality decrease ,even minimal, from 2.01 to 2.02? ofcourse stability is the main issue but i'd like to know if there are quality differences and in which modes,so i can choose FM 2.0 in case i don't have stability problems... Thanks again!

@towi Shouldn't do. These settings relate to Time_Scale in the AVCHD standard. time_scale is the number of time units that pass in one second. For example, a time coordinate system that measures time using a 27 MHz clock has a time_scale of 27 000 000. time_scale shall be greater than 0.

This relates to Num_Clock_Ticks. So long as the transport stream time scale is greater than 0 all should be fine.

If you analyse a AVCHD header, in the PPS set you should be able to see the results of GOPx2 time under time_scale.

@driftwood & @LPowell I just tested Crossfire variation 2 'Green Screen matrix' set to 24h. It looks good but it shows up as 24fps in after effects not 23.98

@Botvinic Coarse encoding at extremely low light levels is not a "bug", it's an inherent shortcoming of the AVCHD encoder's 4:2:0 color depth. @charlie_orozco helpfully sent me his original test footage and permitted me to embed it here. I think it's a very good example of one of the most difficult shooting situations, a high-contrast scene with near-black shadow details. What's challenging is that enhancing the shadows in this case involves not only a technical gamma correction - it needs something of an artistic touch to render the coarsely encoded data in a naturalistic manner.

The problematic issue with shadow details is that the image sensor resolves them as full-color RGB data, where it should really be desaturating the shadows as they fade into black. In preserving over-saturated hues of shadow areas, the camera fails to account for the fact that to the human eye, pure blues and purples appear much darker than other shades that may be recorded at the same illumination levels. With care, this undesirable psycho-visual effect can often be corrected in post.

One the most significant distinctions in Flow Motion v2 is how it smoothes out low-level chroma noise while fully preserving luminance detail, both in shadows and highlights. This makes the AVCHD encoder behave more like the way human vision works: high-resolution perception of contrast combined with low-resolution perception of color.

Here is the original GH2 Flow Motion v2 test footage with near-black shadow details:

I used Adobe After Effects CS5.5 to produce this color-graded version with enhanced shadow details. No filters were used to add or remove shadow noise from the video:

@Botvinic The second clip is not an example of properly-exposed Flow Motion footage. It is an attempt to salvage the severely underexposed areas of the first clip. If you can contribute more sophisticated post-production salvaging techniques, I'd be interested to learn from your examples.

@LPowell Okay.

Why in other settings, shadows - good. And then - the dirt? So the problem in your settings :) I want those shadows http://www.personal-view.com/talks/uploads/FileUpload/e4/2071415771e37fc063005b9b9f9be1.png

You can do special for us (me and charlie_orozco) settings to "correct" :) shadows? Special Flow Motion, Lol.

I just tested FloMo v 2.02 vs Sanity v5. It appears to me that FloMo v2.02 is more contrasty, and also sharper.

Is this by design?

@Botvinic. People like @LPowell, @driftwood, @RalpB and others put weeks of work to make GH2 a better camera. They are doing it with the best of their knowledge and limitations of the camera capabilities. There are plenty of options to choose from. You don't like one, pick another that fits your need better. I don't know if it is a language problem or not but you are in no position to make such offensive remarks and demands of these guys like you are paying them for what they do. You are more than welcome to provide feedback for their settings but to demand that they fix it for you after they have explained the reason is ludicrous. If there was a way to fix it, they would have done it already. Please have some respect. It annoys the rest of us who read these posts.