Jump to content
Multi-Sonik

Waves V9 scan problem

Recommended Posts

Hello to you, brand new FORUM! 

I'm using Waves V9 (Latest V9) with both Platinum and Bandlab versions of Sonar. (Win10 1803, latests BandLab and Platinum builds)

Yet I have a big problem scanning my VST. The scan hangs up while attempting to scan the MONO version of the STUDIORACK plugin. I think this is preventing me to register my DIAMOND bundle. (none of the plugins are avail as of now to my DAW)

UPDATE: Scan went through and StudioRacks got registered, but still no DIAMONDS plugin bundle detected...

The WavesShell V9 seems indeed to be scanned by Sonar, but the plugins are not loading... I do not know if I'm overdoing it with my folders, though... see capture)

 

Anybody encountred this problem? How can I at least scan all of my plugins and deal with the StudioRack ones later?

Thanks

VstScan.PNG

Edited by Multi-Sonik
screenCapture

Share this post


Link to post
Share on other sites

As long as your plugin support it still active, By ALL MEANS update to  v10 with the Waves Central installer app. Believe me it's well worth the few dollars a year to keep up to date.

 You will always have the latest version, added functionality and more presets, and best support available

Log into Waves account and call or email for support. Allow them remote access, and they will fix it for you within minutes.

If your plugin support is expired, you will need to uninstall and reinstall your Waves plugins manually with Waves Central.

You may also need to move the license of the offending plugin from local (system) to the cloud for Cakewalk/SONAR to complete VST scanning.

Believe me it's well worth the few dollars a year to keep support and everything up to date.

Edited by Steev

Share this post


Link to post
Share on other sites

If you are referring to the FREE studio pack offer and you have any v 10 Waves plugins installed, DO NOT TRY TO INSTALL STUDIOPACK LICENSE TO YOUR SYSTEM.

Save your self the trouble of contacting support, it's not going to work.

And THAT'S why it's free.

Share this post


Link to post
Share on other sites

Thanks for your replies, Steev!

But I just had a DOH! moment here.

Seems like the Diamonds plugins are installed but are NOT showing in Sonar's media browser. These are only avail from within the StudioRack plugin.

