cool! but did you move them after the fact as i'm suggesting?
 
it feels like sonar sees the vst folder and looks through everything in it so that adding an extra "layer" of subfolders for reverb, eq, delay etc. wouldn't affect it
 
not like i have a ton of plugins etc. but it still will be really nice to have things grouped
there is a whole bunch of customization stuff i haven't really gotten into yet.  i'm too busy trying to learn applied theory etc. and well just writing this tune i'm working on.
it's been tough riding this learning curve while at the same time answering to the burning demands of the muse inside of me pushing for this song to be created and finished!
 

Moving VST plug-ins around manually usually works however; it can fail when a plug-in was installed using an installer program. Sometimes installers write information into the registry such as path information which will be broken when moving the files by hand.
 
The Cakewalk plug-in manager scans all the subdirectories in the scan path. Adding additional subdirectories to the directory tree is OK.

understood
 
i think in this case adding "depth" as you say would be the only thing i'm doing correct.  not really "moving" so much as just adding another layer?

The plug-ins are being moved from their install location. It does not matter if they still reside in the same directory tree, it is still a move. As indicated earlier, most plug-ins can be relocated without issue. If the plug-ins have registry entries with locations written in them, the registry may need to be updated.

seed
cool! but did you move them after the fact as i'm suggesting?

 
Yes I did, but only the VSTs that are just a simple .dll file. The others I re-installed.
 
Any VST that is just a .dll file that you put in your VST folder, you can simply move those however you want, and as long as you add the new VST folder to Sonar's plug-in manager, Sonar will see and use it - if it's in a "Reverb" folder for example, that folder will show up in Sonar's plug-in menu when you add a plug-in to a track using the FX bin.
 
For VSTs that use a Windows installer program, these are the types of plug-ins that scook is referring to - the installation procedure writes to the registry, and moving these plug-ins anywhere else, even nested sub-directories, will break them. For these types of plug-ins, what I did was un-install them, then re-install them, and during installation changed the path of the VST folder in the installation dialog windows. That way, the installation program writes the path I've chosen to the registry, so I could have installed the plug-in anywhere, even another drive (i.e. D:\VST64\Reverb) and the plugin will run from that location once that folder is added to Sonar's plug-in manager.

got it
i ran into a thought driving home last night that somewhat messes up my idea?
i can't really have a single folder for reverb because i have both 32 and 64 bit
so then i'll need a "reverb" and "reverb64" or something like that which semi-defeats the purpose
i hope cakewalk manager allows me to group however I want and that will be my solution :)
 
 
 
OK here we go!
 
i downloaded izotope vinyl last night and upon hitting the .exe it asked me where i wanted to put "it"
they suggested c>program files>izotope>vinyl
 
so i freaked out and hit cancel  =()
 
 
will this ask me later where to put the vst as e-mu proteus did?
or will it just put the .dll file under that path and then i'm screwed?
 
how do i answer the question the installer is asking me??
thanks as always guys truly appreciate your insight!
 
 

You can mix 32bit and 64bit plug-ins but in general it is better to keep them in at least two completely separate trees. Some have at least two trees for 32bit plug-ins. One for plug-ins known to work in 64bit hosts and another for plug-ins that only work in 32bit hosts.
 
The iZotope installer asks for several directories. IIRC, the first prompt for "C:\Program Files\iZotope\Vinyl" is the location where the help file, uninstall and other supporting files are stored. There are prompts later in the install process for the plug-in dlls. In the case of Vinyl, you may also want to install the DX version of the plug-in for the features not found in the VST version.

The general concencus is split your x32 and x64 base directories:
e.g.
<DRIVE:\>DAW_Plugins_32
- Rapture
--- rapture.dll
<DRIVE:\>DAW_Plugins_64
- Rapture
--- rapture.dll
 
Sounds like you wish to add a layer for Reverb, EQ, Compressors, etc
e.g.:
<DRIVE:\>DAW_Plugins_32
- Synths
-- Rapture
--- rapture.dll
- EQ
- Reverb
...
<DRIVE:\>DAW_Plugins_64
- Synths
-- Rapture
--- rapture.dll
- EQ
- Reverb
...
 
Mine are actually all under the one to 'top'
e.g.:
<DRIVE:\>DAW_Plugins
- Rapture32
--- rapture.dll
- Rapture64
--- rapture.dll
(Note: But because e.g. Rapture install only asks for the base directory and deploys 'Rapture' beneath, I had to employ the 'hack' to split it out to 32 and 64).
 
Regardless, I'd just put the x32 VST path in the x64 Sonar VST Scan Path as well as the in-built BitBridge feature will allow most of the x32 plugs to work in Sonar x64 mode. This is easiest seen in Browser>Plugins>Instruments - where x32 plugs are 'green' and x64 plugs are 'blue'. If it finds a double up x64 will take precedence.
 
x32 mode Sonar does not play x64 plugs - so just leave the x32 Sonar VST Scan Path pointing to x32 plugs. But it'll just ignore the x64 plugs if they are in the same path.
 
I think you know, but Scan Path denotes the 'top' of the tree. Any .dll beneath will be scanned and added if possible. If not, then in most cases it'll handle it, ignore and move on.
 
Re Q5: The line denoted whether the plug was a VST or DirectX - these seem to be split by separate sub-menus now ( are you on an older Patch Level? x3e is out :) ).
 
I should be able to post that "Good Tips" link after 3 days (tomorrow) - if you can't wait, Google "VST on Windows XLN" - first hit. (It's getting less exciting now with good tips in this thread).

oh and since we're talking rapture hehe
 
should i be using the DXi version or VSTi???
at least i think that's what i'm seeing :)

Use VSTi.  The DXi version has been discontinued.
 
Are you using version 1.1?  There is an update (v1.2) that you can download here:
http://www.cakewalk.com/S...b/reader.aspx/20090428