Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

XML Translation was aborted due to a critical error

Hi all, I exported XML from FC, imported to Color, graded, rendered, saved, exported XML from Color, and when trying to import back to FC i get " XML Translation was aborted due to a critical error" message.
I didn't have any problems with FC-Color roundtrip, I always do the same. My footage is XDCamEx 1080i, no speed changes, filters etc. (only basic transitions), I do have Motion animation on the beginning (I tried to delete the animation from Color and reexport, didn't help). I use Color 1.02 (because of the incompactibility of 1.03 with XDCamEx footage).
Any ideas what to do with this?

MacPro, Mac OS X (10.5.4)

Posted on Jan 20, 2009 2:29 AM

Reply
Question marked as Best reply

Posted on Jan 20, 2009 8:11 AM

You may be having a problem with the Motion clip if you deleted it from the COLOR timeline -- the XML re-edit is probably corrupt as a result. At this point, if nothing else works, you may need to create a new project without the Animation clip, insert a placeholder clip in its stead, and somehow fake the export back to FCP. Whether you have to re-render everything or not depends on whether you can re-link the new project back to the original renders or not. That will take some cleverfness. Otherwise "Import Color Corrections" may be the route with a full re-render and supposedly back to normal after that.

The underlying issue is that COLOR does not create a new XML -- it always uses the exported file created in FCP as the root. Change that and all bets are OFF. Apple makes a point of underlining the need to avoid changing anything on the timeline. It is locked for a reason.

You may want to upgrade to COLOR 1.0.4 which apparently fixed the XDCam issues, but I rarely work with that format.

jPo

Message was edited by: JP Owens
4 replies
Question marked as Best reply

Jan 20, 2009 8:11 AM in response to PetrKotora

You may be having a problem with the Motion clip if you deleted it from the COLOR timeline -- the XML re-edit is probably corrupt as a result. At this point, if nothing else works, you may need to create a new project without the Animation clip, insert a placeholder clip in its stead, and somehow fake the export back to FCP. Whether you have to re-render everything or not depends on whether you can re-link the new project back to the original renders or not. That will take some cleverfness. Otherwise "Import Color Corrections" may be the route with a full re-render and supposedly back to normal after that.

The underlying issue is that COLOR does not create a new XML -- it always uses the exported file created in FCP as the root. Change that and all bets are OFF. Apple makes a point of underlining the need to avoid changing anything on the timeline. It is locked for a reason.

You may want to upgrade to COLOR 1.0.4 which apparently fixed the XDCam issues, but I rarely work with that format.

jPo

Message was edited by: JP Owens

Jan 21, 2009 10:22 AM in response to PetrKotora

I'm chiming in with my support for the "Import Color Corrections" route that JP mentioned.

Essentially, you'll re-export out of FCP and a create a new Color project WITH A DIFFERENT NAME (you must not delete your original Color project).

Before you re-export out of FCP, replace all Motion clips with a dummy clip. It's important that you have the exact same number of clips as you had before - and on the exact same tracks. Don't change anything else.

Then, in your new Color project select "Import Color Corrections". Navigate to your original project and all your corrections will be applied to this new project. Note: This Import is completely unsophisticated. It'll apply the correction on the first clip from your original project to the first clip on your new project - all the way down the line; starting with V1 and then moving up the layers. It does NOT do any fancy name matching or clip matching. Which is why you can't just delete the Motion clip - but it must be replaced with a placeholder.

Then, re-render and Send to FCP and hopefully you'll be good to go.

HTH

- pi

XML Translation was aborted due to a critical error

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.