Does anyone know of a way to take a VP project into Resolve without using Premier as an intermediate step?
I've got a project with a few hundred clips on a single timeline, I've cleaned it of all fx and transitions but there doesn't seem to be any way to get the xml from VP into Resolve.
What in particular are you trying to do in Resolve? If it's just coloring, I'd just render out an intermediate like ProRes and send it over that way. VEGAS' external editor export options have been in need of upgrading for years, but it'll be a while before that happens, they are currently rewriting the video engine to make VEGAS much faster and more stable, and that work is likely going to take priority for now... as it should, VEGAS sorely needs it.
Follow this 
. It is a Youtube video by Doug De Young, that I found years ago, and which should still be applicable. Of course, possibly some minor differences, but You should be able to "Adapt & Overcome".
It was actually the first video that came up on my search query at Youtube of: "roundtrip vegas pro and davinci resolve".
Mike
out of curiosity, what things specifically? I might be able to offer some tips, or at least offer suggestions to the development team for future upgrades to VEGAS.
@fr0sty you're not supposed to admit that you're in the same group I am :-)
I'll PM you
Haven't done this for several years now, but likely it has not changed... FCP 7 XML from Vegas will import into Resolve IF YOUR CLIPS HAVE VEGAS READABLE SOURCE TIMECODE. You can check this in the clip properties. Stills also work BTW.
@Kinvermark I'm not seeing anything in the properties that says one way or another if the timecode is vp compatible.
Something like above. Otherwise will just be zeroes, I think.
Another thought.... won't work with mixed frame rates either.
@Kinvermark Well, I definitely have a mix of frame rates and resolutions. I'll see if limiting an export to the same settings changes the behavior as well as setting a custom timecode
@Kinvermark Turns out it *will* work with mixed frame rates and resolutions but the solution isn't obvious. To me at least.
I did finally manage to get the entire timeline imported with only a few clips showing offline. A conform on those clips fixed things.
I'll write this up in a tutorial form so future me and others don't have to waste so much time figuring it out. At least until something changes. Again.
Glad you made it work :) Double check the clips that don't have the same "base" frame rate specified in your Vegas project. I haven't done this in a long time so I don't remember exactly what failed, just that there was a problem - maybe the clips import, but the edit points are off for the "oddball" framerates?
@Kinvermark it's worse than you described.
I needed to first review the clips that showed a usage count of 0 (mostly 120fps clips) to make sure they shouldn't be used and when I went back to review the 59.9 clips I found that nearly every clip imported into Resolve with the identical base filename.
So, I need to do more experimentation tomorrow. Tonight, a Gibson is calling my brain.
@Kinvermark Well, I'm going to give this up for now as a lost cause. VP can't properly read the timecodes from the gopro footage I'm using and even when I manually input the correct timecodes into the field you showed, VP exports using 0 as the starting tc for every clip