wow i always used my dds As c drive but this thread states that i should use in for my D drive where all the projects and SVT are since there workin harded
is this a fact cus it makes sence. i have 2 SSD and a 2 tB to work with
so 1 ssd AS-C
     1 ssd AS-D with all the workfiles
 or the 2 tB drive as C. im confused whats best now
common sence would say use a SSD as your C drive for the base program and synths. ?

Jonesey/Kalle: Thanks for the info. I always turn mine off as well and leave my power options set to "performance". There are times though, when I leave for a few hours and was curious if it were a good idea to turn the drives off just so the computer isn't sitting idle yet being wide open. Thanks again...sorry for the hi-jack.

-Danny

You should definitively have one SSD for the c: drive where you have the OS.
But use the other SSD for projects and the 2TB for finished projects.

/M

Danny Danzi

Jonesey/Kalle: Thanks for the info. I always turn mine off as well and leave my power options set to "performance". There are times though, when I leave for a few hours and was curious if it were a good idea to turn the drives off just so the computer isn't sitting idle yet being wide open. Thanks again...sorry for the hi-jack.

-Danny

Hey Danny,


I don't know this via any kind of scientific research but I don't think it matters. I allow my drives to automatically power down if the system sits idle too long. No problems. I think I have the power setting at about 30 mins, so if there's no activity after 30 minutes the drives power down, but the system itself stays on. I don't like to use the sleep or hibernate options of Windows. I've sometimes had problems after "waking up" the system, but no problems with the drives.


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

One last question on this...


I my current setup I'm down to a choice to make for my Softsynth Library files. Which would be the better option?.

1:  Put them on a dedicated, non-partitioned 80GB HDD at 5200rpm

2:  Put it on the 2nd Partition of a 1TB 7200rpm drive (1st partition reserved for Sonar Audio)


and would the difference be significant?

moffdnb


One last question on this...


I my current setup I'm down to a choice to make for my Softsynth Library files. Which would be the better option?.

1:  Put them on a dedicated, non-partitioned 80GB HDD at 5200rpm

2:  Put it on the 2nd Partition of a 1TB 7200rpm drive (1st partition reserved for Sonar Audio)


and would the difference be significant?

Several folks have posted what I am about to say - there is no realistic performance point whatsoever in creating logical partitions.

All of the SATA 3 drives are plenty fast - 7,200 rpm is a better spin rate and more desirable than 5,200.

An SSD is much faster than a non-SSD SATA 3, but either has plenty of horsepower to avoid bottlenecks in Sonar.

If I ever see a need for it, I will add a third internal drive.  Right now, I use 2 - both are internal SATA 3 3.5" non-ssd drives.  I split them by OS and programs on the primary drive, and samples and projects on the 2nd drive.  

That works great - I never have any data issues or performance issues, and with the money I saved on returning a 512 GB SSD drive that crapped out in the first 3 months I owned it, I was able to buy another 16 GB of memory, a 46" HDTV, and 3 new pairs of Nike basketball shoes from the outlet store.


But back to my original point - you are better off buying a bigger case if you need it, and adding one or 2 additional SATA 3 drives - SSD or not, than you are by partitioning yourself silly.


Bob Bone

The ability to partition a HDD is a throwback to the old days when the average OS could only support "small" drives.

About the only use today is to have multiple operating systems on one HDD.

Partitioning a modern HDD for audio data is pointless and will reduce performance.

I disagree. Partitions offer an extra level of organisation, why not use it ?

I use multiple hard disks and partitions (which just look like disks). Makes things easy to backup (for example, just copy a data partition) and when you have to restore a broken OS you can reformat and clean install just the C: drive, nothing else needs to be touched.

I move all the "My ..." folders and Mozilla's profiles, Outlook's mailbox, etc, to another partition/disk.

Paul, just using top level folders will get you the same convenience backup-wise.  You could oganize it like:
C:\Windows stuff
C:\Sonar Stuff
C:\Outlook Stuff
etc.  Just a thought. Wouldn't help with reformats, I will concede.

Paul P


I disagree. Partitions offer an extra level of organisation, why not use it ?

I use multiple hard disks and partitions (which just look like disks). Makes things easy to backup (for example, just copy a data partition) and when you have to restore a broken OS you can reformat and clean install just the C: drive, nothing else needs to be touched.

I move all the "My ..." folders and Mozilla's profiles, Outlook's mailbox, etc, to another partition/disk.

For a computer with a single drive running office type applications, where file access times and read white speed is not so important I agree. But for a DAW no. Best to have three unpartitioned drives, one for the OS and programs, one for Audio and one (or even two) for samples. This is the way  to go if you want preformance.