Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy import with alpha cause wrong field order

  • Anders Bundgaard

    January 4, 2011 at 8:14 pm

    yes out of after effects and without field…

  • Anders Bundgaard

    January 4, 2011 at 8:16 pm

    sorry the 23.x or 24 was me not remembering what it was. i know that it’s very important to match frame rates, been i too many nightmare situations to forget 😉

  • Jeremy Garchow

    January 4, 2011 at 8:32 pm

    And FCP will usually mark the field order correctly when a movie is 23.976 fps or 24.0.

    Any chance you can render a small one second test, zip it, and upload it here? It could be anything, just black is fine.

    Jeremy

  • Atticus Culver-rease

    January 5, 2011 at 2:10 am

    I was having this same problem recently… rendering either animation or ProRes 4444 out of AE and importing into FCP the field order in FCP would say upper every time, even though I was definitely rendering progressive (30p in my case) out of AE. The fix, as you discovered, was just to manually set the clips to “none” fields in FCP, but yeah, it’s annoying to have to do it every time.

    I don’t recall having this happen until just recently, so my guess its some kind of issue that’s popped up having to do with the latest update of FCP and/or AE CS5.

  • Jeremy Garchow

    January 5, 2011 at 5:15 pm

    [Atticus Culver-Rease] “I was having this same problem recently… rendering either animation or ProRes 4444 out of AE and importing into FCP the field order in FCP would say upper every time, “

    This is because you haven’t set the field order correctly in the QT dialog in AE and then saved it as an output module.

    ProRes has a field order flag that can be set and it will be honored by FCP upon importing. In the QT dialog of the output module, make sure that the “Interlaced” box is not checked.

    At least, that’s how it works here.

    Jeremy

  • Jeremy Garchow

    January 5, 2011 at 5:25 pm

    I should add that this metadata flag is not possible to add in the Animation codec. You have to modify it later, which can be tricky.

    Geez, and one more thing, Dumpster works here on Intel, Snow Leopard.

    Jeremy

  • Anders Bundgaard

    January 5, 2011 at 6:08 pm

    just done a render from another machine.
    cs5 as well. no fields. animation codec. and it imported with a field dominance of ‘none’.

    plot thickens.

  • Anders Bundgaard

    January 5, 2011 at 6:08 pm

    just done a render from another machine.
    cs5 as well. no fields. animation codec. and it imported with a field dominance of ‘none’.

    plot thickens.

  • Atticus Culver-rease

    January 6, 2011 at 2:59 am

    Well actually I do have a custom output module for ProRes 4444, and if I open that up and go to “format options” and then “codec settings” the “interlaced” checkbox is NOT checked. I just re-checked and tested it again to be sure, and FCP still thinks it’s upper field after import. I also made sure that field render in the AE render settings is turned off.

  • Jeremy Garchow

    January 6, 2011 at 4:32 am

    Yeah, not making much sense there. Any chance you can render, zip and upload that one second test?

    Also, what version of FCP?

Page 3 of 4

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