I am in the process of moving Unify STD v1.11.4 from a Windows 11 Home Version 24H2 computer to a new system running Windows 11 Pro Version 24H2.
I have been unsuccessful in being able to install the Waze Electric200 Stereo VST3 Plug-in, which I must point out, loaded without problems on the old Windows 11 Home computer but refuses to load into Unify on the Windows 11 Pro machine.
Furthermore, which is very baffling to me, is that the Standalone version of the plug-in and my Cakewalk By Bandlab DAW can run the Waze Electric200 Stereo VST3 plug-in on the Windows 11 Pro computer without any problems.
I have also tried manually loading the plug-in by using "Select plug-in file(s) to scan..." to no avail so any help from Forum Members would be greatly appreciated as I really would like to be able to continue enjoying and using this plug-in within the great Unify application.
I think you mean "Waves" not "Waze".
Waves puts all their plug-ins into a common "container" which will be called something like WaveShell1-VST3 15.0_x64.vst3. Drag/drop that into Unify's known plug-ins list to add ALL your Waves plug-ins. You may end up with more in the list than you want (perhaps including plug-ins that you don't have licenses for), in which case you can just click the "Manufacturer" column heading to sort by vendor name, scroll down to the Waves plug-ins, and select and remove any extras you don't want. Note you can Ctrl-click multiple plug-ins, then click the Operations button and choose "Remove selected plug-in(s) from list) to remove several at a time.
@getdunne Sorry, about my spelling of "Waves" and thank you for your quick response which I already saw posted in another thread and tried to Drag/drop it into Unify's known plug-ins list on my Windows 11 Pro computer but for some reason it did not include the Electric200 Stereo VST3 plug-in after everything had downloaded.
Is there any way that I could move Unify's Known Plug-ins list from my Windows 11 Home computer which does have the Electric200 Stereo VST3 plug-in loaded and showing in Unify's Known Plug-ins List to Unify's version which is successfully installed on my new Windows 11 Pro machine?
I don't think moving the list from another machine will work for Waves plug-ins, because of the very peculiar way they package them.
As I said, those large "shell" VST3 files that Waves uses actually contain all their plug-ins, so they have some hidden mechanism to figure out which ones you've paid for, so you see only those when you scan. I think you have to use their Waves Central app to download, install, and license each plug-in before scanning the shell VST3 will actually find it. However, you said that the specific plug-in is already loading in your DAW, so you probably already did that.
Another aspect is that Waves periodically revises all their plug-ins into new versions, and you may find that your machine has more than one "WaveShell..." VST3, and you may need to scan them all. I'd suggest starting with the latest one (v.15), then successively lower versions as needed, until all of the plug-ins you want are available.
On my PC, I have multiple v.14 WaveShell-VST-...dll files in C:\Program Files\Vstplugins (these are older VST2 plug-ins), but in C:\Program Files\Common Files\VST3 I have several v.14 WaveShell-VST3-...vst3 files and just one v.15 file called WaveShell1-VST3 15.0_x64.vst3. If you've used Waves plug-ins for any length of time, you probably have a similar situation. If you scanned only those *.dll files, you'd only get older plug-ins which Waves provided in VST2 format. I believe they switched to VST3-only at v.11 or so, so you must scan the VST3 shell file(s) to see the newer VST3-only plug-ins.
I know the whole VST2 vs. VST3 thing is confusing (especially when DAWs like Cubase insist on calling them both "VST", even though they are completely different and incompatible formats), but it's something we're all stuck with. I'd advise using only the VST3 versions of all your Waves plug-ins when you can, BUT if you have created your own patches using VST (i.e., VST2) versions in the past, you'll need to also scan in the VST2 versions to ensure those patches open correctly.
Thanks again for your quick response and since I had several WaveShell1&2 VST3 15.0_x64.vst3 installed on my Windows 11 Pro computer as per your terrific suggestion I just opened them all which finally resulted in the Electric200 Stereo showing up in Unify's Known Plug-ins List.
i can't thank you enough for helping me to get this working once again within Unify and also for your previous detailed response to my other thread of how to move Unify from one Windows 11 computer to another.
If only other plug-in manufactures would take a lesson from you and Skippy as to what it actually means to provide exceptional customer support and service, they might just get an understanding of what has transformed Unify into such an outstanding product!!!
