Final Cut Pro Version 10.6 Errror - The XML document could not be imported. DTD version is not recognized.

So I found the solution after spending a long time looking for it.

Open your xml on a editor text and change the version of Final Cut to a actually version.

For example:

My xml had the 1.4 version and I edited it to <fcpxml version="1.10">

After change save and it's done!

I did this and it worked:

1) create a folder in applications and name it final cut 10.5.4 there in that folder install the previous version of final cut

2) open final cut (version 10.5.4) import the project from pluraleyes to a new final cut project. It was imported successfully. Close final cut 10.5.4.

3) I opened final cut 10.6.1 and it asked me to update that new project that I had imported from pluraleyes and that's it.

Not sure if this will help this particular problem, but I just received this from the Lumberjack folks:

"Lumberjack System Co-Founders, Philip Hodgetts, and Gregory Clarke became aware of an issue in Final Cut Pro 10.6

where it sometimes shows an error message reading,

"The XML document could not be imported.

DTD validation failed.

(The data couldn't be read because it isn't in the correct format)"

A workaround was immediately developed by the Lumberjack team and we wanted to share it with you as it will undoubtedly help in your workflow as well.

Here's the solution:

Go to System Preferences/Language & Region and temporarily set the Region popup menu to "United States," then import the XML file again.

After import, you can reset the Region back to your preference.

This will affect our customers who use Builder, but not Lumberyard."

As I said earlier in this thread: 10.6 won't read (write) XMLs at all unless you switch language/region to (any)English/AUS, UK, US. "International" 10.6 also stopped support for XML versions < 1.5 additionally any XML with "empty" parameter values will either cause errors (which unfortunately often might be not obvious) or will fail.

DVR might be worth to try as a converter.

If's a meanwhile known bug confirmed by Apple.

Only workaround is to switch system settings to English and region to UK/US.

Older XML versions (< 1.6) might fail as well.

Thanks spherico, switching to English / US solve the problem here !

I mentioned the above solution somewhere above but be careful - if you’re used that FCP will ask at import whether to replace something or not: this is gone and things are silently replaced.

I meanwhile recommend another solution: keep a copy of a previous version, create an intermediate lib which you won’t update, open the XML using this, copy your project etc, close FCP, open the new version and paste your things. This also seem to fix some internal errors.

No restart required to switch language/region.

Quit and launch of FCP will be enough - if you want to be on the safe side you can do an „log out, log in”

Plural Eyes uses an old XML format which at this time isn’t supported anymore - regardless of language/region. You need to use version 10.5.x.

You may try Da Vinci Resolve.

If you have a spare system - do not update to latest version for now. Sync multi files and export to FCPX 10.5.4 as example. Then - just open it on a latest version, update and use. Yes - takes sone extra time - but works.

I could still get the file.

The version of xml that it produces is 1.2, which is very old.

FCP uses version 1.10; the previous version, FCP 10.5.4, had version 1.9 of fcpxml.

I can't import your file into FCP 10.6, nor to 10.5.4.

Is upgrading PluralEyes an option?

fcpxml version 1.2 isn’t supported anymore. Rumors say it must be at least 1.5 - but nobody knows

Anyway - if you need XML you should better downgrade and wait until Apple releases a bugfix.

AMYthereandhere wrote:

Thank you Luis! It works just find with regular FCPXML file yet, despite old or new version of file, whenever there is 'caption' added in the project, I get "The XML document could not be imported." message. Do you have any clue with this issue?

I did only make a few very short tests, but they did include a caption.

Would it be possible for you to show us a small example of xml file that fails to import?

Since posting links is frowned upon here, and they will likely be deleted, you could perhaps open the xml file in, say, TextEdit, select all, copy, then in a reply here click the "additional text" button:

and paste the whole xml content into the text box.

I would like to try on my mac (no need for any media), to see it if would import or not, and whether some error message may help figuring out what may be wrong.

Would it be possible to post a complete xml file that fails to import?

Use the "additional text" button and paste the contents of the file there.

Also, if you don't mind my curiosity: why use PluralEyes at all? What does it do that the current version of FCP?

Just enquiring with an open mind.

Your problem seems to be the same as the OP: PluralEyes generates an old version of fcpxml (1.2).

The current version is 1.10, and FCP 10.6 apparently fails to read such an old xml.

I gather that there is no update available for pluraleyes at this time.

Even in 10.5.4, the XML file produces several errors.

I was able to import after doing a find and replace throughout the file, but I have no idea if what came through is correct.

Hi duquemiguelpt, as terryb posted, it is in System Preferences->Language & Region "Idioma e Região" for me.

You can add English / US as main language (the first in the list) and restart your mac.

After importing you can switch back to Portuguese. Just drag Portuguese to the top of the list and restart again.