Skipping VST Plugins on Launch

Phil_P wrote on 8/18/2021, 7:44 AM

I guess this only really applies on first launch but it happens to me regularly as I do a lot of testing work.

On first launch, Vegas scans VST Plugins.

I have a ton of Plugins that would be useless (and many that are indeed very useful) in Vegas, many of them are Instruments and also things like the UAD Plugins (I have the full collection) and Waves (also full collection) which simply don't work very well within the Vegas environment.

Now for example I have just installed Vegas 19 and it has already crashed once on the startup scan which took about 15 minutes. And now it I'm on my second startup. The scan is taking (understandably) for ever. :-)

The thing is, I could of course temporarily move the VST Plugins and then start again. Then tell Vegas to ignore certain useless/needless ones etc. But in order to be able to do that, we have to actually have them there in the list, which doesn't happen unless they are scanned... (And tbh moving them should really not be necessary).

So the question is how to tell Vegas please do not scan certain plugins before scanning? Is there a plugin blacklist for example? I have searched and cannot find anything relevant yet. I think there are some other music producers/composers here. I wonder if anyone else here is using Vegas with a large amount of plugins. (I am talking about 500+ plugins).

Cheers, P.

Comments

Dexcon wrote on 8/18/2021, 7:56 AM

So the question is how to tell Vegas please do not scan certain plugins before scanning? Is there a plugin blacklist for example?

This question/issue has been asked/raised many a time on the forum over the years. Thus far, there hasn't been a way to exclude problem plugins. Within the last few months, 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.

With VP19, there's unfortunately nothing so far which suggests that VST3 is now supported.

Cameras: Sony FDR-AX100E; GoPro Hero 11 Black Creator Edition

Installed: Vegas Pro 16, 17, 18, 19, 20 & 21, HitFilm Pro 2021.3, DaVinci Resolve Studio 18.5, BCC 2023.5, Mocha Pro 2023, Ignite Pro, NBFX TotalFX 7, Neat NR, DVD Architect 6.0, MAGIX Travel Maps, Sound Forge Pro 16, SpectraLayers Pro 11, iZotope RX10 Advanced and many other iZ plugins, Vegasaur 4.0

Windows 11

Dell Alienware Aurora 11

10th Gen Intel i9 10900KF - 10 cores (20 threads) - 3.7 to 5.3 GHz

NVIDIA GeForce RTX 2080 SUPER 8GB GDDR6 - liquid cooled

64GB RAM - Dual Channel HyperX FURY DDR4 XMP at 3200MHz

C drive: 2TB Samsung 990 PCIe 4.0 NVMe M.2 PCIe SSD

D: drive: 4TB Samsung 870 SATA SSD (used for media for editing current projects)

E: drive: 2TB Samsung 870 SATA SSD

F: drive: 6TB WD 7200 rpm Black HDD 3.5"

Dell Ultrasharp 32" 4K Color Calibrated Monitor

rraud wrote on 8/18/2021, 9:05 AM

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.

Dexcon wrote on 8/18/2021, 9:09 AM

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.

Cameras: Sony FDR-AX100E; GoPro Hero 11 Black Creator Edition

Installed: Vegas Pro 16, 17, 18, 19, 20 & 21, HitFilm Pro 2021.3, DaVinci Resolve Studio 18.5, BCC 2023.5, Mocha Pro 2023, Ignite Pro, NBFX TotalFX 7, Neat NR, DVD Architect 6.0, MAGIX Travel Maps, Sound Forge Pro 16, SpectraLayers Pro 11, iZotope RX10 Advanced and many other iZ plugins, Vegasaur 4.0

Windows 11

Dell Alienware Aurora 11

10th Gen Intel i9 10900KF - 10 cores (20 threads) - 3.7 to 5.3 GHz

NVIDIA GeForce RTX 2080 SUPER 8GB GDDR6 - liquid cooled

64GB RAM - Dual Channel HyperX FURY DDR4 XMP at 3200MHz