Logical, in a way, but I am kind of surprised by this (not having the Diamond bundle avail as "native" to Sonar's media browser). Makes me wonder how to collaborate with a colleague that has a couple of waves plugin but is not SG ready yet... To investigate...

Share this post


Link to post
Share on other sites

 I've always found a good work around for collaboration is to record one dry track and record a 100% wet mix of any FX plugin used to an aux. track right next to it and let the fellow collaborator mix/balance it  to the dry track. a.k.a. parallel processing.

 Seldom to NEVER will 2 different computers handle plugins the same way whether you have the same DAW and plugin software installing them in different folders in "Program Files."

 Waves have also recently changed folder locations and shells, you will need to update Waves Central and reinstall everything and you cannot run (years) older non updated v9 or below and v10 plugins at the same time.

 Bad times for anyone using cracked/keygen versions of Waves plugins, anything that isn't registered in a current Waves User Account will no longer run.

  With Sound Grid method you need to install your licensed plugins on a portable/external USB or eSATA drive, and then you can use the plugins on another computer or digital mixer that supports SG..

   For use With SONAR you will need to plug the USB drive with the plugins installed on it and run a VST scan. This doesn't install the plugins on the computer, Sonar or CbB will simply run the plugins off the USB drive.

 You would still have to mix down and save the effected tracks because once you remove the external USB or eSATA drive the plugins used will no longer be found by the plugin manager or inserted to a channel or in the FX bin.

Edited by Steev

Share this post


Link to post
Share on other sites

I am also having problems with Waves plugs in CBB. In my case with the latest V10 version and I have to reset all parameters on the Cakewalk plug-in manager to get all plugins properly working every time I install a new plugin. That is really annoying and I haven't received any response from Waves Support. On the other hand, the Bandlab support team told me that they will investigate the issue.

Edited by Alex H.

Share this post


Link to post
Share on other sites

Are you using Waves' StudioRack plugins as well? When Sonar scans the stereo and mono version does it take forever for you? on V9 here it is really long but usually it goes through. I'm wondering because on my end I am not encountering the problem you're talking about on my V9. I'm juste trying to see if some of these behaviors can be found on both V9 and V10 versions.

Share this post


Link to post
Share on other sites
3 hours ago, Multi-Sonik said:

Hello to you, brand new FORUM! 

I'm using Waves V9 (Latest V9) with both Platinum and Bandlab versions of Sonar. (Win10 1803, latests BandLab and Platinum builds)

Yet I have a big problem scanning my VST. The scan hangs up while attempting to scan the MONO version of the STUDIORACK plugin. I think this is preventing me to register my DIAMOND bundle. (none of the plugins are avail as of now to my DAW)

UPDATE: Scan went through and StudioRacks got registered, but still no DIAMONDS plugin bundle detected...

The WavesShell V9 seems indeed to be scanned by Sonar, but the plugins are not loading... I do not know if I'm overdoing it with my folders, though... see capture)

 

Anybody encountred this problem? How can I at least scan all of my plugins and deal with the StudioRack ones later?

Thanks

VstScan.PNG

I just noticed something very wrong with this picture.. You need to "add"  c:\program files\VST plugins   to your VST scan path or SONAR CbB won't know where to look for any x64 Waves plugins shell

Program files.jpg

Edited by Steev

Share this post


Link to post
Share on other sites

Waves Studio Rack does not contain any plugins until you assign them to a location in the rack. look at it as a way to organize your most commonly used FX and placing them at the top of the rack for easy access, exactly like you would building a 19" hardware rack placed right next to your mixing console for easy hands on access. It makes them easier to get to than searching through a Waves folder that lists every plugin in alphabetical order..

 By installing Studio Rack, ALL your Waves plugins should be now located there, whether you install them in the front end of rack itself or not, Studio Rack is the only place you should ever have to look for them ever again.

 

 Waves bundles like Diamond and Mercury, etc are a great way to save money purchasing multiple plugins at once. Through the years the included bundle of plugins packages change. Some get dropped, others get added, and as long as you continue to pay for update support everything gets updated and improved to the current latest release version.

 If your update support expires your plugins will continue to work, but won't be updated to the latest version # which is now v10.

 So if you are running v9.0 or 9.2 plugins you are still entitled to update to the latest v9.7 version but won't be allowed to update further to v10 until you renew your update license plan for the particular plugin you can't live without.

 v10 gives you updates with stuff like  VST2 to VST3, ARA support which greatly improves performance using plugins in real-time for ultra low latency with SONAR/CbB input monitoring.

 

 There is no need to run Sound Grid unless you are running Waves Plugins from an external device. USB stick, eSATA drive, or the all power Waves Sound Grid stand alone Server unit, which is great and freak'in AWESOME, but costs around $2000 (us)

 That usually averages about $10 per year per plugin if you keep up. Renewing every plugin in the Diamond bundle is not recommended, and that can be VERY pricy and can easily reach in excess of $100 per year to maintain FX that you will never use.

Keep in mind that there is no such thing as collectable vintage plugins. Any plugin on your system that is too old to be fully supported by you current DAW and OS is a waist of hard drive space and merely "Bloatware" filling up "Windows Registry" with 100's to 1000's of broken dead end paths your DAW needs to search though that end up going nowhere.

 I for one believe this to be the #1 cause of poor system and DAW performance that will eventually lead to certain premature death of a computer/workstation if neglected for too long.

  The more plugins you have installed the longer the VST scan will take, so if you have 300 plugins installed that you will most likely never use, you can greatly increase project load times and over all system performance of your DAW by uninstalling them.

 And then run a Registry cleaning utility for the true OMG?? My computer runs like new again experience..😍

Edited by Steev

Share this post


Link to post
Share on other sites

Well.. another update, now for no obvious reason all my waves plugins are now showing up in Sonar's browser... I'll obviously have to find which folder I am scanning that are causing theses duplicates... But at least I can see and use them.

 

VstScan2.PNG

Share this post


Link to post
Share on other sites

By the way Steev, I bought the Impact server about a year ago... but have not yet completed the setup for various reasons. I'm getting back to it now, hence my posts...

 

Share this post


Link to post
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now

×
×
  • Create New...