XML export -1

[Andy Mees]

hey Jabran

opened the xml on my system and all worked fine … but got spinning beach ball of death before i could look at the timeline

opened project file and exported as xml from my system (xml v1 as per fcp 4.5)
reopened xml and all was fine, sequence identical to original timeline
would be happy to send you the xml but need an address to send it to.

cheers
Andy

[Jabran Soubeih]

Andy,
Yes, please email me the xml file at jabran at furriestdog dot com.

Regards,
Jabran

[Jabran Soubeih]

Andy,
The xml file that you emailed me has and values of -1. That’s the problem I’m trying to fix. I’ve been able to export an edl with proper timecode which I can use I just have to re-write my script that I was using to parse the xml to be able to parse the edl file which has a completely different format.

Jabran

[Wes Plate]

The -1 values are not a problem.

Perhaps you should ask your questions on the pro apps dev list.

— Wes Plate
Automatic Duck

[Jabran Soubeih]

What I want out of the xml file are the timecode in and timecode out points for each clip. It appeared to me from creating another sequence that the timecode in and timcode out points for a clip in the sequence were written to and . There is also and values but if you look through the xml file you will notice the values for those fields don’t incrememnt.

[Andy Mees]

Jabran

I refer you back to the post way back when I explained:
…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.

you can harp on here as long as you like but the problem is your expectation. you seem aggrieved that the xml does not hand you on a plate the values that you want … but the values you need are indeed all there; witness the fact that when you import the xml the sequence is correctly recreated. you just have to calculate them from the given data my friend. lots of people using XML automation methods do exactly that, and you just have to get on and do this too. (or you could just carry on blindly stating the xml is “wrong”, your choice)