This is for Cubase 13 Pro and it’s more of a curio to me than a real headache but just as a for-instance:
When I installed XStream a couple of days ago, I noticed that some files were listed as blocked by the VST Plugin Manager.
They caused no problem as such but for the sake of good order, I found where they were and deleted them. XStream still works fine, so all’s well.
However, I was wondering why this happens in the first place. Is it that the plugin installs files in more than one location and that not all are needed?
I hope that I’ve described it adequately. I’ve had it a couple of times with new installations of VSTs but there’s never been a problem caused by either the blocking or my subsequent deletion.
That’s the Microsoft Edge Webview that’s being blocked. Ignore it. Universal Audio unfortunately chose to use Webview to do the GUI for their UADx Native apps.
Steinberg also uses Webview for the left side of the hub that has web content.
A .dll is a “dynamically linked library” of functions. There is a chance that the SSL Meter is not supposed to be a plugin. It would then be used by the actual plugins to help them display meters.
If nobody here knows for sure what the file is you can ask the good folks from SSL.
Cubase will probably have had a reason to block this plugin. Maybe you have an older version, latest is 1.3.5. Sometimes the plugin is in a bundle with hardware, like UF1. Check if you can update.
No it’s all up to date. Latest Cubase 13 Pro and the SSL UF1 is brand new and firmware updated. I think it may be that they provide files for both VST2 and VST 3 maybe? Either way, it all works fine.
It’s in both, VST2 and VST3 format.
If you want to reset the VST2 (.dll) Blocklist, you can delete (or rename) the file %APPDATA%\Steinberg\Cubase 13_64\Vst2xPlugin Blacklist Cubase.xml. Cubase will then rescan for invalid files in the defined VST2 paths during the next start and build a new Blocklist - hopefully without SSL Meter.dll.
.