Up to 35 tracks at most 44.1khz 24bit In Logic. I use a lot of samplers as well. Kontact,Guru,Symphonic orchestra. I was wonder which raid is best 0, 1, 5 doesnt matter, tryin to figure out what to buy with new mac pro
I use RAID0 with 48KHz 24bit recordings and playback easily an Arrangement with 70 tracks with heavy synths aswell such as NI contents, Spectrasonics Atmosphere, etc. .. Reading and Writing is super fast.
http://en.wikipedia.org/wiki/RAID#Organization
RAID0 is the fastest you can get but not that secure. So you have to have a BACKUP ! If one HDD failes, all data is lost. I personally do not Backup all my stuff such as installations. Only my personal mac profile with all logic projects and librarys etc. are saved ! So if this will happen to me one day, I just have to install my programs again which will propably take one day but I have a clean system then anyway ;-)
You can use RAID 01 aswell, but you need a minimum of 4 drives:
"RAID 01
RAID 0+1 (or 01) is a striped data set (RAID 0) which is then mirrored (RAID 1). A RAID 0+1 array requires a minimum of four drives: two to hold the striped data, plus another two to mirror the first pair."
I am also in the same situation as the OP and have been wondering about RAID with recording.
I was wondering however, do you run your samples off a separate HD with your Logic project files off another second separate HD? I have heard that reading and saving files onto the same HD will slow down Logic so I was thinking of keeping my sample libraries (I also use many NI stuff) on a mechanical HD, but I'm still unsure of where to store my Logic project files...
Oh and are you using SSDs in your RAID?
I have never heard of this slow down of Logic. Where did you read this (link) ?
If your projects typically involve many audio tracks, consider a dedicated hard drive for audio. If your computer supports multiple internal drives, then an additional internal 7200 RPM drive would be a good choice.
It appears the information provided by Apple is based on the presumption disks are used as individual drives, so RAID (no matter if hardware or software implemented), wasn't taken into consideration.Wow, thank you very much for your reply. It was very helpful.
Its just from a support article link I've read from Apple that I've read from:
http://support.apple.com/kb/TA24535
After reading this, i just assumed that keeping your project files and audio & samples on separate HDs seemed like the most efficient way. But before I found this article, I wanted to keep both files on the same drive. And if you experience no hiccups, then I guess there isn't an issue at all really.
It appears the information provided by Apple is based on the presumption disks are used as individual drives, so RAID (no matter if hardware or software implemented), wasn't taken into consideration.
But RAID runs much faster. In the case of a stripe set (RAID 0), the throughput is n* single disk performance of the drives used. So a 4x drive stripe set is 4x faster than one of those drives by itself. So in such circumstances, you can put it all on the array, and not suffer throughput issues (but keep in mind, with mechanical disks, keep it at 50% full or less, or you're going to slow down on the inner tracks).
But as mentioned, make sure you've a proper backup in place. But with one difference: Backup is needed whether it's a single drive, or the most complicated RAID on the planet (and level implemented does NOT matter either, as RAID /= Backup).
Yes it will. So will other software, as it sees the array as a single disk (including the OS).Ah, thanks! I think I recall that Time Machine will backup the entire array as one drive, correct?
In the case of a stripe set, Yes. Throughput differs with other levels though (depends on n drives and the level of redundancy involved).About the speed of the array, so you're saying a 2X drive stripe is 2x faster, 4x is 4x faster, etc...?
SSD's aren't the best for writes just yet as a result of existing Flash technology (especially MLC). The statistics used by SSD makers is a manipulation. They only utilize the best 90% of cells, and the wear leveling is based on an empty disk, which boils down to non-real world conditions.And what if your intended RAID is using SSDs. I plan on doing this, except my only concern is constantly writing to the SSD RAID. All those command+S, plus constant copying of samples and audio files into local project folders can't be good for the SSDs, can it?
I have never heard of this slow down of Logic. Where did you read this (link) ?
I have all my samples/librarys/projects on my personal profile (intern HDD) stored (Macintosh HD/Users/my profile). The hole user profile is backed up. I have a 3x 1TB WD Caviar Black HDD RAID 0 installation and an external 1.5TB Backup at the moment. I never experienced a HDD overload in Logic and as I remember and the usage is always around 5% (I guess) anyway. I am not at home right now to look at it.
For now, it's best to keep high write environments to mechanical drives. So SSD's are fine for boot/application drives, but keep the rest of it on mechanical if you're writing often (especially temp/scratch data).
You can use either a single SSD or a stripe set. I like the idea of the latter, but you have to be careful of the throughputs during simultaneous access (SSD + HDD raids at the same time), as you could throttle (exceed what the SATA controller is capable of handling). There is a limit within the chipset of ~660MB/s.Thanks, I figured that was the most practical solution for SSDS still today. So I guess a possible (good?) alternative is to keep a RAID0 of SSDs for boot/application, like you said, and then perhaps a second array of mechanical drives for temp/scratch/write and audio library storage to maintain the read/write speed?
If you go through the hassle of getting both an SSD and a mechanical array, I'd split things up. Place the libraries on the SSD (as it's read performance), and the writes to the mechanical array. BTW, for best performance on a mechanical set, keep your capacity usage to 50% or less, otherwise you end up on the inner tracks, and they'll slow you down (and it gets worse the fuller the drive).This is just going back to my concern about keeping Logic project files, in which a lot of writing will occur, and the audio files library, in which a lot of reading will occur, on the same "disk". Do you think a mechanical RAID0 would remedy this, or is this probably something I shouldn't worry about...?
Quite understandable.Looks like I'll take things one step at a time then and try to achieve one striped set first and I'll see where I (and my funds) can go from there.
A 2x SSD RAID is probably as far as I'll go for now.
If you do RAID 2 SSDs, let us know if you find any real world performance increase (compared to a single SSD). In bench tests you will find them, but I'm sceptical about real-world performance.
Loa
I don't know if RAID is really worth the hassle, but it is essential to have discrete drives for your separate functions. Along with a backup, of course.
My own setup is (and it's pretty standard for audio work):
Drive 1: Boot/apps
Drive 2: reading/writing audio (where project files are saved)
Drive 3: sample libraries
Drive 4: backup/time machine
I don't know if RAID is really worth the hassle