Vegas Pro 8 demo corrupted older installed version

rich-macdonald wrote on 12/24/2007, 5:03 PM
Hello everyone. Been a couple years since I was a regular here. (Just extremely busy doing non-video work, otherwise no excuse.) Anyway, this bug is only going to infect a few of us special cases who are working with very old versions of Vegas, but its painful nonetheless.

Vegas used to do its "save as" by storing the audio and video files separately. The latest version (and perhaps several before; I wouldn't know) stores a single file as interleaved.

If you download the Vegas Pro 8 demo, but your current Vegas version does things the old way, your current version will be corrupted: The first file will separate and store the audio and video correctly, but every other audio file will include the video and every other video file will include the audio.

So far, I have uninstalled the Vegas Pro 8 demo, uninstalled and reinstalled my current version of Vegas, and removed every reference to Vegas 8 in the registry (poor uninstall; lots of registry poopies left lying around) without success. Next step is remove all registry references to the old and the new versions, but I am worried that Vegas 8 installed something into the System folder.

I tried to search the forum, but "save as" had no hits and I couldn't think of other searches. So sorry if this is well know.

(Incidentally, I have a new ipod, so I wanted to check out the ipod rendering capabilities. Should have just searched the forum instead, :-()

Comments

rich-macdonald wrote on 12/24/2007, 7:04 PM
A total eradication of everything Vegas-related from the registry was no help. After a little exploring, the effect on the earlier version of Vegas is as follows:

1) If you have trimmed the clip, things are fine, i.e., Vegas stores separate audio and video files.

2) If you have not modified the clip, then it stores two identical files (named avi and wav), both of which are identical to the original.

I'm testing this on Vegas 5 & WinXp right now.

I depend on separating the files, because I use a deshaker script that appends a 30-frame audio-free file, and virtualdub can only append "like" files, so this is an irritant. At least I have a workaround now (trim 1 frame from every clip), and I only have to do it for files that will be deshaken. I'll explore further. Hopefully this is just an isolated case of one person just being too far back in the upgrade game.