VST Scan Running Forever

Author
SpaceElation
Max Output Level: -90 dBFS
  • Total Posts : 11
  • Joined: 2014/12/26 22:48:50
  • Status: offline
2016/02/13 02:41:56 (permalink)

VST Scan Running Forever

Hi
 I have about 200+ VST plugin Instruments and about the same with FX VSTs. My computer is a 64/32 bit OS win7. My problem is it takes sometimes up to 2 hours to scan all the VST folders on the PC. When I do a install the plugin will install both the 64 and 32 bit versions. 64bit has 3 different vst folders/ 32 bit has the same, then there's vst folders under Common Files, Program Data not to mention the VST3 folders locations. It's got crazy!
Question : Is there a way to scan just certain folders? After I install a new VST instrument I know where it was installed. Is there a way I can direct the scan to a certain folder(s) and bypass the rest? Is there hope!  
#1

10 Replies Related Threads

    mettelus
    Max Output Level: -22 dBFS
    • Total Posts : 5321
    • Joined: 2005/08/05 03:19:25
    • Location: Maryland, USA
    • Status: offline
    Re: VST Scan Running Forever 2016/02/13 03:20:12 (permalink)
    If you go to Edit->Preferences, in "File->VST Settings" on the left, you will get "VST Scan Paths" at the top where you can add/remove paths. For 64-bit SONAR, I have removed the 32-bit scan paths (C:\Program Files (x86)\Cakewalk\Vstplugins) although I do have the 32-bit plugins installed.
     
    Also on that page, I have Scan Options set to "Manual Scan" and checked "Rescan Failed Plugins." I only run the scan after I know I have installed/removed a VST, rather than leave it automatic or on startup.
     
    2 hours is incredibly excessive. Which version of SONAR are you running?
     
    FWIW, I only have the following two paths in my 64-bit VST Settings:
    C:\Program Files\Cakewalk\Vstplugins
    C:\Program Files\Common Files\VST3
    but am also religious about installing to only those two directories.

    ASUS ROG Maximus X Hero (Wi-Fi AC), i7-8700k, 16GB RAM, GTX-1070Ti, Win 10 Pro, Saffire PRO 24 DSP, A-300 PRO, plus numerous gadgets and gizmos that make or manipulate sound in some way.
    #2
    mudgel
    Max Output Level: 0 dBFS
    • Total Posts : 12010
    • Joined: 2004/08/13 00:56:05
    • Location: Linton Victoria (Near Ballarat)
    • Status: offline
    Re: VST Scan Running Forever 2016/02/13 08:52:06 (permalink)
    Is it possible you have an error window open behind the Sonar main screen that is preventing the scanner from finishing?

    Mike V. (MUDGEL)

    STUDIO: Win 10 Pro x64, SPlat & CbB x64,
    PC: ASUS Z370-A, INTEL i7 8700k, 32GIG DDR4 2400, OC 4.7Ghz.
    Storage: 7 TB SATA III, 750GiG SSD & Samsung 500 Gig 960 EVO NVMe M.2.
    Monitors: Adam A7X, JBL 10” Sub.
    Audio I/O & DSP Server: DIGIGRID IOS & IOX.
    Screen: Raven MTi + 43" HD 4K TV Monitor.
    Keyboard Controller: Native Instruments Komplete Kontrol S88.
    #3
    Anderton
    Max Output Level: 0 dBFS
    • Total Posts : 14070
    • Joined: 2003/11/06 14:02:03
    • Status: offline
    Re: VST Scan Running Forever 2016/02/13 09:12:33 (permalink)
    Look in the taskbar to check for what Mudgel references. I have a couple thousand plug-ins, and to scan all of them takes a minute or two.

    The first 3 books in "The Musician's Guide to Home Recording" series are available from Hal Leonard and http://www.reverb.com. Listen to my music on http://www.YouTube.com/thecraiganderton, and visit http://www.craiganderton.com. Thanks!
    #4
    John T
    Max Output Level: -7.5 dBFS
    • Total Posts : 6783
    • Joined: 2006/06/12 10:24:39
    • Status: offline
    Re: VST Scan Running Forever 2016/02/13 09:16:43 (permalink)
    Also, which update are you on? There was a bug a couple of updates back that could cause this, but has since been fixed.

    http://johntatlockaudio.com/
    Self-build PC // 16GB RAM // i7 3770k @ 3.5 Ghz // Nofan 0dB cooler // ASUS P8-Z77 V Pro motherboard // Intel x-25m SSD System Drive // Seagate RAID Array Audio Drive // Windows 10 64 bit // Sonar Platinum (64 bit) // Sonar VS-700 // M-Audio Keystation Pro 88 // KRK RP-6 Monitors // and a bunch of other stuff
    #5
    scook
    Forum Host
    • Total Posts : 24146
    • Joined: 2005/07/27 13:43:57
    • Location: TX
    • Status: offline
    Re: VST Scan Running Forever 2016/02/13 09:38:51 (permalink)
    SONAR recursively scans all the folders in the scan path every time. It might be helpful if you publish your scan path from Preferences > File > VST Settings
     
    As mentioned above consider eliminating 32 paths while running 64bit SONAR. If there are a few 32bit plug-ins needed for 64bit SONAR move them to a separate path so it is possible to remove the bulk of the redundant plug-ins.
     
    Still 200+ plug-ins is not that many and should not take minutes to scan.
    #6
    robert_e_bone
    Moderator
    • Total Posts : 8968
    • Joined: 2007/12/26 22:09:28
    • Location: Palatine, IL
    • Status: offline
    Re: VST Scan Running Forever 2016/02/13 12:58:39 (permalink)
    Yup - I have around 900, and it takes next to no time at all when I launch Sonar.
     
    I too only have 64-bit 3rd-party plugins available in any of the paths in the VST search paths in Preferences, and only point to the 64-bit Cakewalk plugins and the VST3 path.  I direct all installs to use the 64-bit Cakewalk plugins folder, and do not install any 32-bit plugins anymore whenever possible (some installs just put them out there with no way to discourage them from doing so, but no 32-bit plugin paths are referenced by my 64-bit Sonars).
     
    Bob Bone
     

    Wisdom is a giant accumulation of "DOH!"
     
    Sonar: Platinum (x64), X3 (x64) 
    Audio Interfaces: AudioBox 1818VSL, Steinberg UR-22
    Computers: 1) i7-2600 k, 32 GB RAM, Windows 8.1 Pro x64 & 2) AMD A-10 7850 32 GB RAM Windows 10 Pro x64
    Soft Synths: NI Komplete 8 Ultimate, Arturia V Collection, many others
    MIDI Controllers: M-Audio Axiom Pro 61, Keystation 88es
    Settings: 24-Bit, Sample Rate 48k, ASIO Buffer Size 128, Total Round Trip Latency 9.7 ms  
    #7
    Leee
    Max Output Level: -75 dBFS
    • Total Posts : 783
    • Joined: 2004/12/21 11:31:00
    • Location: The Great NorthWest
    • Status: offline
    Re: VST Scan Running Forever 2016/02/14 13:44:57 (permalink)
    As mudgel commented, the only time my VST plugin scan stalls is when there is a problem scanning one of the plugins, in which case a pop-up window will open (but will be hidden behind the other windows).  If I minimize the main Sonar window, I can then see the pop-up window, and either click on OK or close it.   Then the scan continues.
    I also have many plugins, but after the first initial scan, any future scans go very quickly.

    Lee Shapiro
    www.soundclick.com/leeshapiro
     
    Welcome BandLab and thank you for giving Cakewalk and Sonar a new lease on life.
    #8
    SpaceElation
    Max Output Level: -90 dBFS
    • Total Posts : 11
    • Joined: 2014/12/26 22:48:50
    • Status: offline
    Re: VST Scan Running Forever 2016/02/16 00:40:41 (permalink)
    Thanks for all the input I'm going to try scanning Failed Plugins and see if that works
    #9
    bobbyswamp
    Max Output Level: -89 dBFS
    • Total Posts : 65
    • Joined: 2010/12/23 00:06:41
    • Location: Los Angeles, CA
    • Status: offline
    Re: VST Scan Running Forever 2016/02/16 00:53:04 (permalink)
    Very informative thread, I was having a similar issue with lengthy scanning, like SpaceE. But it wasn't 2-hours! Anyways, I'm gonna manually change the path of the scan, too. Thanks for the info...
     
    post edited by bobbyswamp - 2016/02/16 01:07:30

    https://www.reverbnation.com/thegalaxies
     
    Sonar Platinum, Cakewalk by BandLab, Windows 10
    #10
    slincoln
    Max Output Level: -90 dBFS
    • Total Posts : 37
    • Joined: 2014/12/20 12:26:36
    • Location: Minneapolis, MN
    • Status: offline
    Re: VST Scan Running Forever 2016/02/17 01:49:52 (permalink)
    I have had issues with the plugin scan taking forever. For me, it turns out that where the scan hangs, is the plugin which is causing the problem. I had to reinstall the plugin and select "reset" in the scan options. That fixed the problem for me.
     
    I did discovered that MixBus 3.1 is the actual problem. When it locks up, it seems to corrupt plugins. Therefore, the next time I open up Sonar it has issues scanning plugins. Now, I'm back to treating my stems files in MixBus and not mixing.
    #11
    Jump to:
    © 2025 APG vNext Commercial Version 5.1