[Kristian Whitlock]

Hi All,

Apologies, the ‘bad’ XML project info is so broken it won’t even show up in the post. 🙁

Thanks, Kristian

[Kristian Whitlock]

Hi All,

Thanks for your responses!

Luckily my conform was only intended as an R&D exercise but should have found my way to Oliver’s article about FCPX/7 XMLs before now.

https://www.creativeplanetnetwork.com/dv/news/round-trip-workflows-post-workflows-and-final-cut-pro-x/18114

* Jeff:
I tried various find and replace formats for the source file path but to no avail.
However, I also created a simple edit in FCPX, having imported the media afresh, rather than the relinking I did with the ‘bad’ project. The exported XML conformed successfully in Smoke.

Interestingly there’s no difference between the XML path metadata of both projects (see below).

BAD

GOOD
project name=”New Project” uid=”126D2F7B-C5D8-43F3-BC95-CAA7E21F714D” eventID=”C042BA3B-BDD8-4EA6-A1D7-B6953D63DBCD” location=”file://localhost/Volumes/Krissy_Reel/Final%20Cut%20Projects/New%20Project/”>

* David:
These XMLs are v1.2 but couldn’t see an option to revert to v1.1

Thanks, Kristian

Kristian Whitlock
Online Editor – Smoke 2013 | Avid DS | FCP-X