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.
Official Low GOP topic, series 3
  • 1008 Replies sorted by
  • chefchef
    Did this with the "kinda-old" reAquainted from @driftwood 14-42mm kit lens and a 50mm Nikon f1.8.

  • Swiss_BoySwiss_Boy
    Shot this video with Aquamotion V2 and for now i'm sticking with this patch i think.

    Feedbacks would be apreciated

  • svartsvart
    @csync: I've seen the blocky red/blue noise on my camera with pretty much every GOP1 patch I've tried. I think the smoothing nature of AVCHD compression has hidden this from us up until this point.
  • Zaven13Zaven13
    I went to the beach in Southern California for some test shots with GH2 yesterday. It turned out to be a foggy day so I tested GH2 in the fog. I quickly assembled the clips in the attached video uploaded in Youtube. I used Driftwood SeaQuake 24H with Panasonic 14-140 lens in cinema mode. Video was shot handheld without stabilizer or tripod but still ok. Please remember I do video for hobby, it is not my day job. This is a different winter from @mrsquirrell's snow shots earlier. There is no post processing and video resolution is reduced for Youtube upload. Select 1080p playing mode in Youtube player.
  • shianshian
    @csync What's the file size? I have dropbox.
  • csynccsync
    @shian - it's actually a bit long, around a 1m30s. My only way of explaining it outside of sensor issues is that my CFLs are so poor with their light quality that the GH2's white balance increases the gain heavily on the red channel - that or some severe issue with Quantum 5. I'm going to run a few more lighting tests in a little while, and I'll see if it persists.

    If you have FTP somewhere, I can upload all of it, but it would just take a while. I'll also check to see if I have a smaller clip exhibiting the same issues (I probably do).
  • shianshian
    @csync how long is the clip? I'd love to download the MTS file and hit it with ColorGHear and see if it's strong enough to tame that artifacting cuz it's REALLY bad... I've never seen noise that bad on the GH2.
  • Mark_the_HarpMark_the_Harp
    @No_SuRReNDeR Love the look of those screengrabs.
  • No_SuRReNDeRNo_SuRReNDeR
    I just cant afford to buy a bunch of 95MB cards so I find Aquamotion is a good reliable and high enough quality vs storage space patch. Seems to work great on all the cards I have.
  • csynccsync
    @FGCU I'll try Quantum 2 with the same lighting and post some results.
  • Swiss_BoySwiss_Boy
    @FGCU does Aquamotion V2 also has this noise grain issue you reported for Quantum V5 ?
  • csynccsync
    @proaudio4 - yes, but this was shot at 400 ISO, which I think is bug-free.
  • proaudio4proaudio4
    You do know about the ISO bug, right?
  • csynccsync
    I've noticed for a while, especially at any ISO higher than 320, that my GH2 seems to have a lot more noise than most others I've seen. Here are two screenshots, taking from an MTS file viewed with ffMPEG natively. The noise I'm referring to is very obviously found on her arm (image left), it looks especially red and blocky. Does anyone else have the same noise? Even at 640 I often get some colored bar banding running horizontally across the image. I'm considering sending it in for a repair, but obviously want to make sure I'm not just seeing things [that aren't there].

    These were shot with driftwood's quantum 5 patch (GOP1). 400 ISO, 1/50th shutter. 1080/24p.

    I couldn't get my ProRes 422 (HQ) export to work from FCPX, so this is whatever their encoder spits out on its "Vimeo HD" setting:

    GH2 noise sample from csync on Vimeo.



    password is: GH2
    Screen Shot 2011-12-31 at 7.56.40 PM.png
    1920 x 1080 - 2M
    Screen Shot 2011-12-31 at 7.56.33 PM.png
    1920 x 1080 - 2M
  • No_SuRReNDeRNo_SuRReNDeR
    Been shooting AQuamotion 100MB for a feature I'm working here are a few test grabs from the screen tests I did yesterday... I shoot all these nostalgic -2 all the "grading was actually done by duplicating layers in FCP and add a 3 way CC to bottom layer I blend the toplayer with soft light on the top layer or for extreme contrast hard light as seen in middle pic... where she needz to look all CRAZY...lol --- See last pic
    look at me.png
    1920 x 1080 - 2M
    crazy.png
    1920 x 1080 - 1M
    couch2.png
    1920 x 1080 - 2M
    Screen shot 2011-12-31 at 3.27.11 PM.png
    1440 x 900 - 529K
  • sohussohus
    Let's continue this (Great) discussion over here:
    http://personal-view.com/talks/discussion/1888/gh2-post-production-workflows
    Can @vitaliy_kiselev please move the posts above over there?
  • pinger007pinger007
    Unfortunately, Media Composer 6.0 is a broken NLE when it comes to their promised AVCHD AMA support - it simply doesn't work (even on approved systems). There have been countless complaints (most of which I've experienced myself) regarding AMA lock-ups, gamma shifts upon AVCHD import/transcode, and generally slow performance compared to 5.5 and 5.0 (I would even go as far as saying that version 4.0 was faster and more fluid). Until Avid fixes these issues with patches (sooner rather than later would be nice), I would suggest a Premiere workflow, or reverting back to Media Composer 5.0 or 5.5. It's a shame... really would have preferred a polished product and not a rushed application...
  • towitowi
    @rozroz
    of course you can simply import the MTS files into Avid MC (at least with MC Version 5 xy... not quite sure about Version 6). But all clips will have the same timecode and they have no reel name assigned.
    For further export/roundtrip via EDL, AAF etc. reel names are mandatory (as Avid always refers to reel names, not to clip names). Unique timecodes for each clip also help a lot. This is why I first convert to QT, batch rename the files and then modify the clips in qtChange: I assign reel names (I simply assign the clip name as reel name... this is why I first rename the clips) and use the shooting time as timecode. These modified QT files will be imported into Avid MC with DNxHD 10bit finally.
    It's really easy... and safes a lot of work later on.
  • sampledisampledi
    @sohus
    @towi
    Panasonic AVCCAM Importer won't help with these MTS files. MC6 simply have issues with AVCHD that range from weird characters in transcoded MXF files to crashes during playback..... + you won't have proper tape ID and timecode that way.
    There are couple of ways how it can be done.
    A) The most expensive and the most fluid is Assimilate Scratch. Simply place all AVCHD files in new Construct, type in desired TapeID, set it to re-generate timecode and render out DNxHD MHX files. Place those files in Avid Media Folder and bring them in with AAF files that were generated by Scratch. This method would give you fast transcode directly to Avid MXF, proper TapeID and continuous timecode. Of course with price range from 5 to 17K $, this is not realistic option for "indie" GH2 workflow.
    B) All other free options include re-wrapping of MTS files. You would use something like FFMPG, FFMBC (http://code.google.com/p/ffmbc/) or similar. Re-wrapping can be done instead of copying files from SD card. That way you won't loose any time (data is going from SD card to HDD in different container), and you'll have same clips in different container (MP4, MOV), that more programs can read.
    - Resolve Light (free), in new version can export DNxHD MXFs. Bring your files into Resolve, give them TapeID, Timecode and render out MXfs, or
    - You can AMA re-wrapped clips in MC. From some reason they will perform better compared to MTS, but you will have to transcode anyway (do not forget that AMA>transocde is much faster than Import>Transcode).
    - You can also use QTchange before importing clips into MC, to give them proper Timecode and TapeID, however I had some issues with that method because files were not interpreted correctly.
    I'm still exploring best workflow for GH2 material with many different applications. Native editing (Premiere for example) is nice but it is not realistic option for long form projects and for situations when you have to do CC or finishing in another tool. Also responsiveness during creative cutting is often much more important than instant editing.
    This is probably too long post for this topic and should go in some separate section where we can discuss GH1/2 post workflows.
  • rozrozrozroz
    @towi
    why not import to a high DNxHD codec?
    why all this workaround?
  • darkman1983darkman1983
    @inhausegoods
    I like your Video ^^
    Is it graded?
    Settings, more light sources?
  • inhousegoodsinhousegoods
    Quick video I shot using Driftwood's SeAQuake patch, can not be grateful enough for how far the hack has gone! Thank you Driftwood and Vitaliy! All of the stills are screenshots from the video

  • towitowi
    @sohus
    You need this QT plugin: https://eww.pass.panasonic.co.jp/pro-av/support/desk/e/download.htm#avccamip
    This plugin enables QT to playback the MTS files... therefore Avid MC can link to your MTS files through AMA (the regular QT AMA plugin, which is installed by default).
    Editing with MTS files is a nightmare as it is _extremely_ processor intensive. I'd recommend to convert to QT first, then modify the files with "qtChange" (to assign reel names and unique timecode, for instance the timecode of the shooting time... however qtChange is Mac only) and then import the converted + modified files into MC (or link with AMA).
  • sohussohus
    Who's working with Driftwood's footage and Avid Media Composer 6? I am having problems linking to it with AMA. I get all kinds of hangs and errors. If I convert using clipwrap to ProRes/DNxHD I have no problems using the footage. Any thoughts? I am using the latest version, Avid 6 in trial mode.
  • mrsquirrellmrsquirrell
    Thanks very much for your lovely comments, I was kept warm by a few.... coffees laced with schnapps :)
This topic is closed.
← All Discussions