Resolve and fcpxml 1.9 and 1.10

What am I missing here? Latest version of fcp only exports fcpxml versions 1.9 and 1.10 and latest resolve 17.4.2 only imports up to version 1.8.


Sent from my iPhone using Tapatalk

Resolve 17.4.2 outputs FCPXML 1.9 from:
File menu > Export > Timeline > FCPXML 1.9

The Deliver page currently outputs a FCPXML 1.8 file.

What I mean is there is currently no way to export an fcpxml from the latest version of fcp and import it into the latest version of resolve because there is no compatible version of fcpxml shared between them. 1.9 or 1.10 seems to currently be the only options out from fcp unless there is some secret I am not aware of. And 1.8 is the latest version resolve will import.


Sent from my iPhone using Tapatalk

Resolve 17.4.2 imports FCPXML 1.9 Timelines via the File menu > Import > Timeline command or from the Media Pool's Timeline > Import function.

FCPXML 1.9 exports from Final Cut 10.6.1 open in Resolve 17.4.2 without issue.
Only FCPXML 1.10 is not currently supported.

Thanks so much. Your comment to made me persist and I found out that I was sent a 1.10, told it was a 1.9 and the resolve error message you get only lists compatible versions up to 1.8. Mystery solved. So they need to update that error message to include 1.9. So all is good now.


Sent from my iPhone using Tapatalk

Hey,

I finally found this thread today because we have a compatibility issue about a project I was given this XML way by the latest FCPX...
I found this too, on the Apple forum side : https://discussions.apple.com/thread/253349471

Ok, so I'm glad I'll be able to finally work on it tomorrow, when my colleague send me a 1.9 xml instead of the 1.10 he sent me before...

TLDR; ? : Since Resolve can import 1.9 XMLs timelines, please BMD modify this obsolete error message when trying to import a 1.10, because it may prevent from even trying 1.9, which apparently works

error.png (23.57 KiB) Viewed 4658 times

Resolve 18 adds support for importing and exporting Final Cut Pro v1.10 XMLs.

Yes, but 18 is a beta, and I work...
Still, 17 has been importing 1.9 actually for 7 months now : I just wanted to tell those in the same situation that they should try 1.9 (therefore not take this error warning for granted)

The error message is simply wrong.

Yes it is, but did you understand the reason why I insist ?
It is clearly wrong BUT it can also prevent partners from finding the truth, which is "yes, you guys on the last version FCPX* and the last stable version of Resolve** clearly CAN exchange a TL to work on together"

*the last FCPX is only able to export 1.9 & 1.10 XMLs - **Resolve 18 is still a beta and therefore doesn't count here

This afternoon, we almost dropped a collaboration because of that (it's a tiny project anyway), fortunately I wanted to dig deeper and discovered my partner just had to send me an 1.9 XML; who knows how many gave up here just because of a wrong error message ?