Using XML Export in Vegas Question

JasonATL wrote on 3/18/2013, 9:25 AM

I asked a question before about Resolve and Vegas before (http://www.sonycreativesoftware.com/forums/ShowMessage.asp?MessageID=853548&Replies=0), with no response. In that thread, I describe how Resolve fails to import and link files from Vegas Pro 12, but it has no problem with the identical timeline and files using Premiere Pro. This includes the odd behavior that I can export to a PPro project first, use PPro to export an XML file and read/link successfully in Resolve. That is, putting Premiere Pro between Vegas Pro 12 and Resolve fixes the problem. This leads me to believe that Vegas Pro 12 has some error in its XML exports.

I've started this thread in the hopes that a someone has some insights to a more general question about XML exports.

It appears to me that Sony's XML exports are not compliant with whatever DaVinci Resolve is expecting. Specifically, Resolve seems to have trouble locating and linking files from a Vegas XML export.

In my testing, the problem arises when trying to use the original source files in Resolve (not the files rendered from Vegas).

Does anyone here use a Resolve workflow and/or XML? Any issues or tricks that you suggest?

Thanks in advance.

Back to post

Comments

Former user wrote on 3/24/2013, 2:59 PM

Jason,

Finally got an XML to import correctly. I had to delete the audio track from my project. This audio track had an MP3 music track that had been edited so I don't know if it was the format or the existence that caused a problem.

In order for TC to work right, I rendered the Prores to a DNXhd file which defaults to a 00:00:00;00 timecode so it syncs up. But I would hate to have to add the extra render and quality hit for this to work.

edit: Okay, without an audio track, it works with the Original Prores file as well, if I change the properties within Vegas to the correct timecode. So apparently, my audio track was messing things up. Weird.

Dave T2

TiDa wrote on 3/25/2013, 7:54 AM

I'm wondering if you did look at below concept. XML export /import seems to be really sensitive as you mentioned that another audio track gives trouble...

This would work....

http://personal-view.com/talks/discussion/6238/edl_convert-workflow-developement-for-sony-vegas-pro-davinci-resolve-/p1

JasonATL wrote on 3/25/2013, 10:02 AM

This would work....

TiDa: Correct me if I'm wrong, but the workflow in the link you provided does not seem to accomplish one key goal that some (many?) of us have, which is to color grade the using the original source files or in as few generations as possible.

This issue would be less important for me if I were not using 12-bit raw source files. For example, if I started with 8-bit 4:2:0 files, then the loss of quality over one (or two?) generation of re-rendering might be negligible, given the high-quality DNxHD renders. But, if I'm starting with 12-bit raw and rendering to 10-bit (even 4:2:2), I'm losing some of the key point that I used 12-bit raw in the first place.

I haven't tried the workflow in the link you provided, so I'm not sure if I am correct that it relies on second-generation files in the Resolve color grading step. It appears to me that it does, so I would appreciate any clarification.

JasonATL wrote on 3/31/2013, 11:23 AM

For anyone that cares:
I've posted a script here that infers the timecode from Blackmagic Cinema Camera files and sets the custom timecode in VP12 to the correct timecode. It seems to work for both QuickTime (DNxHD) files from the camera and QuickTime (DNxHD) files that are rendered from raw .dng files from the camera. See the script and post for details. This makes it so that XML exports from Vegas to Resolve successfully match to the original source files in Resolve.

Unfortunately, this script is really only useful for Blackmagic Design Cinema Camera files because it is using the naming and timecode conventions that are specific to that camera (all of which I inferred and any of which are probably subject to change in firmware updates to the camera and version updates in Resolve).

But, absent Vegas Pro 12 working like it should, this is my temporary workaround. The problem with VP12 remains: VP12 is not reading the timecode from QuickTime files. If it did, that would seem to make the interoperability with Resolve work as it should and as it does with other NLEs.

videoITguy wrote on 3/31/2013, 3:04 PM

JasonAtl, while you acknowledge this script has a narrow fitting app /user community - you are exactly on the right track - more of this kind of development needs to be done.

Do you mind if we approach, a forum member, who would be more interested in taking your exploratory work, and going with a full bore release package?? Not concerned about copyright, but that you give your blessings to such a person's work. They should give you credits but I alone cannot guarantee that that will happen.

Ahimoteb99 wrote on 9/8/2023, 6:26 PM

I'd just like to add to this thread that I had an absolute nightmare trying to get myproject from my Vegas 17 to the DaVinci Resolve of my colourist. The XML export in Vegas and the export to Premiere simply don't work, and I was about to upgrade to Vegas 21 but have now decided after long years to change to DaVinci.

If anyone is stuck: In the end I paid $59 for AA Translator. It's a bit of a tricky install as you have to install a script into Vegas, but it spit out the XML files instantly.

https://www.aatranslator.com.au/

Former user wrote on 9/9/2023, 12:50 AM

Most of the interchange options in VEGAS Pro are woefully out of date.

The FCPX XML option is useless for going to Resolve because it is the first revision and Resolve will reject it due to being too old/out of date (it only supports newer revisions of that "standard"). The Premiere Pro XML option wasn't reliable, last time I checked.

AAF is not reliable, and AAF import was even less reliable.

FCP7 XML did work, but the order of tracks was reversed when going from VEGAS to Resolve Studio, which is "fine for Audio (Track Order is only an organizational consideration), but a complete showstopper for Video.

Even still, the Options when exporting for formats like AAF are woeful.

The development team needs to address this, and make at least one reasonably functional option available for people who need to go from VEGAS to Resolve and/or Pro Tools, as those two packages are industry standard in the film industry. Even for indie films, if you contract out the color and audio work to anyone, they are more likely to be using Resolve Studio or Pro Tools than anything else.

This is not about whether or not someone can do it in VEGAS. It's about being reasonably compatible with Specialist Professionals who you may contract/hire to do this kind of work. Time is money.