Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro FCPX XML file broken?

  • FCPX XML file broken?

    Posted by Kristian Whitlock on March 18, 2013 at 6:13 am

    Hi All,

    Trying to conform a 90sec piece in Smoke 2013, which I cut in FCPX. No joy.

    I began the project on another iMac while I waited for my Mac to be delivered. Brought the hard disk home and relinked all the events to populate the timeline on my new machine.

    I wonder if the XML is pointing to the original machine’s media location. Below is a sample of the file path when XML is opened in text editor.

    file://localhost/Volumes/Krissy_Reel/kristian_capture/

    Are there any obvious steps I should beware of when exporting the XML in FCPX? Do i need to something as silly as mark and In and Out for the whole sequence?

    Any help much appreciated.

    Thanks, Kristian

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

    Kristian Whitlock replied 13 years, 5 months ago 5 Members · 6 Replies
  • 6 Replies
  • Andreas Kiel

    March 18, 2013 at 10:39 am

    I’m not sure whether Smoke accepts FCPX XML at all – it will work with FCP 7 XMLs.

    Andreas

    Spherico
    https://www.spherico.com/filmtools

    “He who fights with monsters should be careful lest he thereby
    become a monster. And if thou gaze long into an abyss, the abyss will
    also gaze into thee.” – Friedrich Nietzsche, Beyond Good and Evil

  • Oliver Peters

    March 18, 2013 at 11:51 am

    It is supposed to work with FCPXML just fine. I’ve done testing and it linked correctly, but that was with everything on the same drives and no movement of the media. Make sure your XML is located at a level above the folder containing all the media. Sometimes that helps with Smoke.

    Oliver

    Oliver Peters Post Production Services, LLC
    Orlando, FL
    http://www.oliverpeters.com

  • Jeff Kirkland

    March 18, 2013 at 8:43 pm

    FCPX XML generates absolute rather than relative links to the media in use at the time. If the media is in a different location when you reload the XML then you need to either use the target app’s relinking facility or do a search and replace in the XML file with a text editor to change the location references.

    Jeff Kirkland | Video Producer | Southern Creative Media | Melbourne Australia
    http://www.southerncreative.com.au | G+: https://gplus.to/jeffkirkland | Twitter: @jeffkirkland

  • David Battistella

    March 19, 2013 at 2:27 pm

    Try Exporting a V1.1 instead of V1,2 FCPX XML

    David

    ______________________________
    The shortest answer is doing.
    Lord Herbert
    https://www.davidbattistella.com

  • Kristian Whitlock

    March 20, 2013 at 2:05 am

    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

  • Kristian Whitlock

    March 20, 2013 at 4:47 am

    Hi All,

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

    Thanks, Kristian

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