-
X to 7 and premiere weirdness/warning
-
[Jeremy Garchow] “[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.
“The problem I run into, in a shared media environment, is that everyone didn’t know the havoc this could cause. They do now… >:-| This has happened a couple of times, both times with projects that were done, but it’s a bit… disconcerting. In both cases the file was exactly the same, save for some sort of metadata being written to it, which was signaled by the files’ modification date changing. Same size, same format, same audio configuration… same file. No problem at all in FCP 7, but X just plain refuses to relink. Also, the error message states that there’s not enough media or something, which is just plain wrong. Again… disconcerting…
————————————————————-
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~ -
[Charlie Austin] “The problem I run into, in a shared media environment, is that everyone didn’t know the havoc this could cause. “
Let’s back up a second.
This is footage on a SAN?
I assume your are using aliased links or is this media in the Event?
XMP does not seem to trip up my files on the SAN here.
Have you tried simply dragging a file back in to see if it reconnects? It should have the little “alias” arrow not a green plus sign.
-
[Jeremy Garchow] “[Charlie Austin] “The problem I run into, in a shared media environment, is that everyone didn’t know the havoc this could cause. ”
Let’s back up a second.
This is footage on a SAN?
I assume your are using aliased links or is this media in the Event?
XMP does not seem to trip up my files on the SAN here.
Have you tried simply dragging a file back in to see if it reconnects? It should have the little “alias” arrow not a green plus sign.”
Not a SAN, on NAS… central RAID served over gigabit ethernet. And yes, linked files, not in the event, which is local. tried dragging it in again, no change, the file I dragged in shows up right next to the offline “file” in the event browser. Nothing relinks…
————————————————————-
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~ -
[Charlie Austin] ” Also, the error message states that there’s not enough media or something, which is just plain wrong.”
Yeah, that is wrong. I wonder what would be different (besides the obvious) from SAN and NAS XMP modified files.
Jeremy
-
[Jeremy Garchow] “[Charlie Austin] ” Also, the error message states that there’s not enough media or something, which is just plain wrong.”
Yeah, that is wrong. I wonder what would be different (besides the obvious) from SAN and NAS XMP modified files.
“No clue. I guess the current “solution” is be certain that nobody opens a master file in any Adobe app with out first turning XMP write off…
————————————————————-
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~ -
I have tried everything too. Reimport puts it right next to the other. My files are all local on the Pegasus. Some originals, some optimized, some AE renders that are linked, etc.
-
[Bret Williams] “I have tried everything too. Reimport puts it right next to the other. My files are all local on the Pegasus. Some originals, some optimized, some AE renders that are linked, etc.
“Even more frustrating is the fact that the symlink/alias/whatever in the Finder, reveals the original just fine, so there really is something odd in the XMP data that X doesn’t like…
————————————————————-
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~ -
I might do some tests after I fix this pile o sheet that Adobe created for me. But I think that it’s just the modification date. AND possibly that I had X open at the time. Perhaps the times Jeremy said his complained, but then relinked, that his FCP X had been off when the modification occurred. Mine was on, and so the files changed right under X’s nose and I guess it got jealous or something.
But the modification date is the reason it kicks off in 7. I’m starting to remember playing with going FCP 7 to XML to Premiere a year or two ago and getting just as ticked that my 3 hour render was kaput. But if a file is modified, then the render is no longer relevant. So that made sense. I should’ve learned my lesson back then, but didn’t seem like such a horrible thing. I rerendered and forgot about it. Til now.
-
[Bret Williams] “Perhaps the times Jeremy said his complained, but then relinked, that his FCP X had been off when the modification occurred. Mine was on, and so the files changed right under X’s nose and I guess it got jealous or something.”
No, I can watch it happen with Pr, FCPX, and QT Edit all open and change any file and everything stays linked everywhere.
This is on local or SAN, modified creation date and all.
Date should have nothing to do with it. Fcpx is picky about length, audio channel configuration, and type.
What type of media is this?
-
And Digital Rebellion did the trick. Batch removed (5 clips at a time with the trial version) the XMP data from the afflicted files. Opened up FCP X and it’s all happy again. Thank you Jeremy and Charlie!
Who says there’s no FCP X suite? It’s FCP X, Motion, Compressor, 7 to X, Event X, 7 to X, and Digital Rebellion
Reply to this Discussion! Login or Sign Up