Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy FCP will not export progressive ProResfile, only Interlaced…

  • FCP will not export progressive ProResfile, only Interlaced…

    Posted by Richard Lyons on January 12, 2009 at 1:32 pm

    I have captured a clip from tape using 1920×1080 25i setting on Kona3 card with the ProRes HQ codec. The tape is progressive but there was no option to capture 1080 25psf so I was informed that 1080 25i would be fine.

    FCP states the clip has Upper field dominance so I set it to ‘None’ and dropped it into a 1920×1080 ProRes HQ 25fps sequence.

    The Sequence timeline settings were ‘None’ and the Prores Advanced codec options the Interlaced option was also unchecked. All fine, exported the clip based on Current Settings to render a new (progressive) Quicktime.

    I then reimported the rendered clip it back into FCP and it stated that the rendered clip is still Upper Field dominant. Short of reencoding through Compressor (v slow and creates a second generation encoded file) I cannot seem to get FCP to export this material as progressive.

    Is there a way I can just change the Field Dominance flag/tag of the clip within FCP or another application to “None” withut any rerenders/encodes?

    Any help gladly appreciated as this is becoming a real mystery/headache!

    Michael Magallon replied 17 years ago 6 Members · 18 Replies
  • 18 Replies
  • Jeremy Garchow

    January 12, 2009 at 2:45 pm

    [Richard Lyons] “Is there a way I can just change the Field Dominance flag/tag of the clip within FCP or another application to “None” withut any rerenders/encodes?

    Sure, if you have changed your clip to ‘None’ and your timeline to ‘None’ and you have shot progressively, then for all intents and purposes, its progressive. (PsF or Progressive Segmented Frame is the true technical definition) There’s no reason to export and reimport. If you do need to do that, simply change the field dom of the imported clip to ‘None’ again as the clip is progressive. FCP is just tagging it as Upper because it doesn’t know and assumes a field order of Upper first.

    Make sense?

    The other thing to try (I haven’t tried this yet) is to duplicate the 108025i capture preset and save it out as ’25psf’ then uncheck the interlaced box in the Advanced settings and try to capture again. That might get FCP to tag the file as progressive right off the bat. I find that the little interlaced box is metadata that can sometimes transfer to FCP correctly.

    Jeremy

  • Richard Lyons

    January 12, 2009 at 3:07 pm

    Hi Jeremy,

    Thats very helpful, many thanks.

    If I was using it myself that would not be a problem and I would certainly employ your route, but I am having to supply these to a client who requires the files to be progressive as they are using them in FCP or some other NLE app.

    If the files are not recognised as progressive when they import they may reject them…Compressor produced files that import into FCP as ‘None’ but took a long time to render in comparison to the FCP export and I need to create a fast workflow…

  • Jeremy Garchow

    January 12, 2009 at 3:12 pm

    Okay, as a test try modifying the preset like I mentioned. That way you might be progressive right off the bat. Also, in your sequence, did you turn off the interlaced flag there as well?

    I will try and test this at the office today as well.

  • Richard Lyons

    January 12, 2009 at 3:22 pm

    Hi Jeremy,

    I tried creating the preset (with Interlaced turned off in the Prores Advanced codec options dialog also), dropped in the captured clip, confirmed I did NOT want to match the sequence to the clip (as it sees it as upper field dominant) and exported again. The exported file was still seen by FCP as Upper Field dominant… ;-(

    The other issue is that the material (many hours) has already all been captured in this way so to try and avoid recapturing if at all possible…

  • Rafael Amador

    January 12, 2009 at 3:30 pm

    Hi Richard,
    Don’t break your head. Your clip is progressive, but by default FC will ALWAYS identify a ProRess 25fps HD or PAL as Upper.
    The same that always will identify a DV as Lower. QT have not a field order flag and FC have always to guess those things. Even if you just have exported from FC.
    Just check your clip manually as NONE in the Browser. Then use it in a NONE sequence.
    Cheers,
    Rafael

    http://www.nagavideo.com

  • Jeremy Garchow

    January 12, 2009 at 3:44 pm

    But Rafael, he has to DELIVER progressive files with no end user changes. He’s not using the files himself.

    Richard, let me do some tests.

    Jeremy

  • Jeremy Garchow

    January 12, 2009 at 3:46 pm

    RIchard-

    I doubt that you can do this without recapturing. Let me test though.

    Jeremy

  • Richard Lyons

    January 12, 2009 at 4:13 pm

    Hi Jeremy,

    Have tested the amended capture and sequence settings here and it works! (FCP does see it as progressive and keeps that on export and re-import)… looks like I may have to recapture it all again… 😉 / ;-(

    unless you know of another way…?

  • Jeremy Garchow

    January 12, 2009 at 4:22 pm

    [Richard Lyons] “Have tested the amended capture and sequence settings here and it works! (FCP does see it as progressive and keeps that on export and re-import)… looks like I may have to recapture it all again… ;”

    Cool, I thought it might. Glad you tested it.

    That metadata is flagged in those captures as Upper First. I do not know of a way to change it after capture in the actual QT file itself. I am sure there must be some tool that allows you to dig in to the QT file, but I am unaware of it and you can’t access it from the standard Quicktime interface as far as I know. But that doesn’t mean it’s not possible. If I were you, I’d recapture.

    Jeremy

  • Chris Henderson

    April 1, 2009 at 9:04 pm

    What version of FCP are you using that this works on? I’m on FCP 6.02, QT 7.5.0, and OSX 10.4.11. It still gets flagged as Interlaced even with the checkbox in the QT Settings set to Interlaced Off.

    Thanks in advance,
    Chris.

Page 1 of 2

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