C drive: 2TB Samsung 990 PCIe 4.0 NVMe M.2 PCIe SSD

D: drive: 4TB Samsung 870 SATA SSD (used for media for editing current projects)

E: drive: 2TB Samsung 870 SATA SSD

F: drive: 6TB WD 7200 rpm Black HDD 3.5"

Dell Ultrasharp 32" 4K Color Calibrated Monitor

VEGASDerek wrote on 8/18/2021, 9:12 AM

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.

Phil_P wrote on 8/18/2021, 9:15 AM

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. :-)

Phil_P wrote on 8/18/2021, 9:17 AM

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.)

nothing wrote on 8/21/2022, 5:06 AM

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.

RogerS wrote on 8/21/2022, 6:11 AM

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

Custom PC (2022) Intel i5-13600K with UHD 770 iGPU with latest driver, MSI z690 Tomahawk motherboard, 64GB Corsair DDR5 5200 ram, NVIDIA 2080 Super (8GB) with latest studio driver, 2TB Hynix P41 SSD, Windows 11 Pro 64 bit

Dell XPS 15 laptop (2017) 32GB ram, NVIDIA 1050 (4GB) with latest studio driver, Intel i7-7700HQ with Intel 630 iGPU (latest available driver), dual internal SSD (1TB; 1TB), Windows 10 64 bit

VEGAS Pro 19.651
VEGAS Pro 20.411
VEGAS Pro 21.208

Try the
VEGAS 4K "sample project" benchmark: https://forms.gle/ypyrrbUghEiaf2aC7
VEGAS Pro 20 "Ad" benchmark: https://forms.gle/eErJTR87K2bbJc4Q7

Dexcon wrote on 8/21/2022, 6:24 AM

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.

Cameras: Sony FDR-AX100E; GoPro Hero 11 Black Creator Edition

Installed: Vegas Pro 16, 17, 18, 19, 20 & 21, HitFilm Pro 2021.3, DaVinci Resolve Studio 18.5, BCC 2023.5, Mocha Pro 2023, Ignite Pro, NBFX TotalFX 7, Neat NR, DVD Architect 6.0, MAGIX Travel Maps, Sound Forge Pro 16, SpectraLayers Pro 11, iZotope RX10 Advanced and many other iZ plugins, Vegasaur 4.0

Windows 11

Dell Alienware Aurora 11

10th Gen Intel i9 10900KF - 10 cores (20 threads) - 3.7 to 5.3 GHz

NVIDIA GeForce RTX 2080 SUPER 8GB GDDR6 - liquid cooled

64GB RAM - Dual Channel HyperX FURY DDR4 XMP at 3200MHz

C drive: 2TB Samsung 990 PCIe 4.0 NVMe M.2 PCIe SSD

D: drive: 4TB Samsung 870 SATA SSD (used for media for editing current projects)

E: drive: 2TB Samsung 870 SATA SSD

F: drive: 6TB WD 7200 rpm Black HDD 3.5"

Dell Ultrasharp 32" 4K Color Calibrated Monitor

Steve_Rhoden wrote on 8/21/2022, 7:57 AM

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

Per-Boysen wrote on 9/13/2023, 5:01 AM

@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 wrote on 9/14/2023, 6:54 PM

@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.

Phil_P wrote on 9/15/2023, 2:20 AM

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".

EricLNZ wrote on 9/15/2023, 4:08 AM

@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 wrote on 9/15/2023, 4:14 AM

@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.

NickHope wrote on 9/15/2023, 12:48 PM

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.

DMT3 wrote on 9/15/2023, 1:13 PM

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.

Phil_P wrote on 9/16/2023, 4:35 AM

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.

Phil_P wrote on 9/16/2023, 4:37 AM

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.

NickHope wrote on 9/16/2023, 2:38 PM
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

Phil_P wrote on 9/16/2023, 3:53 PM
 

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

Thanks Nick that's really useful, I'll be able to write a little application that can sift through this. :-)