AR Chamber 'went into' WaveShell2-VST 10.0_x64.dll, plugins that I already owned that were upgraded (ie those still under WUP, including a couple only two or three months old) 'went into' WaveShell-VST 10.0_x64.dll, including some only a couple of months old as V9s. (I found this eventually became the case with V9, there were two WaveShell dlls being created.)Mathematics wrote:If you just bought it, like within the last couple of days and in my case, specifically AR Chambers, you'll end up with a new WaveShell2-VST 10.0_x64.dll file that you would have to copy to your custom VST folder. In Live, this will create a new folder group called something like WaveShell2-VST 10.0_x64.MogwaiBoy wrote:Advice please...
If you've got V9 and V10 working together perfectly, what happens when you buy a new plugin... just install as normal through Waves central, or is there the potential for something to break?
I don't know about Pro Tools though because it seems to just load up fine. It works fine in Performer...no issues.
If it's one of the older but updated plugins that you bought, say for instance...L2, I don't know. Perhaps same results? I'd like to know. Just know, that if it doesn't show up in Live, you may have a new Shell2 file to deal with.
Note : I dont use WaveShells directly, I create individual plugin stub .dlls with Shell2VST, which still works prefectly with V10.