Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Word of caution – Premiere and FCPX sharing files

  • Word of caution – Premiere and FCPX sharing files

    Posted by Michael Garber on June 2, 2012 at 9:05 pm

    Just wanted to give a quick word of caution if you are going to try to share media between FCPX and Premiere. Luckily, I was just doing some tests, so no major damage was done.

    I was using Xto7 to do some render time tests. It didn’t do a great job of translating my sequence. But that’s neither here nor there.

    Then, I brought the same XML into Premiere. Premiere couldn’t open it. Note, I didn’t try sending and xml out of FCP7. I was using the one straight from Xto7, just to see how it might work.

    Later, I opened FCPX and found that a bunch of the files had changed and X couldn’t re-link them. Tried manual relink, but it said that the file was changed.

    I’ve seen this before with Premiere and FCP7. If you send an XML to Premiere from 7, then it will mess up all your render files in FCP7. So my guess is Premiere is messing with the metadata and FCPX doesn’t like it.

    Anyway, just a word to the wise, if you choose to share FCPX files with Premiere, I would recommend copying them to another folder first.

    Michael Garber
    5th Wall – a post production company

    Kevin Johnson replied 14 years, 3 months ago 4 Members · 6 Replies
  • 6 Replies
  • Oliver Peters

    June 2, 2012 at 9:46 pm

    [Michael Garber] “Later, I opened FCPX and found that a bunch of the files had changed and X couldn’t re-link them. Tried manual relink, but it said that the file was changed….
    …..I’ve seen this before with Premiere and FCP7. If you send an XML to Premiere from 7, then it will mess up all your render files in FCP7. So my guess is Premiere is messing with the metadata and FCPX doesn’t like it.”

    Actually this happens with FCP X only if you have the XMP preferences enabled in the Adobe apps. If you intend to go back and forth, TURN OFF all Adobe app prefs that enable writing XMP metadata into the media files upon import. At the very least, this alters the modification date of the file. As a result, X now thinks it’s a completely different media file, because the parameters of the file no longer match the X database. Thus, it’s offline when you return to X.

    – Oliver

    Oliver Peters Post Production Services, LLC
    Orlando, FL
    http://www.oliverpeters.com

  • Michael Garber

    June 2, 2012 at 10:12 pm

    Thanks, Oliver! Here I was thinking there was no way around it.

    Does having XMP turned off mess you up in any way when using Premiere?

    Michael Garber
    5th Wall – a post production company

  • Oliver Peters

    June 2, 2012 at 11:53 pm

    [Michael Garber] “Does having XMP turned off mess you up in any way when using Premiere?”

    I never use their metadata XMP stuff. So for me, no.

    – Oliver

    Oliver Peters Post Production Services, LLC
    Orlando, FL
    http://www.oliverpeters.com

  • Jeremy Garchow

    June 3, 2012 at 5:17 pm

    This same process should be used for Ae as well.

    Jeremy

  • Michael Garber

    June 3, 2012 at 5:53 pm

    Thanks again, Oliver and Jeremy. Much appreciated!

    Michael Garber
    5th Wall – a post production company

  • Kevin Johnson

    June 6, 2012 at 6:30 pm

    This burned me on a FCP project before…sent files to AE and then came back to FCP, and hours of renders were lost as FCP refreshed the files, so annoying!

    Kevin Johnson

    Autodesk Smoke Artist
    FCP Editor
    Washington, DC

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