Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Adobe After Effects 10-bit highlight clipping problem

  • 10-bit highlight clipping problem

    Posted by Scott Mcdonnell on September 14, 2011 at 1:22 pm

    Hi,

    I am working for the first time with 10-bit DNxHD QuickTime footage in AFX CS5 on Windows and have encountered a few issues.

    We wish to import DNxHD, add effects, and export as the same 1080p/25 DNxHD 185 10-bit.

    I thought the workflow with 10-bit is to set the project settings Color Depth to 16 or 32 bpc but both give me a clipping in the whites:

    If I turn to 8bpc the highlights appear normal:

    but does this not render the output as 8-bit?

    I have tried various color management options and all interpret footage options and none fix the issue. Any ideas?

    Here are the rest of the settings:

    Jean Drand replied 6 years, 4 months ago 6 Members · 7 Replies
  • 7 Replies
  • Ben G unguren

    September 14, 2011 at 9:41 pm

    If you hover your mouse over the problematic colors and look at your info window, I bet you’ll see “nan” instead of a number. This is a mathematical issue, where “nan” stands for “Not a Number.” It’s something that pops up every once in a while when you’re working in spaces higher than 8-bit.

    Fortunately Brendan at fnord software has written a plugin that will catch any NaN pixels and convert them into something readable (thank you Brendan!).
    https://fnordware.blogspot.com/2011/04/nanny.html

    good luck!

    Ben Unguren
    Motion Graphics & Editing
    http://www.mostlydocumentary.com

    Some contents or functionalities here are not available due to your cookie preferences!

    This happens because the functionality/content marked as “Vimeo framework” uses cookies that you choosed to keep disabled. In order to view this content or use this functionality, please enable cookies: click here to open your cookie preferences.

  • Scott Mcdonnell

    September 15, 2011 at 2:50 pm

    Hi,
    Thanks for the help and good suggestion.

    Just checking the info and the black pixels show up as a color:

    Here is a black pixel in 32bit mode:

    And this is 16bit:

    Arrgh – it looks fine in QuickTime and Premiere.

  • Jakob Wiessner

    December 21, 2011 at 8:52 pm

    Hi Scott!
    I’m having the same issue here… did you manage to find a solution yet?
    Best, Jakob

  • Arne Münch

    December 31, 2011 at 6:04 pm

    I would also be happy if someone solved the problem and shares his knowledge..
    i don´t like everything related to avid..

  • Scott Mcdonnell

    January 4, 2012 at 9:35 am

    Hi, sorry to not posted earlier but we worked around in the end rather than solved it.

    The problem seemed to be in footage supplied by the post house and not in any we rendered in-house. To work around we dropped the AFX down to 8bpc essentially rendering 8-bit. I would recommend looking at the source and trying different outputs or taking the hit on 8-bit.

  • Alex Johnson

    June 17, 2012 at 10:43 pm

    Unfortunately that’s the exact same thing we’ve had to do as well. I can’t seem to find any answer to this issue on the net. If I figure something out I’ll post the solution here, as I’m sure all of you will.

    Here’s hoping we don’t smash too many monitors before the answer arrives…

  • Jean Drand

    December 12, 2019 at 5:15 pm

    My post is not a precise answer to your question but it can help you to understand why there are clipping issues in After Effects an how to solve the problem. I have just write this post to another user wich has a similar problem. I use 8bit for the explanations but the same is true for the other bit deephts

    Excuse my bad English

    This issue is very common. Due to the color difference encoding math, Y Cb Cr (and all the YUV encoding processes) can encode color levels that are fare above the RGB color space. Almost all the camcorders record Y in the range 16-255. For ex.: If Y=255 and Cb and Cr=128, this is equivalent to RGB 255,255,255 but if Cr and or Cb are not 128, this codes for a color that has the max RGB luminance but is not white and can thus not be converted to RGB because it is a color above 255. Even if you limit Y to 235 when shooting, a big lot of colors can be above 255. The fact that the 16-235 YUV range is further scaled to RGB 0-255 exacerbates the clipping problem.
    For ex.: my Sony has shoot Rec.709 YCbCr=244, 63, 207 (bright red part if a lava flow) = RGB 365.63!!, 219.75, 126.08. I have very often G or B=290. This is a conversion to RGB assuming that my YUV is 16-255 for Y, but if I assume it is 16-235, then the resulting RGB values are scaled a lot higher due to the conversion from 16-235 to RGB 0-255. In Rec.709 YUV, the max. encodable unscaled values are about RGB 400, but only 2 colors can be above 255 at the same time. The max encodable color level for a pixel depends on the levels of the other colors of this pixel.
    If your TV or Pro monitor is XVycc (=x.v.Color) compliant (case by Sony, Panasonic and Philips), those out of RGB space levels are correctly displayed without any clipping when you connect your camcorder HDMI on the monitor. This TV’s and monitors convert internally 8 bit YUV to 9 bit RGB, wich can hold RGB levels from 0 to 512. At the moment, the only solution to see the whole signal on a suitable external YUV monitor when you grade is to use Edius with an Grass Valley output card or with the very good Blackmagis Intensity Pro 4K. Edius import your YUV clip as is, send the datas as is to the external monitor and also to the output YUV codec without clipping!
    The managment of the data levels in the Adobe programs is catastrophic. Never import YUV because it is clipped at 16-235 at import time and this 16-235 range in then scaled to 0-255. In Edius or in Resolve, lower the gain to have all the color peaks under 255 (=1023 in Resolve) and export in 16 bit RGB (for ex. in TIF, Edius can only export 8bit Tif’s ). This creates a darker RGB file but with unclipeed colors. Import this in Adobe and export from Adobe in 16 bit PSD or TIFF (in fact, it’s only 15 bit because the Adobe range is 0-32767 and not 0-65534). Now, you can reimport the clip in Edius or Resovle and gain it back up to his original level. Be aware that by doing so, the black level is not correct in Adobe because it is between 0 an 16 instead of 0, but this has no importance if the purpose is to only apply moving effects. Be also aware that Resolve import YUV as is but, even if properly configured, send only the at 255 clpped levels to the external monitor an to the output codec, wich is not the case with Edius. Be also aware that the conversion between YUV and RGB is highly destructive and introduces color banding. If you must absolutely do this conversion, use always a codec that has an higher bit deepth than your source and use the gain reduction method described above. The whole RGB range falls in the YUV space but not the opposite. In Resolve, you can render in 2 16 bit RGB float math codecs wich can hol the full YUV color range, but the levels are miss interpeded by Adobe. If the purpose is to make full camcorder quality masters, you must chose an NLE that has an internal YUV core and that does no any level conversion of the souce clips. Many many NLE’s don’t satisjy the ITU-BT specs wich says: “The original camcorder data levels that are under 0 or above 1 may never be clipped during production nor in the intermediate files. In a pro editing application, the transmission of all the video information (including ivalid and illegal levels) between equipment is required. Masters must always contain all the original video levels that can be encoded in the chosen Rec.”
    I am waiting for your reaction.

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