Scan VST Plugins

Author
CBJ
Max Output Level: -89 dBFS
  • Total Posts : 54
  • Joined: 2007/03/12 22:07:23
  • Status: offline
2016/04/19 15:18:17 (permalink)

Scan VST Plugins

Greetings Fellow Sonar-ites! Or is that Sonar-ers, SonarMates, or Sonarians? OK, still not working for Ya? How about Sour Sonarites? Yikes Soooorrrry!
 
Well at least I got a chuckle if not a small smile out of you for the day! That's a good thing with what is going on in this world today, count our blessings and enjoy our freedom!
 
I have run into a situation that I can't seem to find any reference to on the forum so I've decided to post this in hopes that someone can point me to a simple solution that I have overlooked. It has happened in the past & I have simply deleted the offending plugins to circumvent the issue.
 
Here's the scenario. I've installed an izotope multi effects plugin & went about scanning the newly added plugin to register the effect & during the scanning process the scan hung up on another previously installed Line 6 product called Helix. The scan was interrupted by a .dll called " opengl32sw.dll " & would not move past this item. The scan was hung up for roughly 30 minutes & NO ERROR MESSAGE or IGNORE option was available so I cancelled the scan. Nothing in the help file covered this problem so the only option was to unload the current Helix software & drivers then reinstall the Helix to an entirely different location so it was no longer in the scan list.
 
I deliberately created ( C:\Audio ) & use this folder on my boot drive called Audio where I install all my studio related software, such as Sonar, all the associated hardware & software drivers, manuals, videos, & any other things that relate or pertain to the recording studio. The only thing that I don't store on the boot drive is the recording data ( WAVE FILES ) & Virtual Instrument audio samples which are stored on two very large external hard drives via Esata.
 
Since the Line 6 Helix was installed in a sub folder within a folder called Audio (where I store other plug ins) it was automatically included in the scan. Sonar does not allow an exclusion list however, I think it should be considered in the next release & here's why.
 
As previously mentioned my current boot hard drive layout consists of a dedicated folder called Audio where I store everything AUDIO! I try to put things away where I think they belong rather than allowing Windows to take control & put things away where the programmers have determined it belongs. I'm sure that a lot of us have experienced the frustration of trying to find a file on our hard drive &  considering the physical size of the current hard drives this is getting harder every day.
 
So here's a sample of what I do before I put things away with my current file structure
 
C:\Audio\
C:\Audio\Amps\
C:\Audio\Hardware\2 Box
C:\Audio\Hardware\Helix
C:\Audio\Hardware\Integra i7
C:\Audio\Hardware\Midas
C:\Audio\Hardware\Presonus
C:\Audio\Software\
C:\Audio\Utilities\
C:\Audio\Virtual Instruments\
C:\Audio\Effects\
C:\Audio\Effects\EQ\
C:\Audio\Effects\Dynamics
C:\Audio\Effects\Reverb\
C:\Audio\Effects\Reverb\Lexicon
C:\Audio\Effects\Reverb\Perfect Space
C:\Audio\Effects\Reverb\Oxford
 
On the surface this all looks quite simple & one would say just create the list above & ignore the  C:\Audio\Hardware\ & your problem is solved but these sub folders are layers deep so it's not as easy as it seems. If Sonar was to offer an option to exclude selected items it would go a long way in helping this out.
 
In Sound Forge alone there are hundreds of ( useless ) plugins (well OK, maybe I'm exaggerating but there's lots) that get registered not to say other plugins that Windows scatters all over folders such as C:\Programs or C:\Programs (x86). Other vendors (even Sonar) put their drivers in regardless of where the user has specified the contents of the installed software should go. Even after I specified that Sonar is to install the contents of Melodyne & Dimension Pro, I find .dlls & other files installed in folders within C:\Programs or C:\Programs (x86). It's frustrating when you are trying to run a tidy operation in order to save time.
 
Perhaps this is not a big enough problem to warrant a nod but I think it would make things more efficient. Even if the Cakewalk code Gods decide to add additional options to the hang up window that appears ( caused by whatever is causing it ) would allow us PEONS to select (from a dropdown list) mark as (in the future do not load ), ignore or any other logical choice would go a long ways of making me press Ctrl, Alt, Del to cancel Sonar & reload it to start all over for the 10th time. Having a list of items ignored would help as well in case the user made the wrong choice and now can't change it since it no longer comes up during the scan procedure.
 
Anyway, that's all I got say about that! Cheers guys!
Have a wonderful day! It's the only one you get, so make the most of it!
#1

1 Reply Related Threads

    scook
    Forum Host
    • Total Posts : 24146
    • Joined: 2005/07/27 13:43:57
    • Location: TX
    • Status: offline
    Re: Scan VST Plugins 2016/04/19 15:28:36 (permalink)
    SONAR does not have an exclude list. Instead SONAR works with an include list. Only folders containing VST2/3 plug-ins should be in Preferences > File > VST Settings. These folders will be recursively scanned for .dll and .vst3 files. There is no point in adding SoundForge plug-ins to the scan path, they are not VST format.
    #2
    Jump to:
    © 2025 APG vNext Commercial Version 5.1