Those of you using SSD drives for samples... keep in mind that you really only get a performance boost for sample libraries that are streamed from the disk as they are being played. Many libraries (all those from Cakewalk) are just loaded into RAM, so you don't really gain an advantage there and you're wasting precious SSD space. Just my opinion...
 
Scott

--
Scott R. Garrigus - http://garrigus.com - SONAR X2 Power! - http://garrigus.com/?SonarX2Power
* Author of the Cakewalk Sonar and Sony Sound Forge Power book series: http://garrigus.com/?PowerBooks
* Author of the Cakewalk Sonar ProAudioTutor video tutorial series: http://garrigus.com/?ProAudioTutor
* Publisher of the DigiFreq free music technology newsletter: http://digifreq.com/?DigiFreq
* Publisher of the NewTechReview free consumer technology newsletter: http://newtechreview.com/?NewTechReview

Very true. I my case, the drive was there so it just made sense to put read only stuff on it. None of the samplers I use are setup stream so it does not really matter.

scook
Very true. I my case, the drive was there so it just made sense to put read only stuff on it. None of the samplers I use are setup stream so it does not really matter.

Cool... well, in that case, at least you do get the advantage of projects with synths loading up faster.
 
Scott

--
Scott R. Garrigus - http://garrigus.com - SONAR X2 Power! - http://garrigus.com/?SonarX2Power
* Author of the Cakewalk Sonar and Sony Sound Forge Power book series: http://garrigus.com/?PowerBooks
* Author of the Cakewalk Sonar ProAudioTutor video tutorial series: http://garrigus.com/?ProAudioTutor
* Publisher of the DigiFreq free music technology newsletter: http://digifreq.com/?DigiFreq
* Publisher of the NewTechReview free consumer technology newsletter: http://newtechreview.com/?NewTechReview

Why would you want to install 32bit and 64bit versions of Sonar?

If one had older projects with 32bit DX effects and synths a 32bit host must be used to open the projects and keep the plug-ins intact. It is also easier to work with older 32bit plug-ins in a 32bit environment. Other than that, I would use a 64bit host.

Consider using the SSD as a temporary "scratchpad" area where you house your active projects and their AUDIO folders.  When you are done with the projects, copy that entire file tree to the lower cost storage.
 
I had an SSD for my OS for a few years.  it was cool to have fast boot time, but really made very little difference after the boot.  But using the SSD for your project data pays dividends continuously.

aglewis723
Why would you want to install 32bit and 64bit versions of Sonar?

I use the DrumCore plug-in and have heard it should work in 64-bit but may be finicky, so I thought I'd install both. However, now that you're asking the question... it makes more sense to install 64-bit, and ONLY if there is a problem, install the 32-bit.
 
Yes? No?

garrigus
Those of you using SSD drives for samples... keep in mind that you really only get a performance boost for sample libraries that are streamed from the disk as they are being played. Many libraries (all those from Cakewalk) are just loaded into RAM, so you don't really gain an advantage there and you're wasting precious SSD space. Just my opinion...
Scott

Can someone explain the difference between sample libraries streaming from the disk as they're being played and ... the other kind, whatever that is? And a few examples of each kind so I can learn about this?

Streaming - To reduce their memory footprint some synths such as Kontakt or BFD can be configured to read their samples from disk while playing.
Nonstreaming - All of the Cakewalk sfz engine synths (Rapture, DimPro, Session Drummer, Studio Instruments) read their samples into memory when the synth loads into the project.

I believe that the streaming samples are very much the minority and probably a non-issue for most of us.