@Skip_van_Rooij There were a number of problems outlined in this topic. Which specific problem are you referring to please?
Do you mean that Berlin Studio and Gemini BM7 plugins do not show up in Wavelab 12? If so, did you try using File / Plugins / General / Force Plug-in Detection at Next Launch? Also, do the plugins appear in the ‘Ignored Plug-ins’ list?
P.S. Generally speaking, a plugin working in Cubase is no guarantee that it will work in Wavelab - it just usually means that the plugins were tested in Cubase by the developers but were not tested in Wavelab. This does not necessarily mean that Wavelab is to blame - this is most often on the plugin developer side and a case of a poorly written plugin.
P.P.S. you might get a solution by contacting technical support but TBH IMO in the case of WL you are equally likely to get a solution by posting the full details here in this forum.
I reported the issue of Samplicity Berlin Studio working fine in Cubase but being blacklisted in Wavelab to the developer not long after it was released. He said he would investigate and I have just installed the latest version 1.3.1 and you will be glad to know that it now works! I too tried a trial of the Gemini B7 and that was blacklisted too but there is an updated version due soon so hopefully that will fix it.
Edit: I didn’t fully test it when I said this and unfortunately I’ve discovered that when rendering an audio file (24/48wav) I just get silence. A workaround is to insert about 3 minutes of silence before the audio file then everything is ok. I have reported this to Samplicity.
Plugins VST3 64bit not working in WaveLab 12, but work in Cubase 13. I don’t understand why WaveLab 12 flags VST3 64bit plugins as not compatible 64bit when the same plugs VST3 64bit are compatible with Cubase 13. WaveLab recorded 1402 VST3 64bit plugins, only few of them are working inside WaveLab. I don’t understand how that is possible?
Hi, thanks for your your response
My station is a MacPro 2019/Ventura. My plugin list is quite exhaustive, But I would say some of Plugin-Alliance, Some Sonnox, sone UAD… So far that what I managed to discover
Thank you for the tip. I am afraid I tried that already without success. And I am fully aware that virtual instruments won’t work. 2 exemples: VST3 Shadow Hills Mastering doesn’t show up, but the VST one does; same for Sonnox Inflator, …other VST3 Sonnox are visible. Inside the settings>plugging I can see that they are installed and recognised as VST3 64 bit, but I can’t use them.
Thank you all for your post, and at least you guys tried to give me some answers where Steinberg boot me out.
In response to the previous post, I needed the Class A from Plugin Alliance for the M/S option.
My point is
-Steinberg support told me that they don’t do support for WaveLab, and pushed me to the Forum for my queries.
-There I discovered that 1 year ago someone had the same issue, and so far there is no reason, no explanation, no solution.
-WaveLab made updates since the original vs12, but didn’t fix this issue. Why?
I am grateful for all your answers, but I wish that the WaveLab developer, who monitors this forum (this is what Steinberg support told me), takes action and fix the issues. This is not the only issue I have with my WaveLab 12 app . I have to force quite regularly, the windows show glitches randomly.
And if you guys have encountered those kind of issues and have an idea how to solve them, that would be wonderful, and I would be happy to learn. I don’t want to spread bad things, I just don’t know what to do for all those troubles. Thank you
AFAIK, Steinberg has not received any information from PluginAlliance pointing to a bug in WaveLab that would prevent their plugin from working. Of course, Steinberg does not test all the plugins in the world. Plugin manufacturers have to do their share.
In the image i posted you can see the “Class A” version is also active in the rack, on the top right.
I opted for the image of the “non-class A” because on your original post you didn’t mention the version.
But in fact they both work. At least on my system.
Maybe they both work in Steinberg’s test computers too.
Every system has slight incongruencies that can be caused by “millions” of small variations due to other software, usage, previous errors and so on.
Anyway, the PA compressor you mentioned works perfectly well with WabeLab 12… in my system.
Hi, thank you Paulo for your response, I didn’t pay enough attention at the image you shared, good for you if everything works.
Yes, all my plugs are updated, perhaps I should reinstall them again… Which I did with all my Plugin-Alliance plugs unsuccessfully.
About PG 1 post, I said in my first post that most of the VST3 64 bit work in Cubase 13, and not in WaveLab 12. I am not expecting that W.Lab should test all the plugs in that planet that doesn’t make sense to me. I was surprised and frustrated that WaveLab, inside the Settings>Plugins was able to see all my VST3, even I managed to select the Dyn option, but were not available inside Plugs insert. This was my starting point about thinking about an issue with WL. I took the Shadow Hills Class A as an example, to be honest I installed the VST2 for my job and it works well.
So to warp up, I wish Steinberg could provide support because those glitches are probably personal and not a general WaveLab issue. But because the Support leaded me to the forum, it creates a kind international issue, which is certainly not. And I am sorry for that.
Apparently there is a no magic solution, so I will deal myself with all my frustrations with WaveLab.
Thank you all for your support, this is the fist time that I dare exposed my issue inside a forum, this is really nice. Thank you
FYI, this option has nothing to see with plugin detection. It is mainly used for hardware-based plugins such as UID to better handle memory resources. It should better not use otherwise.
The only thing i can suggest now is that you try to use WL as an Administrator.
Remove the “PluginSettings.dat” from
C:\Users[YourUserName]\AppData\Roaming\Steinberg\WaveLab Pro 12\Preferences
…run WL as Administrator and let it rescan all your plugins and see if it works.
That is how i’m using WL and fortunately without any problems with my plugins.
Maybe i’m about to find one that doesn’t work but so far, i’m happy.
Hello
Thank you guys for all your support.
I finally decided to reset one more time the plugins Prefs. Rather than hit again the button “Force Plug-in Detection at Next Launch” I followed the advice from Justin Perkins which is trash the “plugin-registry.txt” file, as I am a macOS user. For those who could be interested the record path is:
Users>User>Library>Preferences>WaveLab Pro 12>Cache>plugin-registry.txt
This time it worked out well, the VST3 plugs are now reachable.
Thank you agin all of you, that was very useful for me.
My best, jf m
