From Vegas to Resolve and back to Vegas : it works !
Posted: Fri Aug 23, 2013 9:18 amHi,
With Resolve 9.1, Vegas pro 12 export/import works like a charm. There were some scripts and tricks (exporting to Avid from Vegas) that are partly working. The official Vegas export to xml is the way to go !
There is just a few things to know, but once you get a success, it works for the whole movie:
- From Vegas, simply export to XML (Resolve/FCP option) into a directory
- Import that file in Resolve. Here, you can get an error message, where Resolve can not find the original medias (for some strange reason, the directories passed in the XML are not well read in Resolve) either from disk or from the media pool. No panic, Resolve will ask you to choose where the first source is located, and will try to discover the other medias in the same directory (so it is not a huge task if all your source medias are in the same dir.)
- You can get another issue here : Sometimes Resolve refuses to link the source media to the timeline. The reason is that there is a mix of timeline res (50 and 25 for instance) in the XML (not in the source media. I had this issue because, in Vegas, I dropped in different types of files when editing and trying ideas, some files where at 50, so the concerned timeline in vegas switched to 50, while another timeline of the the same project, was at 25. So I had that timeline converted to 50, I deleted the source, imported a new one at 25, but the timeline stayed at 50. The project was made of 25fps sources, but some tracks were at 50, and resolve does not like this situation (even if you play with all the different settings of mixed timecode). Solution ? Just changes (in the properties of each track) the timecode, set it to the correct value (25 in my case))
If you correct this, you now have something perfect in Resolve !
Exporting:
There is nothing special about exporting, it works fine, except that the soundtrack is lost (though it is correctly imported in Resolve)
The only solution I found is :
I create a nested project in Vegas;
- the main project includes a subproject with videos only
- The main project also includes the sound
When you export to resolve, just export the subproject, so you won't have to reinclude the sound.
Conclusion:
What happens in Vegas does not always stay in Vegas !
With Resolve 9.1, Vegas pro 12 export/import works like a charm. There were some scripts and tricks (exporting to Avid from Vegas) that are partly working. The official Vegas export to xml is the way to go !
There is just a few things to know, but once you get a success, it works for the whole movie:
- From Vegas, simply export to XML (Resolve/FCP option) into a directory
- Import that file in Resolve. Here, you can get an error message, where Resolve can not find the original medias (for some strange reason, the directories passed in the XML are not well read in Resolve) either from disk or from the media pool. No panic, Resolve will ask you to choose where the first source is located, and will try to discover the other medias in the same directory (so it is not a huge task if all your source medias are in the same dir.)
- You can get another issue here : Sometimes Resolve refuses to link the source media to the timeline. The reason is that there is a mix of timeline res (50 and 25 for instance) in the XML (not in the source media. I had this issue because, in Vegas, I dropped in different types of files when editing and trying ideas, some files where at 50, so the concerned timeline in vegas switched to 50, while another timeline of the the same project, was at 25. So I had that timeline converted to 50, I deleted the source, imported a new one at 25, but the timeline stayed at 50. The project was made of 25fps sources, but some tracks were at 50, and resolve does not like this situation (even if you play with all the different settings of mixed timecode). Solution ? Just changes (in the properties of each track) the timecode, set it to the correct value (25 in my case))
If you correct this, you now have something perfect in Resolve !
Exporting:
There is nothing special about exporting, it works fine, except that the soundtrack is lost (though it is correctly imported in Resolve)
The only solution I found is :
I create a nested project in Vegas;
- the main project includes a subproject with videos only
- The main project also includes the sound
When you export to resolve, just export the subproject, so you won't have to reinclude the sound.
Conclusion:
What happens in Vegas does not always stay in Vegas !