VST best practices?

Author
Post
Essentials Only Full Version
kmcintyre
Max Output Level: -88 dBFS
  • Total Posts : 118
  • Joined: 2004/01/24 03:53:08
  • Status: offline
2016/01/30 13:51:20 (permalink)

VST best practices?

I'm running X3 and my VST Scan never completes since I installed Dimension Pro, Rapture Pro, and Z3ta+ 2 . 
 
Further, I'm having issues reloading VSTs when re-opening projects.  (I'm told that a soft synth dll is missing...) 
 
I have about 6 different vst directories in preferences.  There is no organization to where my VST dlls are located.  (Many installer seems to ignore my directions on where I want the VSTs stored.)  I have old versions, demo versions, full versions, some provided by multiple vendors as "free" soft synths...  32 and 64 bit versions... Yikes!
 
I ^think^ what I want to do is organize all my VSTs into a single folder, turn off autoscan, and manually manage VSTs as I install them.  (So let the installers do their default thing, then find the VST dll and copy it to my VST folder, then do a manual rescan with X3.)
 
Does this sound correct?  Is there a better way?
 
Thanks!
Keith
 
#1

2 Replies Related Threads
    scook
    Forum Host
    • Total Posts : 24146
    • Joined: 2005/07/27 13:43:57
    • Location: TX
    • Status: offline
    Re: VST best practices? 2016/01/30 14:25:28 (permalink)
    Depends on what you are trying to accomplish. If you only run one audio application or all your applications can use the same plug-ins then one big directory tree may work for you. However, moving things around is probably not going to help get a complete scan. Neither is turning off autoscan.
     
    When I had trouble getting a complete scan, I would incrementally build up my scan path by adding one path at a time to the scan path definition in Preferences. If the directory tree could not scan to completion, I would move parts of it until it would scan completely. Then add back pieces, scanning with every addition.
     
    Do not have the same path more than once Preferences. IOW, if your scan path include "C:\Program Files\Cakewalk\Vstplugins," do not add any children of the path and do remove any which already exist. For example, if the path also contains "C:\Program Files\Cakewalk\Vstplugins\Cakewalk Sound Center," remove it. It is redundant and can cause problems.
     
    It is not a particularly good idea to mix 32bit and 64bit plug-ins in the same path especially if they are the same effect. In 64bit installations, Cakewalk does install some 32bit plug-ins in 64bit directory tree. My guess is to reduce the scan path and installation as simple as possible. I avoid adding third party 32bit plug-ins to the 64bit path.
    #2
    dwardzala
    Max Output Level: -61 dBFS
    • Total Posts : 1470
    • Joined: 2008/05/26 19:18:33
    • Status: offline
    Re: VST best practices? 2016/01/30 21:22:16 (permalink)
    This tip from Craig Anderton may be of use.
     
    http://forum.cakewalk.com/FindPost/3361645
     

    Dave
    Main Studio- Core i5 @2.67GHz, 16Gb Ram, (2) 500Gb HDs, (1) 360 Gb HD
    MotU Ultralite AVB, Axiom 49 Midi Controller, Akai MPD18 Midi Controller
    Win10 x64 Home
    Sonar 2017.06 Platinum (and X3e, X2c, X1d)
     
    Mobile Studio - Sager NP8677 (i7-6700HQ @2.67MHz, 16G Ram, 250G SSD, 1T HD)
    M-Box Mini v. 2
    Win 10 x64 Home
    Sonar 2016.10 Platinum
     
    Check out my original music:
    https://soundcloud.com/d-wardzala/sets/d-wardzala-original-music
     
     
    #3
    Jump to:
    © 2025 APG vNext Commercial Version 5.1