HCMarkus wrote:although some would suggest using the SSD as your boot/applications drive. The call probably depends on how much VI stuff you do vs how often you boot your system.
This may sound goofy, but I kind of just don't trust SSDs quite yet for using them as the main drive (doing little writes all over the place). I just feel a little safer using it only as a send-only (non-write) drive. And the fact that the SSD here is the smallest drive, I figure using it for my current few VIs is best. But I ask...
Question: The
Slate Digital Drums and
Damage... How much of their installs are "VI data"? I.e., will I likely be installing a plug-in portion (on my applications drive) and then "VI data" portion separately, or does it all always go together? And
Slate FGX and
Recabinet, those would install purely as a plug-ins (on the applications drive), nothing for those installs on a pure VI drive, right? (Sorry if that's a stupid thing to get a confirmation of, but...

)
HCMarkus wrote:I like the external HD backup approach, as it allows me to keep two backup drives which I rotate on and off site. Having survived a wildfire 10 years ago in which my studio didn't fare so well, I cherish and protect my data.
My PC build allows me to hot-swap drives in the top of the case. (And they are "internal drives" drives, plugged straight into the mobo, are
not USB.) The 7200rpm drive was going to be the one sticking out the top so that I could often swap it with another of its low-cost ilk to do easy different-drive backing up (via copying project folders over from the 10,000rpm main drive).
HCMarkus wrote:You could put project and audio files on your 7200 RPM spinner, which should be able to serve up plenty of tracks to take care of all but the largest project. But your would then need a another HD to use as backup.
Cool. But if I have lots of room on the 10,000rpm drive then using that drive for the projects as well as OS and program files is fine, right? Or would it be
way better to have the project files on a different drive than where DP8 and MachFIVE and other plugs are installed? I just don't imagine the computer needing to be reading a lot of DP8's program code from the drive when doing playback, but am I wrong?
Do the OS and DP8 and plug-ins generally cause a lot of constant drive spinning in and of themselves (in acquiring their commands operation code)? I imagine it's just usually a blip of drive-read to send a command into RAM and that's about it (unlike bouncing to disc where everything is chugging away). Correct, wrong?
HCMarkus wrote:I'm currently enjoying an all-SSD workflow (except for backups) and finding it to be refreshingly speedy. SSD 1: OS, SSD 2/3: VI Data, and SSD 4: Project and Audio Files.
Nice. I don't really have the funds for that myself at this point. And I guess you're finding the SSDs to be fully reliable. Cool.
