Forum Replies Created

  • Jesse Garrison

    January 10, 2020 at 5:34 pm in reply to: PluralEyes to FCPX DTD validation failed.

    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.

  • Jesse Garrison

    March 12, 2015 at 5:06 pm in reply to: Pluraleyes 3 error message

    It’s possible that he had no audio in one of the clips to sync to his audio. Make sure you have a audio in the clip that PE is saying is an error.

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy