Activity › Forums › Apple Final Cut Pro › X to 7 and premiere weirdness/warning
-
X to 7 and premiere weirdness/warning
Jeremy Garchow replied 13 years, 5 months ago 4 Members · 25 Replies
-
Charlie Austin
April 2, 2013 at 4:11 am[Jeremy Garchow] “Date should have nothing to do with it. Fcpx is picky about length, audio channel configuration, and type.
What type of media is this?”
Agreed, which is why this is so weird. As far as I can tell, and I looked pretty hard, the only discernable difference between the online and offline files, is the creation date. Invisible is whatever the XMP data was. This has happened to me twice. Once with a DV source clip, once with a Prores file. Both about 2 hours in length. In the first case, I had another copy of the original on my local drive. When I replaced the “modified” version with that one on the server, it relinked just fine. This recent time, I unfortunately had tossed the copy of the original that I had. Very odd. I’ve pinged Apple about it…
————————————————————-
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~ -
Bret Williams
April 2, 2013 at 4:13 amI just posted that rebellion fixed it. It was mainly DSLR footage from a 5D mk II. BUT, some was AE pro res renders, and some was stock footage that had been transcoded to ProRes.
So yeah, modification date didn’t matter (although I guess it does for the render files in 7?). Removing the XMP data was instant fix.
Thanks again!
-
Charlie Austin
April 2, 2013 at 4:14 am[Bret Williams] “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!”
Nice!… sadly didn’t work for me… maybe another issue but I’ve got no clue what it could be. I know it was opened in AE with the Write XMP function turned on, so I really don’t have a clue. I’ll try the QT Edit again tomorrow. Anyway, glad you’re back up!
————————————————————-
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~ -
Jeremy Garchow
April 2, 2013 at 4:56 am[Bret Williams] ”
Thanks again!”I’m not only the forums squeakiest wheel, but I’m also a client.
Reply to this Discussion! Login or Sign Up