VEGAS Pro cant export XML for Davinci Resolve

alifftudm95 wrote on 10/31/2020, 1:38 AM

I can export/convert VEGAS Pro 18 project into Premiere Pro projects by exporting an XML file.

Pr import the XML from VEGAS Pro 18 very well. You can see the comparison between VEGAS & PR timeline:

Off course, some stuff will be ignored like Generated Text Media, video FX, composition etc when importing XML into PR. But, as far as I remember, scale (Strictly SCALE, no rotation) via Pan/Crop will be read/reflects in Premiere Pro, as well normal fade transitions on Video & Audio, which is great too.

But, from the same XML, I cant import into Davinci Resolves. It will prompt me with this error saying clips is missing, despite having a dedicated folder with the used clip from VEGAS media pool. Weird things it only read MOV file, not any other container like MP4.

The only solutions for me to export XML from VEGAS to Davinci Resolve (Im doing cuts in VEGAS and send the footage to colorist) is by importing the XML into Pr first, then only re-export the XML via PR for making sure Davinci able to import the timelines.

I hope VEGAS Team can fix this error.

Comments

Deata wrote on 10/31/2020, 11:36 AM

You don't happen to be using a Sony a series camera ?

Because if you are, the xml export error to Davinci resolve is an issue with davinci and not vegas.

Resolve has a bug where it gets confused by the internal timecode of XAVC-S files coming from a series cameras when importing an xml, so far i have had no luck trying to figure out how to go past this issue.

Only solution seems to be to replace all files shot with a series cameras with proxy files and then when in resolve swap them back to original ones.

alifftudm95 wrote on 10/31/2020, 12:23 PM

You don't happen to be using a Sony a series camera ?

Because if you are, the xml export error to Davinci resolve is an issue with davinci and not vegas.

Resolve has a bug where it gets confused by the internal timecode of XAVC-S files coming from a series cameras when importing an xml, so far i have had no luck trying to figure out how to go past this issue.

Only solution seems to be to replace all files shot with a series cameras with proxy files and then when in resolve swap them back to original ones.

The media is a mixture between Sony a6500 footage (XAVC-S) & DJI Mavic Air footage.

I tried using ProRes media from ARRI Alexa cam & MXF media from Sony FS cam, same result:

I still think its a issue from VEGAS, because Davinci import XML timelime from PR with no problem at all, same media too as in VEGAS.

The only solution for now is to send XML from VEGAS to PR, re-export from PR and import into Davinci Resolve.

Kinvermark wrote on 11/1/2020, 3:46 AM

@alifftudm95

Look up my old posts about XML to Resolve. Works fine. But there are issues and they exist more on the Resolve side than the Vegas side. (Just do some research on the BM DR forum and you will see that imports from ANY of the main NLE's can be problematic, but also can usually be solved by simplification or change in media types used. SOURCE TIMECODE is often the main issue.)