Personal View site logo
Make sure to join PV on Telegram or Facebook! Perfect to keep up with community on your smartphone.
Please, support PV!
It allows to keep PV going, with more focus towards AI, but keeping be one of the few truly independent places.
GH2 Flow Motion v2 - 100Mbps Fast Action Performance & Reliability for Class 10 SD cards
  • 1036 Replies sorted by
  • I tested Flow Motion 2.01 first with the new Panny 25mm/f1.4 The only failures were with 720pSH from either Manual Movie or from Still setting pushing the red button. The subject was a large avocado tree in the wind panning slowly across it from under. One time the camera froze and I had to take the battery out to reset and no file was written in that case; other times failures gave a message and file was created up to failure spot. 720pH worked fine and pretty high quality. Using a manual lens, like Minolta 35mm/f1.8, works fine and I could not make it fail. Thus, it appears that an AF lens plus 720pSH with a subject that has lots of changing details may be too much for the camera and Flow Motion 2.01.

  • @crunchy Thank you! That alerted me to an oversight I made in importing the HBR video into Adobe After Effects CS5.5. The GH2 records progressive HBR videos into exactly the same 1080i file format as interlaced FSH files, and there is no explicit way for an editing program to tell the difference. As a result, After Effects naturally assumes that HBR files are interlaced, and interprets the footage as "Upper Field First", which causes spurious interlace artifacts. To correct this, I had to use AE's Interpret Footage dialog to set Separate Fields to OFF. That eliminates the interlace distortion in the HBR frame grab I first uploaded, which I've now corrected in that post. Here's two frame grabs for comparison:

    Flow Motion v2 1080p25 HBR mode, incorrect displayed "Upper Field First" image

    Flow Motion v2 1080p25 HBR mode, "Separate Fields OFF" image

    Low Light FM2 HBR 2X field bug.JPG
    1024 x 545 - 185K
    Low Light FM2 HBR 2X.JPG
    1024 x 545 - 207K
  • @LPowell, I have imported your HBR clip by using Avisynth script:

    DirectShowSource("LPowell_HBR_101354524.MTS")

    ConvertToRGB32

    and opened it with VirtualDub. The picture is now much better (see below pure 200% resize). I've used frame 50.

    LPowell_HBR_01.jpg
    1092 x 634 - 175K
  • Thank you! Now it shows "There was a problem loading this video", but I was able to load the original file.

  • Hmm, I was able to download the video from that Vimeo HBR link, even after I logged out of Vimeo. If you are unable to access it directly, you can go to my Vimeo index page and click on the HBR video:

    https://vimeo.com/lpowell/videos

  • @LPowell, I tried but it says: "Sorry but you do not have the proper permission to access this area of Vimeo.". :-(

  • @crunchy I pasted the Vimeo download link for the HBR version in between the two embedded videos in the post above. Just copy it into your browser's address bar to link to it.

  • @LPowell You mentioned that "the original HBR video is available for download from the Vimeo link". Can you state it more precisely where is it? I've found only 24P and MJPEG version.

  • It was. I added the cinegrain package to it. I absolutely love it.

  • Here are links to the original Flow Motion v2 low light video files previewed in the previous post. Unfortunately , Vimeo balked on compressing the HBR version into its online streaming format, but the original HBR video is available for download from the Vimeo link.

    Flow Motion v2 1080p 24H mode

    Flow Motion v2 1080p25 HBR mode

    • Download link: vimeo.com/43353433/download?t=1338757200&v=101354523&s=755c93b6e6ca720a1688fc3b17521719

    Flow Motion v2 1080p30 MJPEG HD mode

  • Flow Motion v2.02 Low Light Comparison

    Download link to latest version:

    http://www.personal-view.com./talks/discussion/3337/gh2-flow-motion-v2.02-spans-in-hbr-25p-24h-720p/p1

    Flow Motion v2 maintains its finest quantization quality even in dim lighting situations. These frame grabs taken from a smooth panning shot compare FM2's performance in 1080p25 HBR, 1080p 24H, and 1080p30 MJPEG HD modes. These videos were shot two-stops underexposed, illuminated by a pair of 75W incandescent bulbs. The video gain of each frame was boosted by 50% in Adobe After Effects CS5.5, and the frame grabs were cropped at 200% resolution.

    Flow Motion v2 1080p 24H mode, 200% crop: image

    Flow Motion v2 1080p25 HBR mode, 200% crop: image

    Flow Motion v2 1080p30 MJPEG HD mode, 200% crop: image

    EDIT: Thanks to @crunchy, I discovered a footage interpretation error that caused spurious interlace artifacts to appear in the original HBR screen grab I posted above. I've replaced that with a corrected version, which displays HBR image quality virtually indistinguishable from the 24H frame grab.

    Low Light FM2 24H 2X.JPG
    1024 x 545 - 185K
    Low Light FM2 HBR 2X.JPG
    1024 x 545 - 185K
    Low Light FM2 HD 2X.JPG
    1024 x 545 - 174K
    Low Light FM2 HBR 2X.JPG
    1024 x 545 - 207K
  • @EH_films Nice sky shots, was the graininess added in post?

  • I need HBR in detailed shots so I made a test with 24p and HBR 30p on a tripod. I uploaded directly the MTS files. Both are spectacular.

    BTW I discovered that the Vimeo codec from straight AVCHD 1080p sucks. Looks at the original mts files.

    116Mbps for 24p and 57 Mbps for 30p

  • I decided to take some shots this morning with the 2.0 patch. I used the 720p in a few places and didn't really notice any problems. Video was converted to 2:35:1 for that look...

  • I take it the aperture changes you referred to are produced by zooming the 14-140mm lens at a wide-open aperture setting?

    Zoom+Focus will induce error.

    Aperture changes will too, but don't need wide open. Bright daylight shots of trees in the wind...125fps, f11->f9.

  • @v10tdi I tried every kind of shutter-button focusing trick I could think of, but still couldn't find a way to provoke a recording error in 720p60 Creative Movie Mode in the "P" setting. I was using a Panasonic Lumix 45-200mm lens in OIS and AFS mode, and zooming occasionally to alter the aperture setting. I don't have access to a 14-140mm zoom, so if it's something specific to that particular lens, I don't have a way to test for it.

  • @v10tdi Thanks, I'll see if I can provoke recording errors with shutter-button focusing during 720p video shooting. I take it the aperture changes you referred to are produced by zooming the 14-140mm lens at a wide-open aperture setting?

    If it's able to save a non-zero file after being provoked to halt recording, the MTS file could provide useful clues.

  • @LPowell - I'm able to reproduce the error in 720p SH creative movie mode using the 14-140 panny lens. I usually produce write/speed errors when focusing (shutter half-press) or exposure changes (aperture) during filming. Sandisk 16GB Extreme 30MB/s Class 10

    On the flip side, the footage quality is spectacular.

    Let me know if you want the MTS

  • @karl Thanks for your detailed reply. This sounds like the same issue that @mpgxsvcd reported above, and that I was able to confirm as well. In my tests it occurred only when shooting 720p SH in Still-Frame P-mode with an auto-focus lens. I've observed no recording failures in any of the Creative Movie video modes.

    Since Still-Frame P-mode can't use 24H or HBR modes and doesn't give you direct control of shutter speed, I haven't tested it a great deal with Flow Motion v2.01. However, there is a workaround for those who find this fully automated mode useful. With Still-Frame P-mode, 720p "H" mode will work reliably at a 60Mbps peak bitrate, with image quality significantly improved over stock firmware.

  • @LPowell: I shot the 720p60 samples in "Stills P-Mode".

    I tried recording the same scene 3 times in a row, it stopped in all three cases, the first time after 8 seconds, the second time after 15 seconds, the third time after 12 seconds.

    Since I had to revert the firmware due to the 720p60 issue anyway, I decided that I could just as well use the opportunity to take some more shots in 24H, first with FM-2.01, then with GOP3ZILLA-MAX_Standard_V2_BETA5, to do some image quality comparison.

    I merged some test shots in 24H at ISO 160 (the tree), at ISO 3200, 6400 and 12800 (just some dark corner of a hallway with some stuff) into a short video, with the patch settings side by side.

    I did not apply post-processing to the ISO 160 shot, but to the ISO 3200/6400/12800 shots I applied a spatial/temporal noise reduction filter, a level/gamma correction and a bezier-curve based desaturation of the darker parts, choosing the filter parameters such that I liked the FM 2.01 recorded footage best, then I copied the filters including all parameters to the video track that I had recorded using GOP3ZILLA (which gives the latter some disadvantage with regards to fitting my personal preference, but I wanted to use the same parameters for a better comparability).

    Of course, everything but the ISO 160 shot were extreme conditions where the result is far from being ready for the cinema... ;-) - but I just wanted to know how the many adjustments in FM 2.01 work under these difficult conditions.

    The screen shots that I appended to this post were taken from frames that I considered "fairly comparable" - I tried to choose frames where both settings deal with the same (low but not zero) amount of motion.

    I think it is not easy to decide what actually looks better, from the ISO 160 and ISO 12800 shots I could not assign a winner. In the ISO 3200 and 6400 shots, I think GOP3ZILLA retains a little more details, but it also has a little more contrast, which may or may not be a good thing. In the end, it's probably a matter of taste - and others may have preferred other postprocessing settings, of course.

    fm2_vs_gop3zilla_iso160.jpg
    1920 x 1080 - 1M
    fm2_vs_gop3zilla_iso3200.jpg
    1920 x 1080 - 444K
    fm2_vs_gop3zilla_iso6400a.jpg
    1920 x 1080 - 426K
    fm2_vs_gop3zilla_iso6400.jpg
    1920 x 1080 - 579K
    fm2_vs_gop3zilla_iso12800.jpg
    1920 x 1080 - 416K
  • @karl Thanks for your test report, I'm familiar with those kind of windy conditions and with the info you provided I can reproduce your testing setup. Was this 720p60 only in still-frame P-mode, or in Creative Movie P-mode? Did you see it halt just once, on sporadic occasions, or repeatedly under the same conditions? Thanks, these details are very helpful in pinpointing the issue.

  • Being one of those who had reported aborted recordings with FM 2.00 / 720p60, it took me a few days until the weather allowed to retry with FM 2.01 - but today there was sun & wind, again.

    Alas, I have to report that FM 2.01 failed again, stopping the recording after only 8 seconds (on a freshly formatted SanDisk 64GB 95MB/s).

    Find attached a screen-shot of the scene (just leaves of a tree moving in the wind, sun shining, GH2 mounted on a tripod), plus an animated GIF showing 12 frames near before the recording aborted. Recording parameters: 720p60 SH, shutter 1/200 (mode P), aperture 4.0, lens Panasonic Vario X PZ 14-42mm, f=~35mm was used, AFS.

    If you would like to have the .MTS file (70 MB), too, please tell me where I could upload it (I don't have a vimeo account or alike).

    fm2_tree_fail.jpg
    1280 x 720 - 446K
    fm201_fail.gif
    640 x 360 - 3M
  • @CurtisMack I use Smooth Film Mode for daylight shots and Nostalgic for incandescent lighting, both set at -2,-2,-1, -2. However, I didn't shoot the Shadow Detail footage above, that was contributed by @charlie_orozco

  • @LPowell. Nice work. Which film mode (Nostalgic, Smooth, etc. )did you use to open up the shadows?

  • @mpgxsvcd It would be very helpful if you could send me original MTS footage of a succesfully recorded video shot under conditions where you've seen the camera fail. Shooting extremely detailed subjects with a Panasonic 45-200mm f4-5.6 lens in "P" Still-Frame mode with both OIS and AFC auto-focus, I have been unable to reproduce any recording errors in 720p60 or 720p50 SH or H modes.

    In broad daylight, "P" mode can often select undesirably high shutter speeds well over 1/125 second, which produces sharply-etched frames with virtually no motion blur. So far, I haven't been able to provoke Flow Motion v2.01 to fail under these conditions.

This topic is closed.
← All Discussions