-
PluralEyes to FCPX DTD validation failed.
Hello filmmaker world!
Help please!! I just bought PluralEyes and am struggling….
I am getting this message when trying to export an XML from PluralEyes to FCPX:The XML document sent from application “PluralEyes 4” could not be imported.
DTD validation failed. (Element asset-clip content does not follow the DTD, expecting (note? , (conform-rate? , timeMap?) , ((adjust-crop? , adjust-corners? , adjust-conform? , adjust-transform? , adjust-blend? , adjust-stabilization? , adjust-rollingShutter?) , adjust-volume? , adjust-panner?) , (audio | video | clip | title | mc-clip | ref-clip | sync-clip | asset-clip | audition | spine)* , (marker | chapter-marker | rating | keyword | analysis-marker)* , audio-channel-source* , (filter-video | filter-video-mask)* ,…)Someone said I should duplicate the XML but I can’t even find it, as it sends it directly to FCPX!
Where does PluralEyes store them so that I can try your trick? Does that mean I have to do this every single time I export from PluralEyes or is there a way to make PluralEyes and FCPX work better together??Any ideas??
Thank you!
Rowena -
1 Reply
-
For me the issue was I applied a “Loudness” on one of the audio files because it was recorded so low. I took that off and now no issues importing the Multicam into X.
_______….
DTD errors are generally encountered in the round trip back to Final Cut Pro from PluralEyes. It is usually a symptom of how the media was imported into FCP initially. You will want to make sure that there was not any audio enhancements made or any other metadata, such as keywords. Additionally, you will not want to include and effects, markers or in/out points. Essentially, any adjustments made by Final Cut Pro will be seen by PluralEyes as an edit and can affect the exported XML.
Can you please try reimporting the media into FCP X, create a new project/library without modifying anything then export to a new FCP XML file and try your sync again?
Alternately, you can start your project in PluralEyes first, syncing and then exporting to Final Cut Pro. This should eliminate any extraneous XML confusion from the round trip process.
If you are still experiencing the issue with a new import/sync, supply a problem report and I can continue to assist from there. To generate this report:
Setup your project as you’ve been doing in PluralEyes
Click Synchronize, then click Export
After that’s done, save the PluralEyes project and click Help > Report a Problem
Save the report, and you’ll have a .zip file on your desktop. Attach that .zip file along with an exported XML of your synced sequence and the FCP XML generated from Final Cut Pro to your response, and we’ll troubleshoot from there.
Reply to this Discussion! Login or Sign Up