Jump to content

Sage

Members
  • Posts

    659
  • Joined

  • Last visited

Posts posted by Sage

  1. Just got the camera, and found there is a little wrinkle in the workflow. The MXFs are being marked with a .9375 pixel aspect ratio in the re-wrapping of C4K files (4096x2160); this results in a slightly squeezed frame, into a 16:9 ratio. It should be a 1.896 ratio (1.0 pixel aspect ratio), and at the moment I am correcting it with 'interpret footage' in Premiere at the outset.

  2. 1 hour ago, Stab said:

    Sometimes I need to make a 'same-day-edit' on a wedding shoot. This would be made from about 400 GB of all seperate GH5 clips with maybe a 2-4 hour time in duration.

    Do you maybe have an indication for me about how long the transcoding would take? 

    That is a tricky situation. It should be faster than realtime, but not less than half. Approximately 1.3-3 hours. Assuming no PC bottlenecks. Write to SSD (a different drive than the read), try overclocking the 3770 if its a K - they are very generous with the extra clock cycles, I run at 4.5 with a cheap 212 Evo cooler

    You'll will want to edit proxies from an SSD, they are small enough to fit and will have instantaneous performance

  3. Proxies! I know you don't want to transcode, but there is nothing like it

    You edit better. Simple as that. JKL ftw

    With your specs, transcode time won't be significant

    Recommend: H.264, Exactly quarter resolution for C4K, or full resolution for FHD, 22mbps for quarter C4K/20mbps for FHD, 6 gop, (max render quality off) all stored on an SSD

  4. 9 hours ago, Orangenz said:

    Log is set to full range Lum values in 8 or 10bit modes, not reduced. Considering the time they had the codecs from panasonic, I also think they should have been able to do a bit better.

    That makes the most sense as to why its not working; that would mean that Panasonic has coded the GH5 file header to specify the wrong IRE placement, according to their own V-Log specs (or it is misread by Premiere, due to differing header format from Varicam). And it is a matter of file header ID, as the wrapping method's success reveals (explains the inconsistent handling of levels across NLEs)

  5. 1 hour ago, Orangenz said:

    As Luke said elsewhere, Adobe was given the files a long time before release. In addition, the luminance setting of vlog files is set by the camera and the compressed luminance recording is on top of the full range for consistent scale. For non-log files making this change does allow import into Premiere but I don't find this particularly useful as the rewrapped files edit considerably easier and have the corrected length. 

    Yes, the rewrap approach is probably the best way to go (I don't have the camera yet)

    The information above, and the little discovery by Justin is of particular interest to me as I am working on a little project involving V-log mapping at the moment

    That compressed luminance recording of v-log and v-log L is even beyond the 64-940 (0-100%) IRE envelope. I.E. exposure bottom* is intended to map at 128. And that is with the 64-940 envelope

  6. On 4/21/2017 at 1:29 AM, JustinJohnson said:

    Hey Orange, I posted a response on the Adobe boards but hopefully you see this here. Check your Luminance Level in the GH5. If it's set to 64-940 or 64-1023 10 bit files work just fine. It's only when it's set to 0-1023 that I get the audio import only.

    I have recorded a bunch of clips with my level set to 64-940 now and now import errors. This should be the proper setting for Premiere as I know it, it defaults to 0-1023 I believe.

    I am running some more test to see if this is it.

    Thanks for sharing this Justin. To further this, it looks like the 64-940 (0-100%) IRE placement matches the official Varicam specification for V-log, as shown in the graphs on this page:

    http://www.slashcam.de/artikel/News/Naeheres-zum-Panasonic-GH4-V-Log-Update.html

    It would make sense that it is the data arrangement that Premiere is expecting and was coded to handle previously (standard Varicam levels)

  7. The GH5 internal codec is most definitely limited. In that 10 bit footage, I see distinct color patches in skin tone when very zoomed in. In motion, full-scale, it is not too big of a deal to me. Its 'good enough' for an internal codec. What is more concerning is distinct banding in the sky at the beginning of the footage. I have watched a lot of GH5 footage, including more 10 bit v-log footage from Pampuri where the sky *wasn't banding, so I have a theory.. Perhaps more later. I will likely purchase the camera after NAB

×
×
  • Create New...