Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy XML export -1

  • Posted by Jabran Soubeih on July 9, 2007 at 8:00 pm

    I have a project in FCP 4.5 that was created from 411 still images that were jpg’s. The sequence was created by importing an XML file with each still image having a duration of 3 seconds. Most of the still images were never imported into the bin. I then added effects, graphics and changed the durations. I now want an XML file output from FCP with the clip names and start and end timecodes the clip is on the sequence. When I export the sequence from FCP as an XML I get -1 and -1. I created a sequence and dropped a few of the still images that are in the bin on the sequence and exported that as an XML file and the start and end timecodes in the XML file are fine. I then created a new sequence and copy and pasted all items from my original sequence to the new sequence but still got the -1 for start and end timecodes in the XML file. Any ideas?

    Thanks,
    Jabran

    Andy Mees replied 18 years, 10 months ago 3 Members · 16 Replies
  • 16 Replies
  • Wes Plate

    July 9, 2007 at 10:50 pm

    -1 means either you or FCP must calculate the start or end. Look at the preceding/succeeding clip(s).

    — Wes Plate
    Automatic Duck

  • Jabran Soubeih

    July 9, 2007 at 11:59 pm

    Sorry I wasn’t clearer. Every clip in my XML has start and end of -1. I have 411 clips in the sequence and they all have -1 for start and end.

    Jabran

  • Andy Mees

    July 10, 2007 at 3:27 am

    if these are still images then they wont have a meaningful timecode, no?

  • Jabran Soubeih

    July 10, 2007 at 5:15 am

    These are still still images so I don’t expect a source timecode for and but I do expect a timecode where they are on the sequence which is the and in the XML export file.

  • Wes Plate

    July 10, 2007 at 5:39 am

    The first clip probably has a start and a duration, so you can figure out what the end would be, therefore you can figure out the start of the next clip. Then, since you know the duration of the second clip, you can figure out the end of the second clip and the start of the third, and so on…

    — Wes Plate
    Automatic Duck

  • Jabran Soubeih

    July 10, 2007 at 6:11 am

    The duration of the first clip and all of the clips is the duration of the source clip which is bogus since they are actually stills. They have a default duration that I had set when I imported them using original XML import file. Duration in the XML export file is associated with the duration of the source clip not the duration that clip is on the sequence which is what I need.

    Jabran

  • Andy Mees

    July 10, 2007 at 6:20 am

    Jabran

    When you import your XML back into FCP does the imported version of the sequence appear correctly?

    If YES, then there is nothing wrong with the XML. The only problem is your expectation that it should work the way you want it to, rather than the way its does.

    If NO, then there you might be in the unfortunate position of having uncovered a bug in the XML export

    Let us know either way. If its the former then maybe we can help you to figure out how you calculate this value for your needs. If its the latter then maybe we could help verify the bug.

    Cheers
    Andy

  • Jabran Soubeih

    July 10, 2007 at 6:24 am

    The file will not import properly back into FCP. Here’s a link to the xml file on my webserver:
    https://www.furriestdog.com/20th_xml_2007-07-05.xml

  • Andy Mees

    July 10, 2007 at 6:47 am

    Jabran, can you zip it up and email it to me, together with the original project file? cheers Andy

  • Jabran Soubeih

    July 10, 2007 at 1:08 pm

    Andy,
    I don’t see your email in your profile or in the post?

    I put the zip file on my website at: https://www.furriestdog.com/20th_slideshow_2007-07-10.zip if you can download it from there?

    Jabran

Page 1 of 2

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