Serious glitches in 12

Bill@cinevid wrote on 9/7/2013, 9:14 PM
Equipment: i5 Intel and i7 Intels, Windows 7, USB 3 drives, 16 gigs of ram, several recommended graphics cards.

Whenever I have more than one instance of Vegas running, the second one's video preview completely freaks out. Artifacts, blanking, freeze frames and even video from the other project suddenly appear and flicker all over the place. Only seems to happen with usb drives, WD MyBook more than Seagate.

Now I even have audio problems. Pieces from other tracks and other clips invade each other and unlike restarting and only running one instance, which fixes the video flashing, these glitches are permanent. I was able to fix some by using media encoder and making aac conversions from wav files.

The program is freaking out!!! However since Sony chose not to make anything backward compatible, I'm totally screwed.


Steve Grisetti wrote on 9/8/2013, 8:35 AM
I've certainly never experienced anything like this. But I also don't have 'several recommended graphics cards', which may or may not be causing the problem.
Kimberly wrote on 9/8/2013, 8:49 AM
[I]However since Sony chose not to make anything backward compatible, I'm totally screwed. [/I]

Very strange. I use a Dell XPS laptop. I had two instances of Vegas 12 running yesterday with an external USB Western Digital drive plugged in. No issues here, but that doesn't help in your circumstance : (

You may have already thought of this regarding backwards compatibility -- you can open an instance of VP 11 or prior and copy/paste material from your VP 12 project into the prior version project. That's not a perfect solution but may give you a jumpstart rebuilding your work in a version that is stable for you.


willqen wrote on 9/8/2013, 8:16 PM
I've had problems like this before.

Sounds to me like Vegas has been corrupted somehow.

Vegas does not normally behave that way.

Look on the SCS web site. They give instructions on how to uninstall Vegas (and any other SCS software you may have installed unfortunately) and clean up your registry.

As I mentioned this has happened to me. It usually occurs from another piece of software installed after Vegas is installed, or perhaps codecs or codec packages installed.

Try to always install Vegas last.

I haven't had any problems with this type of issue since I have maintained Vegas as the last major software install on my system.

By the way, uninstalling, cleaning the registry, and reinstalling your SCS software is not nearly as painful as it sounds.

You will need your serial numbers and activation codes but, you only need to install from the latest update.

SCS includes the entire program in all it's updates so reinstalling does not require starting with version 1 and then running all the various updates and builds, just the most recent.

Good Luck,

Bill@cinevid wrote on 9/9/2013, 6:23 AM
Steve, I got the company I work for to switch from Avids to Vegas, so I was meaning several different machines with nVidia cards.

Kimberly, I was hoping to avoid that because I built a bunch of text on screen with the newer titler, so I'm afraid of losing them. S'pose I could see what happens huh..

Willgen, I'll give it a try. We have the adobe suite CC and it was put on after Vegas.

Thanks folks!
Ros wrote on 9/9/2013, 1:45 PM
Bill, have you got GPU turned on?

I was never able to run a second instance of Vegas with GPU on without any glitch.
Therefore it is always turned off and I usually have 3 to 4 instance of Vegas running at the same time without any issues.

Only recently I was curious to check build 670 with GPU on..... just a quick render and it messed it up....
larry-peter wrote on 9/9/2013, 3:23 PM
I had the same happen once when I several instances of VP12 open on my system2 (560ti), but I also got an Nvidia error message. Something that basically said I was overtaxing the card and should close some programs. That was soon after installing and I do believe GPU was on at that time. It's generally off now.