DTD validation failed - importing from Pluraleyes

When attempting to import a project from Pluraleyes 4 into FCPX I received the following error:


XML document sent from "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-360-transform? , adjust-reorient? , adjust-orientation?) , 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)...)


This started happening recently, so I made sure Pluraleyes was up to date, then updated FCPX and my OS to Catalina, so everything should be tip top updates.


My system is 2013 Mac Pro.


Google has not been able to find me much to help, it seems like a relatively uncommon issue.


Thank you for your help!

Mac Pro, macOS 10.15

Posted on Nov 25, 2019 2:41 PM

Reply

Similar questions

1 reply

Jan 10, 2020 9:36 AM in response to Zambonisurfer

I had this issue because I applied a "Loudness" to one of my audio tracks before sending the XML to PE. Remove all adjustments before sending to PE. This should fix it. Here is what Red Giant told me.



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.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

DTD validation failed - importing from Pluraleyes

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