In Sound Forge Pro, there are two ways to bypass VST scanning, one by appending the app's shortcut target . The other is in the hidden 'internal' menu. I do not know if either will work with VP but I will look into it.

Yes, that works with audio FX in Vegas Pro via the Options/Preferences/VST Effects (tab) option, but unfortunately there is no equivalent option for video FX in Vegas Pro.

Improvements to our handling of VST loading is something we would very much like to do. To this point, we have not had a chance to implement those changes.

Thanks guys, I don't use SFP btw my main audio applications are Cubase for music, Nuendo for movie compositions and sound design and Wavelab for mastering.

In my various versions of Cubase and Nuendo I can simply open an XML file if this is ever an issue and add plugins there that I don't want to be scanned. Wavelab simply has text file.

Also, all these applications do indeed have a timeout window that pops up if you are waiting for too long.

Anyway thanks again, I did finally get up and running. It took about 45 minutes from installation. :-)

Also yes of course VST3 would be great and just to reiterate that it is indeed possible to skip certain plugins, (I mentioned this in my first post) but not until the plugin list has been created first, and then viewed in Vegas prefs. (Which means that all plugins must be scanned first in order for Vegas to open.)

Improvements to our handling of VST loading is something we would very much like to do. To this point, we have not had a chance to implement those changes.

I don't understand why it's hard. I'm a programmer and it's just a snap. What you need to do is skipping to scan the vst folder and let users change it after launch. You just need to change a single line in the code.

There's probably a reason it is scanned at launch.

I go back to my comment of a year ago on this thread:

.. there was an excellent suggestion where VP would open a window for a problem plugin and ask if that plugin needed to be bypassed to progress the opening of VP.

Whoever it was who made that suggestion, to me that suggestion was the most practical that I have seen put forward so far.

@nothing If it was that easy the Vegas programmers would have implemented it long ago !

@nothing If it was that easy the Vegas programmers would have implemented it long ago !

You're probably right about that because here I am logging in to this thread two years later and my just upgraded Vegas Pro 21 is stopping at "scanning plugins". Luckily I can switch to another machine and leave the Vegas launch active (I hope....) for the rest of the day :-)

@nothing If it was that easy the Vegas programmers would have implemented it long ago !

Well...many developers don't fix the issue intentionally with some reason these days. It's kinda strategy. We never know. If you learn programming, you will understand what I'm talking about.
What they need is change a line of the code that scans VST on startup. But ordinary people don't understand it as they have no experience in programming.

Very odd that this has marked as [SOLVED]? Not a big issue for me tbh but the original question was:

How to tell Vegas please do not scan certain plugins before scanning? Is there a plugin blacklist for example?

As mentioned, yes, we can skip while scanning if a plugin is taking a long time etc. But there is still no way to do as I asked. We still have to wait for ALL plugins to be scanned before we can get to the list of plugins within Vegas and therefore exclude what we want. For some of us pro audio users with a large amount of plugins, this takes a lot of time. And there are a lot of useless plugins included there, for example VSTi.

As another example, some of them that use a shell type config need to be rescanned after every update. I find that on opening Vegas I am almost guaranteed a 10-minute wait before I can work.

This is not a complaint about how it works, it is fine, and I understand that this was obviously not priority. But the thread is not "solved".

@Phil_P I don't know why and by whom the thread got "Solved" but I "Unsolved" it about six hours before your last post so you shouldn't now be seeing it as "Solved".

@Phil_P I don't know why and by whom the thread got "Solved" but I "Unsolved" it about six hours before your last post so you shouldn't now be seeing it as "Solved".

Cheers Eric. As I said, not a biggie and most likely there will never be an exact solution to this. But yes, just for the sake of saving time for anyone who has the same question, and unable to find the answer, better to be correct, I guess.

Thanks again.

This is what Reaper shows when it needs to do a scan of VSTs and one is taking longer than expected.

I think it's a good solution although I think "exclude" might be a better term than "terminate", and in Vegas it should advise the user to check Preferences > VST Effects to control available VST plugins.

Since you can have many VST folders, I keep the Vegas friendly VSTs in one folder and only read it for Vegas. For my DAWs I can then read all folders.

This is what Reaper shows when it needs to do a scan of VSTs and one is taking longer than expected.

I think it's a good solution although I think "exclude" might be a better term than "terminate", and in Vegas it should advise the user to check Preferences > VST Effects to control available VST plugins.

Yes, Cubase / Nuendo also does this, as does Wavelab, but this was not my question.

Since you can have many VST folders, I keep the Vegas friendly VSTs in one folder and only read it for Vegas. For my DAWs I can then read all folders.

Most VST3 installations do not "like" being moved although they can be referenced with symlinks. However, this was not my question. I was trying to find the file or area that Vegas stores the list of excluded plugin.
 

Not to worry, as mentioned, no biggie. Cheers, P.

Yes, Cubase / Nuendo also does this, as does Wavelab, but this was not my question.

I posted that to add to the discussion, and in the hope that it might be spotted by someone with the power to influence the implementation of something like this in the future.

To directly answer your questions...

So the question is how to tell Vegas please do not scan certain plugins before scanning?

By moving them or changing the name of the folder they are in.

Is there a plugin blacklist for example?

Not that I have ever heard of.

I was trying to find the file or area that Vegas stores the list of excluded plugin.

The included/excluded status is stored in the registry in a key such as this:

Computer\HKEY_CURRENT_USER\SOFTWARE\VEGAS Creative Software\VEGAS Pro\21\Metrics\x64\VstCache\Mappings\{18ED4FBD-FF49-4739-0371-0007E95D36FA}\Enabled