Scan VST folders on Sonar Startup

Author
TraceyStudios
Max Output Level: -78 dBFS
  • Total Posts : 603
  • Joined: 2005/10/13 12:40:33
  • Location: Chandler, AZ
  • Status: offline
2013/05/02 17:52:52 (permalink)

Scan VST folders on Sonar Startup

Is it neccesary to scan the vst folders everytime Sonar loads? It takes 2-3 minutes to load this way. I have diasbled this and now it only takes a few seconds to load. I would assume I need to rescan if I add any new vst's. What is the recomended scan setting?

AMD FX-6100 six-core processor 3.3GHz
8 Gig RAM
SONAR X3 Producer
Tascam FW1884
Mackie Blackbird
Presonus Digimax
Avalon U5
BFD2
SL Trigger
Alesis DM8 Pro drums
KRK Rokit 8s
KRK 10s
ARC2

Folgers Dark Roast, a bit of crazy :)
& lots of help from the forums!
 
http://www.reverbnation.com/blakkmire
#1

16 Replies Related Threads

    John
    Forum Host
    • Total Posts : 30467
    • Joined: 2003/11/06 11:53:17
    • Status: offline
    Re:Scan VST folders on Sonar Startup 2013/05/02 18:09:28 (permalink)
    It should not take any time at all. Noel posted about this awhile back and advised us to implement it. He had fixed the slow scan and optimized if there were no new plugins to scan. I tried it and it is just as he said. 

    As to your question no there is no reason to scan if no new plugins are installed.

    Best
    John
    #2
    scook
    Forum Host
    • Total Posts : 24146
    • Joined: 2005/07/27 13:43:57
    • Location: TX
    • Status: offline
    Re:Scan VST folders on Sonar Startup 2013/05/02 18:22:32 (permalink)
    Make sure that "Re-scan failed Plug-ins" and "Re-scan existing Plug-ins" are not checked. The scan on startup should not take any time at all, if there are no new plugins. If you continue to experience excessive scan times, you are not going to harm anything by turning it off. Just remember to scan when you add new plug-ins.
    #3
    jb101
    Max Output Level: -46 dBFS
    • Total Posts : 2946
    • Joined: 2011/12/04 05:26:10
    • Status: offline
    Re:Scan VST folders on Sonar Startup 2013/05/02 18:25:55 (permalink)
    John


    It should not take any time at all. Noel posted about this awhile back and advised us to implement it. He had fixed the slow scan and optimized if there were no new plugins to scan. I tried it and it is just as he said. 

    As to your question no there is no reason to scan if no new plugins are installed.
    +1 to John's comments.
     
    This has come up a couple of times recently, but the scan should be near instantaneous.

     Sonar Platinum
    #4
    TraceyStudios
    Max Output Level: -78 dBFS
    • Total Posts : 603
    • Joined: 2005/10/13 12:40:33
    • Location: Chandler, AZ
    • Status: offline
    Re:Scan VST folders on Sonar Startup 2013/05/02 18:39:30 (permalink)
    thanks for the answer! this forum ROCKS!

    AMD FX-6100 six-core processor 3.3GHz
    8 Gig RAM
    SONAR X3 Producer
    Tascam FW1884
    Mackie Blackbird
    Presonus Digimax
    Avalon U5
    BFD2
    SL Trigger
    Alesis DM8 Pro drums
    KRK Rokit 8s
    KRK 10s
    ARC2

    Folgers Dark Roast, a bit of crazy :)
    & lots of help from the forums!
     
    http://www.reverbnation.com/blakkmire
    #5
    martinv
    Max Output Level: -88 dBFS
    • Total Posts : 138
    • Joined: 2012/07/28 02:25:07
    • Status: offline
    Re:Scan VST folders on Sonar Startup 2013/05/05 18:20:21 (permalink)
    Perfect timing on this topic.  I had the exact same issue and it is now solved.
    #6
    jimusic
    Max Output Level: -64 dBFS
    • Total Posts : 1325
    • Joined: 2008/05/21 18:59:52
    • Location: Near Vancouver, British Columbia, Canada
    • Status: offline
    Re:Scan VST folders on Sonar Startup 2013/05/06 01:07:45 (permalink)
    Yeah - I disable that after any new plugs, and in fact altogether now.

    My startup is really fast.

    If I install anything new now, I just run it from the Plugin Manager 'Scan Vsts' button opposite the 'Options' button. 
    Then I'm already in the same window to add that new plugin into what I call 'My Layout' instead of using the Default plugin one.

    Other than an older, slower computer, slow startups would be signs of troubles that would warrant looking into for sure - like unecessary background programs, etc.  





     
     
    #7
    Guitarhacker
    Max Output Level: 0 dBFS
    • Total Posts : 24398
    • Joined: 2007/12/07 12:51:18
    • Location: NC
    • Status: offline
    Re:Scan VST folders on Sonar Startup 2013/05/06 06:47:45 (permalink)
    You are correct.  there is no need to scan at startup every time. 

    Shut it off. 

    When you add a new VST with the plug in manager simply scan it at that time and you'll never need to do another scan at startup.



    My website & music: www.herbhartley.com

    MC4/5/6/X1e.c, on a Custom DAW   
    Focusrite Firewire Saffire Interface


    BMI/NSAI

    "Just as the blade chooses the warrior, so too, the song chooses the writer 
    #8
    Brandon Ryan [Roland]
    Max Output Level: -40.5 dBFS
    • Total Posts : 3458
    • Joined: 2003/11/06 03:29:12
    • Location: Los Angeles, CA
    • Status: offline
    Re:Scan VST folders on Sonar Startup 2013/05/07 02:07:52 (permalink)
    The best practice IMO  is to have "Scan on Startup" on and "re-scan" options turned off.

    I once wrote a blog about why here: http://blog.cakewalk.com/why-you-should-use-scan-vst-plug-ins-on-startup-in-sonar-x1-really/

    "The sky above the port was the color of television, tuned to a dead channel." WG

    SONAR Platinum | VS-700 | A-800 PRO | PCAL i7 with SSD running Windows 8 x64 | Samsung 27" LCD @ 1920x1080 | Blue Sky monitors with BMC | All kinds of other stuff
    #9
    John
    Forum Host
    • Total Posts : 30467
    • Joined: 2003/11/06 11:53:17
    • Status: offline
    Re:Scan VST folders on Sonar Startup 2013/05/07 02:23:22 (permalink)
    Nice blog Brandon. 

    Best
    John
    #10
    Katnip
    Max Output Level: -89 dBFS
    • Total Posts : 75
    • Joined: 2005/08/19 00:57:43
    • Status: offline
    Re:Scan VST folders on Sonar Startup 2013/05/07 14:52:31 (permalink)
    Yikes! I've been sitting through the lengthy scan process at startup assuming it was necessary, so after reading this thread I turned off the two rescan settings, as recommended, then rebooted my computer and got stuck in and endless list of error messages telling me that the computer couldn't start the program. After at least five minutes -- literally -- of clicking on what I suspected must have been a loop of error messages I was able to access Sonar X2. I turned the rescan settings back on. I'll live with it.
     
    #11
    scook
    Forum Host
    • Total Posts : 24146
    • Joined: 2005/07/27 13:43:57
    • Location: TX
    • Status: offline
    Re:Scan VST folders on Sonar Startup 2013/05/07 15:04:25 (permalink)
    That is not typical. Are you running SONAR as administrator?
    #12
    Elffin
    Max Output Level: -67 dBFS
    • Total Posts : 1196
    • Joined: 2007/02/11 16:49:19
    • Location: Wales
    • Status: offline
    Re:Scan VST folders on Sonar Startup 2013/05/07 15:30:43 (permalink)
    Can I presume that this is also true of Sonar 8.5?
    #13
    John
    Forum Host
    • Total Posts : 30467
    • Joined: 2003/11/06 11:53:17
    • Status: offline
    Re:Scan VST folders on Sonar Startup 2013/05/07 17:43:07 (permalink)
    No. In his post Noel said it was a recent fix. A later version of X1 or the new X2.  

    Best
    John
    #14
    Katnip
    Max Output Level: -89 dBFS
    • Total Posts : 75
    • Joined: 2005/08/19 00:57:43
    • Status: offline
    Re:Scan VST folders on Sonar Startup 2013/05/07 17:58:26 (permalink)
    That is not typical. Are you running SONAR as administrator?

     
    I'm not sure.   It's a new computer from Sweetwater running Windows 7, and they did the tweaks for audio. I've done very little so far other than load software and figure out how to use it. If I have to set it up to run as administrator, then I haven't done that. So far most of it is running according to the default settings.
    #15
    scook
    Forum Host
    • Total Posts : 24146
    • Joined: 2005/07/27 13:43:57
    • Location: TX
    • Status: offline
    Re:Scan VST folders on Sonar Startup 2013/05/07 18:07:35 (permalink)
    It might be worth a shot. There is no need to constantly rescan plugins. The default setup for VST scanning would be to have both rescan buttons unchecked and scan on startup checked. If you did not change the default scan parameters, Sweetwater did. I would ask them why they configured it that way since it is contrary to the recommended configuration by Cakewalk and why the box is performing in such a strange way when configured correctly.
    #16
    Katnip
    Max Output Level: -89 dBFS
    • Total Posts : 75
    • Joined: 2005/08/19 00:57:43
    • Status: offline
    Re:Scan VST folders on Sonar Startup 2013/05/07 21:45:02 (permalink)
    The default setup for VST scanning would be to have both rescan buttons unchecked and scan on startup checked. If you did not change the default scan parameters, Sweetwater did. I would ask them why they configured it that way since it is contrary to the recommended configuration by Cakewalk and why the box is performing in such a strange way when configured correctly.

     
    Just to clarify, the computer didn't come from Sweetwater with Sonar installed & set up, I bought it and installed it after I received the computer, so any tweaks to Sonar would be the things I've done (very few). I had already turned off one of the rescan options, but the other was still on.
     
    Some of the items in the list of things that couldn't be found after I turned off the other rescan option didn't look as though they are part of Sonar, but rather features of Windows 7, but I could be wrong. I probably should contact Sweetwater tech support with more detailed information and see what their assessment of the problem is.
     
    I didn't mean to hijack this thread from the original poster, but thanks for offering suggestions for solving my issue. I wanted to alert others who might try this of a potential problem. I still need to check to see if I'm running it as Administrator to find out if that corrects the problem.
    #17
    Jump to:
    © 2025 APG vNext Commercial Version 5.1