Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Forums Apple Final Cut Pro X FCPX 10.4 – levels shift in DNxHD footage, doesn’t recognize DNxHR

  • FCPX 10.4 – levels shift in DNxHD footage, doesn’t recognize DNxHR

     Jeremy Garchow updated 4 years ago 3 Members · 17 Posts
  • Michael Hancock

    January 2, 2018 at 8:49 pm

    I’m running a fresh install of High Sierra and FCPX 10.4 . Our graphic renders come to us as DNxHD (they’re on PCs). Footage is rendered out of After Effects CC2018, as DNxHD_HQ_8bit or DNxHD_HQX_10bit.

    In FCPX 10.4, there is a levels shift in every DNxHD render except DNxHD_444_RGB. All the rest of the renders have lifted blacks and lowered whites.

    Below is a comparison between a ProRes render and a DNxHD HQX 10-bit render from After Effects, or a ramp going from pure black (0,0,0) to pure white (255,255,255). The only difference between the files is the codec, but the DNxHD is being interpreted wrong, and I can’t figure out how to reinterpret it in FCPX so it’s read correctly.

    In addition, DNxHR Quicktime files don’t work at all in FCPX. They just show up solid green, like the codec is missing.

    Anyone else seeing this, or can anyone else replicate it?

    —————-
    Michael Hancock
    Editor

  • Steve Connor

    January 2, 2018 at 9:25 pm

    Have you done the Pro Video Formats update?

    \”Traditional NLEs have timelines. FCPX has storylines\” W.Soyka

  • Michael Hancock

    January 2, 2018 at 9:26 pm

    Yep. I just checked the App Store again and there’s nothing to update. The ProApps update was installed Dec 19, 2017.

    —————-
    Michael Hancock
    Editor

  • Michael Hancock

    January 2, 2018 at 9:30 pm

    Update as I continue to test this:

    The levels are read correctly in Premiere Pro and Resolve. FCPX is the only program reading them wrong.

    As another test I dropped the DNxHD files into Media Encoder 2018 and recompressed them as ProRes files (matching the source files on all other parameters). They now import into FCPX with the right levels!

    It looks like there is something in the DNxHD metadata that FCPX is reading and interpreting wrong? Anyone know how to change the levels flags in a Quicktime file without having to recompress it?

    —————-
    Michael Hancock
    Editor

  • Jeremy Garchow

    January 3, 2018 at 5:48 pm

    Avid has some very weird left over legacies.

    What you are seeing is the difference between 0-255 full RGB and 16-235 “limited” RGB. Obviously, FCPX isn’t remapping the files correctly. As fas as I know, all Avid material encodes 16-235 internally to Avid, but you can override the settings on import.

    Quicktime probably doesn’t work because QT is nearly dead in High Sierra, but MXF should work.

    I did some test encodings of DNx media out of Ae CC2018 to the codecs you mention and an MXF wrapper.

    FCPX interprets these values correctly. I am not on High Sierra, though. Can you send over that test ramp with the Avid render?

    Here’s what I am seeing:


    And here’s the test renders:

    12041_dnxtest.zip

  • Michael Hancock

    January 3, 2018 at 6:29 pm

    Thanks Jeremy for testing this and for uploading your files.

    I downloaded your files and am still seeing the shift on my MacPro (High Sierra and FCPX 10.4). I also tested them on an iMac running Sierra and FCPX 10.4 and I still see the shift, which is really strange, since you’re on Sierra and aren’t seeing it.

    Here are the files I made in AE2018 for testing. I have both Quicktime files and MXF.

    12042_dnxhdramptestfiles.zip

    The RGB Ramp should be 0-255, and Legal should be 16-235. On my system, the RGB looks like it gets changed to 16-235, and the Legal gets the same shift, making it really washed out. Do you see the same on your system?

    —————-
    Michael Hancock
    Editor

  • Jeremy Garchow

    January 3, 2018 at 7:21 pm

    [Michael Hancock] “The RGB Ramp should be 0-255, and Legal should be 16-235. On my system, the RGB looks like it gets changed to 16-235, and the Legal gets the same shift, making it really washed out. Do you see the same on your system?

    No, both full and legal are what is expected, 0-255 and 16-235 respectively.

    What is different is that both the legal files appear to decode 8 bit, while the RGB files have an obvious difference in 8 vs 10.

    Do you have any other codecs installed and have you tried deleting any old codecs are reinstalling?




  • Michael Hancock

    January 3, 2018 at 7:50 pm

    Thanks for testing all this. Very frustrating that I’m not getting the same results as you!

    As far as I know I don’t have any other codecs installed (I did a clean install to High Sierra just prior to Christmas). The Avid codecs were installed when I installed Media Composer First, which I installed to make sure I got the latest codec pack (and to test it to see just how crippled their free software is).

    Is there a specific place codecs are installed to? I’ll look in my Application folder for an uninstaller too.

    —————-
    Michael Hancock
    Editor

  • Jeremy Garchow

    January 3, 2018 at 7:55 pm

    Hard Drive > Library > Quicktime

    This is the regular Library folder, not the hidden user library folder.

    Jeremy

  • Michael Hancock

    January 3, 2018 at 9:01 pm

    Thanks. I nuked all the Avid codecs, restarted for good measure, rendered a DNxHD .mxf from After Effects (via Media Encoder), and imported it into FCPX. It imports, but the screen is black. Likely because I removed the Avid codecs!

    After Effects and the other Adobe products can read the file just fine since DNxHD is native to them now, and levels on the render match the AE project. I’m going to redownload the Avid codecs and reinstall them, then I’ll reimport.

    Do you know what version of the Avid codecs you have installed on your system?

    —————-
    Michael Hancock
    Editor

Viewing 1 - 10 of 17 posts

Log in to reply.

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy