Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Blackmagic Design Rendering to 10bit in AE yields bad files

  • Rendering to 10bit in AE yields bad files

    Posted by Aaron Neitz on June 27, 2006 at 6:30 pm

    yesterday I did some renders to 10bit UC @ 23.98 in After Effects (and also in Shake). QT player plays them back fine… but Deck Control and FCP play back with strobing, jumpy frames, and lots of black flash frames. FCP comes up red in a timeline… but I can’t see anything about these files that’s incorrect.

    BUT rendering to 8 bit UC @ 23.98 is OK.

    In AE I only see “Blackmagic 10 bit” as my codec choice. In Shake I see “10 bit uncompressed 4:2:2:”. Am I seeing some leftover codec that’s causing these problems?

    os 10.4.6
    BMD 4.6 (4.5 yesterday, upgraded today to see if it helped)
    Decklink HD Plus
    Dual G5 2.3/4Gig RAM
    FCP 5.1.1
    AE 6.5
    Shake 4

    Matt Silverman replied 20 years, 2 months ago 2 Members · 3 Replies
  • 3 Replies
  • Matt Silverman

    June 27, 2006 at 9:38 pm

    We do this all the time without any issues. You should render to the BM10bit codec in AE, then open in FCP using 10bit Uncompressed sequences. Make sure your AE prefs are set to enable 64bit QT for v210. You can then select “Trillions of Colors” in the output module. If you tried using the Apple 10bit codec in AE with Trillions, you will get corrupted frames. This has apparently been fixed with the new ProApps updater, but I haven’t taken the plunge yet (doing this later today). This also fixes the gamma embedding in the Apple codecs, which should allow you to then render directly to the Apple codec in AE.

    To clarify, BlackMagic created the first codec for the Kona cards, which used the v210 file format. Apple then created their own codec and also used the v210 file format. These two codecs are interchangeable, though they get confused sometimes. Overall, the BM codec had better color filtering and was “higher quality”, but they eventually killed it in FCP to prevent headaches with the apple codec. Also, by using the Apple codec they could rely on Apple’s RT effects instead of having to write their own support. Hopefully one day it will rise from the dead with a new file format (I don’t need much RT).

    -Matt

  • Aaron Neitz

    June 27, 2006 at 9:47 pm

    Thanks Matt. Are you talking about the ProApps 2006-01?

  • Matt Silverman

    July 1, 2006 at 4:40 am

    Yes. I installed it but did not have time to test the codec. Editing works fine in FCP…

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