Comments

JohnnyRoy wrote on 7/3/2009, 9:01 AM
> Any ideas?

Move the Waves plug-ins out of your VSTPlugins folder just to get Vegas Pro 9 to load. Then move them back one by one to see which one is causing the problem. Strange that Vegas 8 works fine. Could be a problem with the way V9 handles VST's. I would report it to Sony.

~jr
Steve_Rhoden wrote on 7/3/2009, 9:22 AM
On the contrary.....Vegas 9 works better with the waves plugins than
Vegas 8....A re-install of Waves, sometimes help.
FrankLP* wrote on 7/3/2009, 9:25 AM
Thank jr.

Actually, I followed your suggestion - removing the WaveShell dll from the vstplugins folder; started up V9; closed V9; replaced the Waveshell dll; and everythings seems to be fine. Weird, but good.

MPM wrote on 7/3/2009, 10:17 AM
"Weird, but good."

FWIW, & in case it helps in the future...

Whenever Vegas, or many other Sony apps 1st fire up, they scan for plugins. The list of found plugins, DS filters etc. is stored in the registry, so after an in depth scan subsequent starts don't need or use the extra scan times. When the software picks up changes -- I've never looked to see how/why -- it initiates a full scan once again.

Bluntly, that in depth scanning routine stinks -- could be coded better. It's quite in depth, so much so that it includes files that are at best remotely involved with media handling in Windows, & have no bearing what-so-ever on the Sony app you're using. If this in depth scan finds something it doesn't like, everything halts & the app can crash.

In this case re-locating the file I'd *guess* allowed the scan to complete, which was the main thing. With everything now written to the registry, it won't look again -- until something triggers another in-depth scan -- & things will work normally.

Reason I'm posting all that, is on the chance it (or something similar) ever happens again... I've got a terrible memory & so have already added it to my notes. Thanks.
:)