I’m using Vegas Pro 8 and have been using it or its consumer-oriented predecessor(s) for some time, about 5 or 6 years, at least. Pro 8 since about early summer 2008?
Due to the limitations of my previous computer and budget, I did a lot of projects where I’d shot in HDV, but captured in SD/AVI. I have one particular project where I have a heavily keyframed timeline, especially on the video stream, and I’m now considering replacing the SD capture with its HDV/M2TS counterpart.
Is there a simple way to copy the envelope(s) from the SD clip in my project onto the HDV footage — or sort of swap the footage and retain the full envelope information?
The best online version of this project probably is the one that appears here:
https://www.vimeo.com/2589796
Would defining the HDV footage as a separate take be a good approach? Or is there something much simpler? I’ve just tried getting my head around the way multi-camera takes work in Vegas, and I have to say so far I’m a little frustrated, but then the footage I was using in that project was not really multicamera per se, but separate takes from separate nights’ performances, each with unique timing that might not have been ideally suited for treatment under “multicamera editing”?
This is nothing 12 hours or so of hands on work won’t cure — but before I do that, I wanted to see if there are better ideas, especially when, in the old project I wanted to freshen up, the footage is really essentially identical, except that the one version has been downconverted. The source tape is the source for both clips.
Of course one twist I’m already noticing is that my original project consists of 3 separate clips in AVI (due to the 640MB limit?) while the HDV capture got all that as part of in one considerably longer clip.
Pointers to the right tutorials would be appreciated, as I suspect this is simpler than I’m making it at the moment.
Some contents or functionalities here are not available due to your cookie preferences!
This happens because the functionality/content marked as “Vimeo framework” uses cookies that you choosed to keep disabled. In order to view this content or use this functionality, please enable cookies: click here to open your cookie preferences.