Using Vegas 12 and Resolve - problem with XML?

JasonATL wrote on 3/15/2013, 10:44 AM
Is anyone successfully using Vegas 12 and Resolve to edit footage in Vegas 12 and then grade the raw files in Resolve? If so, please provide some pointers as to where I might be going wrong.

It appears to me that the Vegas 12 export to XML might not be working correctly.

Here's some background. I received my long-awaited BMCC camera this past week. It is amazing in terms of color, dynamic range, and resolution compared to my Canon DSLRs (and other video cameras that I've used).

What I'd like to do is edit in Vegas and color grade (post-edit) using the raw (.dng) files in Resolve. In theory, this should work as follows:
1. In Resolve: Create a media pool of raw .dng files from the BMCC
2. In Resolve: Render the raw files to .mov (proxies) files to use in NLE
3. In Vegas 12: Open the .mov files and edit
4. In Vegas 12: Export an XML file
5. In Resolve: Import the XML file, choosing not to import the media (i.e., to force it to use the same media pool as in Step 1). Resolve should automatically link with media pool files rather than the .mov proxies.
6. In Resolve: Color grade
7. In Resolve: Render final .mov files to be used in final render, replacing the .mov files that were created in Step 2.
8. In Vegas 12: Render final output (perhaps after adding some effects, titles, etc.)

If I replace "In Vegas 12" with "In Premiere Pro", everything works as it should. However, with Vegas 12, the import into Resolve (Step 5) fails to link up the media pool files with the clips from the Vegas timeline. This suggests to me that there is something I'm missing or something amiss with the Vegas XML export. By the way, I've tried the XML export both with and without copying the media with the same failed results.

Oddly, if I export to a prproj (Premiere Pro project) first from Vegas 12, open that project in PPro, save it as a different PPro project and then Export XML from PPro, it seems to work. Specifically, it does not fail at Step 5. This will be my workaround, I guess. But, I'd like to stick with Vegas without touching PPro for this specific workaround. Again, this suggests to me that the Vegas XML export is not functioning to spec.

Anyone else tried this?

Thanks in advance!

Comments

essami wrote on 3/24/2013, 4:54 PM
I'm interested in Vegas and Resolve workflow as well. No Vegas users are doing this?
TiDa wrote on 3/25/2013, 9:34 AM
I think you did post this also on BMD Forum. But might be worthwhile to have a look at this concept:

http://www.personal-view.com/talks/discussion/6238/edl_convert-workflow-developement-for-sony-vegas-pro-davinci-resolve-
JasonATL wrote on 3/25/2013, 10:05 AM
I posted this question to TiDa in the other thread, too. It is especially relevant in this thread that deals more specifically with BMCC files.

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.