Forum Replies Created

  • First note that After Effects(CS5.5) and Final Cut Pro do not recognize the metadata for field dominance the same way when creating their respective renders. More importantly, many factors will determine how field order data is written to the file in AE. I’ve discovered that Frame rate(comp settings) and Gamma Correction(codec settings in render output module) will affect this data the most.

    To simplify this explanation for fixing the issue I am only referring to AE comps formatted for 1920×1080 square 29.97fps or 30fps only. (Comps set to 24fps or 60fps do not experiences this problem–perhaps someone who knows more about pulldown, drop frame etc can explain why)

    NOTE!!! THIS PROBLEM DOES NOT OCCUR BETWEEN AE AND ADOBE PREMIER!!

    THE FIX! – to ensure all AE renders retain the progressive field order(NONE) when imported to FC:

    1. Add to Render Queue. Select Output Module preset(highlighted in orange).
    2. In Video Output settings click on ‘Format Options’ and change Video Codec to any one of the Apple ProRes codecs…you will notice that ‘Codec Settings’ will now go from being grayed out to white text.
    3. Click ‘Codec Settings’ and change GAMMA CORRECTION to NONE

    Voila!! Now your rendered file will import to Final Cut with a progressive field dominance(NONE) as it should.

    Again, this FIX only pertains to AE comps set up with 1920×1080 square 29.97fps or 30fps settings (HDTV 1080 29.97 preset)
    If your workflow is either set up for 24fps, 60fps you will not have to use this fix and can use any Video Codec without Final Cut misinterpreting fields upon import.

    Alternatively you can always check the FIELD DOMINANCE for each footage clip upon import to FINAL CUT – which should be part of every editor/compositor workflow when using multiple platforms. AGAIN THIS PROBLEM DOESNT EXISTS WHEN USING AE WITH PREMIERE!

    Good Luck!

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