-
xml import from FCP 7 general error or crash
Newbie on Premiere. Been test driving. I’m wrapping up a project in FCP 7 and thought I’d take it over to Premiere via XML. I’ve done this before on just a couple cuts and dissolves kinda thing for fun, but this time I have Pro Res 444 footage, color correction, boris titles, some filters, etc. Just thought I’d see what comes across and how.
Lots of weird stuff going on. I’m having trouble getting the xml to always import, and if I DO, it unrenders portions of the FCP sequence, and that’s just not good. The only way that could happen is if Premiere moved files it’s referencing or changed a modification date somehow, which is possible. This only occurs once the XML is successfully imported to premiere. If it doesn’t import, nothing gets unrendered in FCP.
I have a couple sequences in the FCP project but for some reason, when I try to import some of the XML sequences I just get…
“File Import Failure – Error Message – The importer reported a generic error.”Now, when it does decide that an xml sequence will import, it doesn’t appear until I close the project and reopen. Then the bin and sequence are there. Then, upon trying to open the sequence, I get a hard crash.
So, either an xml won’t import, or it does import, unrenders stuff IN FCP, and then crashes Premiere when I try to open. Any ideas?
I’m running PPro 5.0.4, OSX 10.6.8, FCP 7.0.3 on a Mac Pro 1,1 dual dual 2ghz
-
7 Replies
-
Try using the trial version of Premiere Pro CS5.5.
There have been a lot of fixes and improvements in FCP XML interchange between CS5 and CS5.5.
———————————————————————————————————
Todd Kopriva, Adobe Systems Incorporated
Technical Support for professional video software
After Effects Help & Support
Premiere Pro Help & Support
——————————————————————————————————— -
I can try that. Won’t interfere with my Master Collection bundle? Really wish you guys would offer the 1/2 off deal for us FCP’ers to upgrade our Premiere CS5 MC to CS 5.5. I guess I could just add a copy of premiere but that would be kinda silly.
-
I’ve been stripping things out of the timeline to see why one of the seqeunces won’t come across at all. I’ve deleted filters, freeze frames, and I think it may have been the caf audio files. But not sure. Those are in other sequences that came across (and then crashed.)
In any case, I got a problem project across, but then of course, crashola.
-
My guess is that the render files get knocked loose in FCP due to PPro adding XMP metadata to the files, which is what changes them ever so slightly.
I had the same problem using autoduck to send FCP timeline to AE. In AE, you can turn off the XMP which solved the problem back in FCP, not sure if you can do the same in PPro.
-
A little late to this thread, but I just had the same problem of PPro crashing on XML import for no apparent reason.
Thanks to the previous poster (Jeremey) I tried imported without writing the XMP data and it worked. To do that in PPro, it’s under Preferences>Media and you need to deselect the “Write XMP ID to Files on Import”
-
Make sure that you have installed the most recent updates. We fixed a cause of a crash when importing FCP XML in a recent update.
———————————————————————————————————
Todd Kopriva, Adobe Systems Incorporated
Technical Support for professional video software
After Effects Help & Support
Premiere Pro Help & Support
——————————————————————————————————— -
Hey Todd,
I’m up to date with 5.5.2
I’ve been importing numerous FCP projects over the past 6 months and today was the first time I’ve run into the crashing, so it’s really never been an issue.
I thought it may be a corrupt clip, something media related causing the issue, but after eliminating everything I could think of I tried the XMP thing and that did the trick.
_______________
A.J. Leitch
http://www.modrew.com
Reply to this Discussion! Login or Sign Up