Tom Roper
December 26th, 2013, 02:00 PM
I've worked through about 250 of the 741 page manual, certainly have lots to learn, many features I like, but basically it comes down to this, and I'd like to hear from users who edit in Vegas 12 and grade in Resolve.
My observations from using Resolve with the Sony PMW F55 and 4k S-Log2 29.97 fps are as follows:
I haven't found anything grading wise that the Vegas plug-in chain doesn't do as well or better than Resolve nodes for grading. ACES workflows, input Luts and transformations, 32 bit grading precision, YUV 10 bit, 12 bit, 16 bit output, some different tools and variations but it's all there to get the same look and the same quality from either.
I exported a Vegas 4k project XML and Resolve opens a new timeline with the Vegas edited clips and media pool. View the clips in Resolve using the appropriate viewing Luts or input transformations for ACES, color grade with the node tools. Deliver a rendered file or multiple files in YUV 10 bit AVI or other codec of choice. Of course, it came out beautiful! Interesting but I can do the exact same thing, and actually arrived at the same intended color grade and quality from within the Vegas 12 environment, only much faster. I prefer the toolset within the Vegas plugin chain to the node based tools within Resolve, primarily because of familiarity but the controls themselves are nearly instant responding, whereas the Resolve tools are slower and more computer resource intensive. In other words, lag time. To use it proper, Resolve specifies very precisely a high performance computer spec that they recommend for you to have in your editing system. I was able to run most things like timeline scrubbing/viewing in near real time, particularly with the proxy files, but the grading tools themselves are laggy, extending the time it takes. The grading tools for me seemed to speed up by switching OFF the proxy files in Resolve.
The big advantage Resolve has over Vegas is that you can choose from many high quality 4k rendering codecs. Vegas12 in comparison, can output very high quality renders in 10 bit YUV and uncompressed AVI, or DNxHD or XDCAM for HD but any of the other 4k output codecs in Vegas12 including XAVC, are poor. To me, please share your opinion about this, but that's the single most huge benefit for Resolve when almost all the other aspects of usability including speed and audio favor Vegas12.
If you make the round trip and import the Resolve graded clips back into Vegas for finishing, you've just thrown away the most important reason for using it, the rendered ProRes, jpeg2000, Open EXR, Cinema DNG 4k, R3D (etc.) output. Now your going to re-encode that to something lesser in Vegas12? Makes no sense! Yet on the other hand, Vegas can grade equally well with 32 bit precision using its plugin chain of tools as long as you render to uncompressed. The moral...don't let Vegas compress your renders.
That said, I have a lot of experience in Vegas12, not so much in Resolve. And of immediate note as I mentioned in the opening paragraph, the beautiful, extremely well written 741 page user manual for Resolve, yet I would trade that in two seconds to have Vegas12 context sensitive help, which is always there at a single click. The Vegas12 live help would probably amount to that many pages or more, but without having to refer to a large document or pdf. That's the single most compelling advantage for Vegas12 in my opinion.
Rendering takes the same time in either one, the previewing windows are about equal, the grading toolset have some variations between them but both can get you the same look, the same no-compressed quality. Resolve includes basic tools for editing, it is not necessary to use a NLE but for me it is helpful, since I struggled more with some simple things like a cross dissolve transition than I did with color grading and waveform monitors, which were quite intuitive. Unless I'm mistaken, titling is more powerful and libraries of effects are much more comprehensive in Vegas12.
Again, I'm interested in your experiences. For me, it will be necessary to use both products until someone points out for me how I am under-appreciating DaVinci Resolve, which is certainly possible. Just point out how. Thanks.
Edit: And Raw. Vegas12 doesn't do Raw, an essential benefit to Resolve if shooting raw.
Tom
My observations from using Resolve with the Sony PMW F55 and 4k S-Log2 29.97 fps are as follows:
I haven't found anything grading wise that the Vegas plug-in chain doesn't do as well or better than Resolve nodes for grading. ACES workflows, input Luts and transformations, 32 bit grading precision, YUV 10 bit, 12 bit, 16 bit output, some different tools and variations but it's all there to get the same look and the same quality from either.
I exported a Vegas 4k project XML and Resolve opens a new timeline with the Vegas edited clips and media pool. View the clips in Resolve using the appropriate viewing Luts or input transformations for ACES, color grade with the node tools. Deliver a rendered file or multiple files in YUV 10 bit AVI or other codec of choice. Of course, it came out beautiful! Interesting but I can do the exact same thing, and actually arrived at the same intended color grade and quality from within the Vegas 12 environment, only much faster. I prefer the toolset within the Vegas plugin chain to the node based tools within Resolve, primarily because of familiarity but the controls themselves are nearly instant responding, whereas the Resolve tools are slower and more computer resource intensive. In other words, lag time. To use it proper, Resolve specifies very precisely a high performance computer spec that they recommend for you to have in your editing system. I was able to run most things like timeline scrubbing/viewing in near real time, particularly with the proxy files, but the grading tools themselves are laggy, extending the time it takes. The grading tools for me seemed to speed up by switching OFF the proxy files in Resolve.
The big advantage Resolve has over Vegas is that you can choose from many high quality 4k rendering codecs. Vegas12 in comparison, can output very high quality renders in 10 bit YUV and uncompressed AVI, or DNxHD or XDCAM for HD but any of the other 4k output codecs in Vegas12 including XAVC, are poor. To me, please share your opinion about this, but that's the single most huge benefit for Resolve when almost all the other aspects of usability including speed and audio favor Vegas12.
If you make the round trip and import the Resolve graded clips back into Vegas for finishing, you've just thrown away the most important reason for using it, the rendered ProRes, jpeg2000, Open EXR, Cinema DNG 4k, R3D (etc.) output. Now your going to re-encode that to something lesser in Vegas12? Makes no sense! Yet on the other hand, Vegas can grade equally well with 32 bit precision using its plugin chain of tools as long as you render to uncompressed. The moral...don't let Vegas compress your renders.
That said, I have a lot of experience in Vegas12, not so much in Resolve. And of immediate note as I mentioned in the opening paragraph, the beautiful, extremely well written 741 page user manual for Resolve, yet I would trade that in two seconds to have Vegas12 context sensitive help, which is always there at a single click. The Vegas12 live help would probably amount to that many pages or more, but without having to refer to a large document or pdf. That's the single most compelling advantage for Vegas12 in my opinion.
Rendering takes the same time in either one, the previewing windows are about equal, the grading toolset have some variations between them but both can get you the same look, the same no-compressed quality. Resolve includes basic tools for editing, it is not necessary to use a NLE but for me it is helpful, since I struggled more with some simple things like a cross dissolve transition than I did with color grading and waveform monitors, which were quite intuitive. Unless I'm mistaken, titling is more powerful and libraries of effects are much more comprehensive in Vegas12.
Again, I'm interested in your experiences. For me, it will be necessary to use both products until someone points out for me how I am under-appreciating DaVinci Resolve, which is certainly possible. Just point out how. Thanks.
Edit: And Raw. Vegas12 doesn't do Raw, an essential benefit to Resolve if shooting raw.
Tom