View Full Version : Vegas 9 Import XML Scripts


Benjamin Smith
February 21st, 2011, 06:34 AM
Hello all

If there's anyone out there with Vegas 9 installed; could someone please email me the ImportXML scripts (which seem to have disappeared in Vegas 10)

thanks!

/ben

Mike Kujbida
February 21st, 2011, 07:17 AM
Better yet, in case anyone else wants them, here they are.

Benjamin Smith
February 21st, 2011, 07:46 AM
You sir are both a gentleman and a scholar.

/b

Mike Kujbida
February 21st, 2011, 09:22 AM
Glad to help Ben.
I hope they do what you need them to do.

Benjamin Smith
February 21st, 2011, 12:08 PM
Sadly this didn't work. The script runs but throws up an error.

Anyone got any ideas why this doesn't work?

And... is it just me or have Sony made it REALLY HARD to move your edit between Vegas and any other app?

/b

Mike Kujbida
February 21st, 2011, 01:15 PM
Ben, that script dates back to 2006 so my guess is that whatever changes Sony has made to the scripting API since then is responsible for the error message.
We'd need a script guru like Edward Troxel to tell us for sure.

And... is it just me or have Sony made it REALLY HARD to move your edit between Vegas and any other app?

I don't think it's just Sony.
I've read numerous complaints on other Vegas forums about folks who use different NLEs and have similar problems doing this.

Edward Troxel
February 21st, 2011, 01:50 PM
I haven't tried running those scripts in 10. I do know that there are some changes between 9 and 10 but nothing really major. There were only a few minor changes I needed to make to Excalibur to make it fully functional in 10 and it was mostly reading the audio presets. What error does it throw?

Benjamin Smith
February 22nd, 2011, 04:18 AM
Guys

Thanks for your replies. This is insanely frustrating as there seem to be three paths to move simple edits between Premiere and Vegas - AAF, XML and EDL; and none of them work, but all for different reasons.

The XML format apparently has different versions that are either "project" or "sequence"; so maybe Premiere makes the wrong kind of file.

/ben