Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro X to 7 and premiere weirdness/warning

  • X to 7 and premiere weirdness/warning

    Posted by Bret Williams on April 1, 2013 at 4:46 pm

    Here’s an interesting one. I got Xto7 and am very impressed. What I’m not impressed about is how Premiere screws up my FCP X project afterwards.

    I’m using xto7 to transfer a FCPX sequence to premiere. Works. But after Premiere has touched the project files, they are now marked as “modified file” in FCP X. It’s only the h264s FWIW. ProRes animation and stock footage and wavs are fine. WTF has Premiere done to the source media?

    Jeremy Garchow replied 13 years, 5 months ago 4 Members · 25 Replies
  • 25 Replies
  • Oliver Peters

    April 1, 2013 at 5:00 pm

    Turn off the XMP metadata settings in the import preferences for PPro.

    – Oliver

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

  • Bret Williams

    April 1, 2013 at 5:35 pm

    Thanks! Too late now though…

    Thankfully I was just playing with a completed consolidated project. So one more vote for “we need to fix this relinking crap and allow to force a relink!”

  • Bret Williams

    April 1, 2013 at 5:39 pm

    I’ve got 2 –

    Write XMP ID to Files on import (definitely turning that crap off)

    But how about
    Enable clip and XMP Metadata linking

    What else can I turn off that is gonna screw up my system?

  • Oliver Peters

    April 1, 2013 at 5:40 pm

    I think it’s just the “write XMP ID”, since that is modifying the source files.

    – Oliver

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

  • Jeremy Garchow

    April 1, 2013 at 6:01 pm

    QTEdit can strip XMP metadata out of Qt files.

    Jeremy

  • Bret Williams

    April 1, 2013 at 9:23 pm

    Can’t figure out what app that is. Get lots of ProTools links. Who makes it? Free?

  • Charlie Austin

    April 1, 2013 at 9:39 pm

    [Jeremy Garchow] “QTEdit can strip XMP metadata out of Qt files.

    Just tried it on a file… didn’t seem to work. Fortunately it’s from a project that’s done, but if this had happened in mid job, I would be completely f*cked. Hope everyones sending feedback to apple about this, I have… Oh, and Bret, it’s part of Digital Rebellions’ pro media tools. a free trail is downloadable…

    ————————————————————-

    ~”It is a poor craftsman who blames his tools.”~
    ~”The function you just attempted is not yet implemented”~

  • Bret Williams

    April 1, 2013 at 10:55 pm

    Yeah, this was a finished, consolidated project stil on the raid. I have the original camera files elsewhere, but it screwed up other stuff too, like AE renders and converted stock media. Going to be a pain in the a to repair it all. Probably 40 or 50 shots. One by one if the QTedit doesn’t work.

  • Charlie Austin

    April 1, 2013 at 11:15 pm

    [Bret Williams] “Yeah, this was a finished, consolidated project stil on the raid. I have the original camera files elsewhere, but it screwed up other stuff too, like AE renders and converted stock media. Going to be a pain in the a to repair it all. Probably 40 or 50 shots. One by one if the QTedit doesn’t work.”

    Bummer. i’m of 2 minds about this… One mind says that FCPX is being ridiculously anal about relinking. Which is probably true. If I cut from offline pix with window burns etc, and then want to relink a cut to final picture, with exactly the same TC and duration but in a different format etc, is that even possible? it should be. The old “This may blow up in your face. Do it anyway?” dialog. ;-}

    The other mind says… what kind of idiotic app writes data to a master file without at least warning you it’s doing so? At least FCP 7 would say “you’re about to modify a source file. are you sure you want to?”

    Oh well… more things to complain to Apple about. 🙂

    ————————————————————-

    ~”It is a poor craftsman who blames his tools.”~
    ~”The function you just attempted is not yet implemented”~

  • Jeremy Garchow

    April 1, 2013 at 11:57 pm

    [Charlie Austin] “Just tried it on a file… didn’t seem to work. Fortunately it’s from a project that’s done, but if this had happened in mid job, I would be completely f*cked.”

    XMP file modification has been part of Adobe’s workflow for a long time so I usually shut off the XMP options (this has to be done in Ae as well).

    In FCP7, XMP injection simply knocks render files loose, which can be a pain, but not devastating.

    Reconnection in FCPX needs some retooling, absolutely.

    FWIW, I have mistakenly left the option on, and the files flash that they are disconnected in FCPX, but then they relink. I don’t seem to have an issue of XMP knocking the files completely offline.

    Stripping the XMP metadata works for me in Qt Edit.

    Jeremy

Page 1 of 3

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