VST Constant Loop Scan - Why? When will this be fixed?

Every 1-2 minutes VST plugins scan starts - please fix it at last.

It's not necessarily something for BMD to fix as I have never had this with my system or plug-ins, and have used Resolve since version 14. Are your plug-ins the up to date versions without a mix of older and newer versions? For instance if I have a VST 3 plug-in I don't have the VST 2.4 installed as well.

It's not necessarily something for BMD to fix

Yes it is. It started happening in 17.4 seemingly connected to the introduction of VST3 support. And it doesn't happen with any other DAW.

I suspect that Resolve is incorrectly handling plugins that exist in both VST2.4 and VST3 formats and have the same name in each. There's no reason why it shouldn't be able to support these both co-existing, like other DAWs do, eg Reaper:


Plugins existing in multiple formats has worked fine for years in Resolve on macOS with AU + VST2.4 plugins. It's only the addition of VST3 support that has introduced this new problem.

It's just a bug, I'm sure they'll fix it before long.

I have this problem since many versions.

Another problem I have is that I can't disable any VST plugin, once i disable a VST the message box appears: "Changes will take effect the next time Resolve is started." After restart the VST I disabled is enabled.

Oh, interesting. So maybe it was a problem that was always there, but became much worse / noticeable to a lot more people with the addition of VST3 plugins.

I found a way to fix it on my Windows system, I changed the region format from Greek to English (United States).

On the first launch after changing the setting, it did a VST rescan but afterwards there is no more VST rescan at startup and I can disable any VST plugin without problems now.

Region.png (7.65 KiB) Viewed 1736 times

There was a similar problem with black grades caused by region settings when the first V17 beta came out
viewtopic.php?f=21&t=125515

I believe that this is a BMD problem - as on the version before 17.4 there was no such bug on my system, with the DR update it appeared and really interferes with the work. I have many other programs that support VST plugins, but none of them behave this way - the same Adobe scans the plugins once after updating and does not waste time on scanning on subsequent launches.
DR scans the VST regularly while running - Why is he doing this while running? Obviously, no one installs or deinstalls plugins every 2-3 minutes, especially during work.
Plugins must be scanned once and that's it!

I found a way to fix it on my Windows system, I changed the region format from Greek to English (United States).

Interesting, I also found that the scripting API reports incorrect frame rates on Windows in some cases when the region isn't set to English (United States). Seems to be weak spot in Resolve.

It's not necessarily something for BMD to fix as I have never had this with my system or plug-ins, and have used Resolve since version 14.

Yea, it's a thing that started with 17.4.1 -- It'll rescan my VST's at every startup.

Note: All plugins are up to date, no 32 bit vst's installed, I always uninstall Resolve before installing new DR version, and all VST's work in other DAWS & NLE's.

Does the Available Plugins list in Preferences/System/Audio Plugins show all your plugins as Loaded Successfully?

I tried the same test inside a virtual machine with a clean windows installation with the same results.

Here is a gif for proof, with English (United states) as the region format there is no VST rescan at startup, the problem appears once I switch to greek.
(just ignore the unsupported GPU messages, they appear because I'm running from a virtual machine)

Does the Available Plugins list in Preferences/System/Audio Plugins show all your plugins as Loaded Successfully?

Yes, they are all loaded - Even when I uncheck all of them and restart, it will still rescan...

I tried the same test inside a virtual machine with a clean windows installation with the same results.

Here is a gif for proof, with English (United states) as the region format there is no VST rescan at startup, the problem appears once I switch to greek.
(just ignore the unsupported GPU messages, they appear because I'm running from a virtual machine)

I have United States as my region (it's always been that way) however, it will still rescan regardless of region setting on my system.

Guess we'll have to wait until the next update for a fix.

I'm having the same issue with VST2/VST3 plugins being scanned, rescanned, listed one time, unlisted next time and constantly changing states of "enabled".

PS: region setting is germany

v17.4.2 resolves the issues on my system.

Yup, the latest update 17.4.2 fixes the VST scan at every startup.

Sending many thanks to the devs for the fix!

-Cheers

Another big thanks from my side. It drove me crazy having to move plug-ins in and out.

I'm on 17.4.2 and it's still doing it on my system.

Shaheed, check that the build number of your version 17.4.2 is 9 not 8. If it is 8 re-download and re-install 17.4.2.