-
In a pinch (vegas hates .mov files)
I’ve got a time sensitive problem regarding Sony Vegas handling files that came out of Final Cut Pro. According to the person who rendered the files, they are h.264 files (vegas recognizes the files as mpeg-4 and they are in the quicktime .mov wrapper — GSpot marks the codec as mp4v).
Now, dealing with one or two of these files at a time in vegas seems to be no trouble. The files are recognized, and playback works without a hitch. The issue occurs when larger numbers of files are imported (say anything more than 4 at a time). If during an import or drag/drop command, vegas will fill up my RAM and lock up (eventually requiring me to force the app to quit). Similarly, if I import files 1 or 2 at a time, but have more than 6-7 in my project media and attempt to click anywhere…same problem.
I don’t think the problem is hardware related (currently doing the rough assembly on a laptop (Processor: 2.16 Core 2 Duo, 2GB RAM 800Mhz, 160hdd @ 7200rpm). Not a powerhouse machine, but I doubt it should be freezing up like this.
I’ve already started encoding each file over to a huffyuv .avi in the event that a quicker fix can’t be found…but as that equates to 326 separate, grueling renders and I’ve got just over three days to have an assembly done, I’m really hoping someone has a better idea.
-
4 Replies
-
The problem stems from the quicktime decoder which isn’t native to Vegas. You’d have been better off using Prorez, which can be decoded properly without third party software (Quicktime).
Douglas Spotted Eagle
VASSTCertified Sony Vegas Trainer
Aerial Camera/Instructor -
I’m inclined to agree with that thought. However, as I wasn’t the one who had control over the initial render settings (and as the person who did no longer has access to the original files), I was hoping for a solution other than, “re-encode en masse.”
Well, I’m already more than halfway through converting the files, so that’ll have to do for now. But I am still curious: should something like this happen again, is there any other way to address this problem?
-
But I am still curious: should something like this happen again, is there any other way to address this problem?
As Spot said, the way to address the problem is to not have your Final Cut editor render to a format that Vegas cannot easily consume. Use ProRes422 or MXF.
If you’re asking if there is a way around getting MP4 files from Final Cut again, you could use a tool like VASST GearShift to convert the files into DV Proxies or Sony YUV intermediaries. GearShift basically automates what you are doing now manually.
~jr
http://www.johnrofrano.com
http://www.vasst.com -
I’ll keep GearShift in mind should this happen again (and meanwhile, I’ll continue to try and get the rest of my mac oriented group to make files that ‘play nice’ with windows and vegas). Thanks for all the info guys.
Reply to this Discussion! Login or Sign Up