• SONAR
  • More on setting up 64 bit plugins
2014/01/01 09:58:36
Maarkr
So as I'm planning to do a new install of everything on a 64 bit SSD and leave my old plug installs on the old 32 bit C drive (soon to be D drive) I currently have my VSTs primarily in C:/program files/vstplugins.  I plan to put the new 64 bit stuff installed on the new  D:/plugins64bit and D:/pluginsvst3 move the old stuff to D:/plugins32bit???  
Can I install the cakewalk plugins on the D:?  Does it install a folder for 32 and 64 bit?  
I know I'll need to reinstall some of them, but just want the setup planned.  I'll prob understand better after I install it and look at the options.  Any other ideas appreciated.
 
Almost forgot... is there an ini file or something that I can copy from my 32 bit installation to the 64 bit installation that has my preferences and workflow setup?
2014/01/01 10:20:24
robert_e_bone
Well, Sonar will give you the 32/64 install option, and you will also get the chance to override the location of the 64-bit plugins.
 
As far as where either 32-bit or 64-bit plugins are located, Sonar will launch with a default set of paths that includes the one you chose for the install.  Once it is up and running, you can launch the Cakewalk Plugin Manager and add whatever additional path(s) you wish.
 
I DO recommend leaving your setup so that you can launch EITHER 32-bit or 64-bit Sonar, in case you have projects that just do not like having certain 32-bit plugins present in 64-bit Sonar.  (This is a frequent source of much drama and anguish).
 
In addition, I suggest you individually test out the viability of each 32-bit plugin to work in 64-bit Sonar (for which there is not a 64-bit replacement), and create a sub-folder within your 32-bit plugin folder and move the 32-bit plugins that work in 64-bit Sonar to the sub-folder.  THEN, you can add only the sub-folder with the tested plugins that work in 64-bit Sonar to the search path for 64-bit Sonar, and voila, you will be good to go.  
 
Doing the above will preserve the availability of all of your 32-bit plugins in your 32-bit Sonar, because the search in the 32-bit Sonar will automatically pick up the contents of the new sub-folder.
 
I HOPE any and all of the above makes sense, and wish you the best of it all.  
 
Bob Bone
 
2014/01/01 13:06:37
Maarkr
What??? Now I have to decide if I want to install 32 bit and/or 64 bit Sonar???
 
and is there a list/post of 32 bit plugs that won't work in 64 bit Sonar?
2014/01/01 13:22:30
robert_e_bone
You can have both a 32-bit and a 64-bit install of Sonar.  Lots of folks do.
 
I was just explaining the part of putting the 64-bit one in.
 
Bob Bone
 
2014/01/01 13:30:43
mettelus
To Bob's point, the actual X3 program files for X3 are not that "huge" at all. It is the sample libraries that consume volume on a disk. I have seen posts as well where folks run 32-bit X3 if they are going to use 32-bits plug-ins to avoid potential issues that have been noted with certain plug-ins. This is also why many choose the SSD for the OS/Programs/Plug-ins and a second (large) 7200rpm HDD for samples (some sample libraries out could fill an SSD by themselves).
2014/01/01 14:57:45
slartabartfast
Maarkr
So as I'm planning to do a new install of everything on a 64 bit SSD and leave my old plug installs on the old 32 bit C drive (soon to be D drive) I currently have my VSTs primarily in C:/program files/vstplugins.  



Are you planning to run this machine as a dual boot Win 32 or Win 64? I assume the current C: drive is a bootable system drive for 32 bit windows, since the drive itself is (presumably) formatted NTFS not "32 bit." Nor is your SSD a 64 bit drive, so I assume you plan to install an new Windows 64 OS on that. If you are not planning to dual boot, then you are wasting drive space and courting trouble by having two system drives in one machine. The cleanest way to re-use a drive that is set up as a boot drive, would be to copy off the data you want to save there, delete all the existing partitions to get rid of the OS-specific stuff, create one or more new partitions, format the partition(s) and then copy your data back on to the clean drive.
2014/01/01 19:58:34
Maarkr
Plan to install the new Win 7 64 bit OS to a new 240Gb SSD with only the OS and program files... no dual boot since my Win license is only good for one OS per machine... use the old 32 bit C drive as a D drive, load docs and VSTs on it... maybe later delete the Win 7 32 OS files from it, but I may reformat it and load the data files on it like u suggest.  I got plenty of room for stuff... 2 x 500Gb drives, 1 x 1Tb drive for samples, and a 3Tb backup drive.  I don't want to move too quickly in case the SSD/Win64 drive has issues so I can always go back to the Win32.
2014/01/01 20:09:22
mettelus
I have a 240Gb SSD. You should have plenty of room for the VSTs on there too, just be mindful of sample libraries. I run ~70GB free on mine, and have a lot of "non-DAW" programs on it of pretty good size.
2014/01/04 11:23:44
Maarkr
thanks... the libraries are not gonna happen on a SSD... my loops folder is 180Gb, 236,000 files, thanks to years of subscribing to CM.  Only prob is trying to manage and listen to them when needed for a project.
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account