VST / Sample library storage

[therestisnoise]

Hi all,

My current set up is my Windows OS HDD (C drive) - it has the 'My Docs' and OS, DAW etc. and and second internal 1 TB SSD (D drive) for project files.

I understand that to get idea performance, you are best with 3 drives - 1 for OS/DAW, 1 for audio recordings, and 1 for VSTs/Sample libraries - first of all, is that correct do we think?

Secondly, with my current 2 drive set up, presumably am I best to store the VST/Sample libraries on the D drive (SSD) even though project files are there too?

Thanks.

[jthekidd427]

I always had everything on one external HD… but im sure theres a more efficient way… I also wonder if the computers HD would be better than an external hard drive

[BertKoor]

I understand that to get idea performance, you are best with 3 drives - 1 for OS/DAW, 1 for audio recordings, and 1 for VSTs/Sample libraries - first of all, is that correct do we think?

"Ideal" is the situation where the storage device does not get in the way of you getting things done. With spinning rusty platters the limiting factor was how fast the head could move from the inside track to the outside track, and then wait another cycle for the wanted sector to spin along.
Reducing wait times here involved multiple fast (7200 rmp) drives to spread the work load a bit. And then why stop at three, you can use a huge array of disk drives in RAID configuration.

But with the event of Solid State Disks (SSD) it's not true any more. No moving parts, less waiting. The limiting factor is now the data transfer speed.

My current set up is my Windows OS HDD (C drive) - it has the 'My Docs' and OS, DAW etc. and and second internal 1 TB SSD (D drive) for project files.

I bet you'll see a huge improvement in performance if you get rid of that old C drive altogether and put everything on one SSD.

[therestisnoise]

Ok thanks. I actually think I was incorrect and my C drive is in fact an SSD. I don't have performance issues but good to know for future reference.

[lobanov]

In many cases it's not possible to install VST and VST3 in a separate drive. With VST2 it is simpler as you may point to a folder in your DAW. With VST3 it's possible only if you can install them by copying files. You copy files first, either to defalt locations or to locations you choose. If you choose a special location you can make symbolic link to this folder in one of the system VST3 folders (in "Program files/Common files/VST3" and "Program files(x86)/Common files/VST3") and your DAW will find plugins there. Most DAWs don't allow to change these locations and pick up alternative locations (I mean VST3 plugins). Many installers don't allow to choose a place where VST3 plugins must be installed, they use defalt locations.

When you use installers they create records in the registry and copy files needed for a plugin (pictures, presets, configs etc.) to folders where this plugin will find these recources. Sometimes it is drive C, you can't change it.

So, in many cases you must install plugins on the system drive.

I prefer such logic: all what I can install by copying I place in non system drives. Mostly projects and libraries, partly plugins. If installers are inevitable I don't bother, I let them use places they are dedicated to use. May be, excluding their libraries (especially big ones). That is, in such a case I use system drive.

One important point. If one day my system drive fail to load I will reinstall OS and some software only (including some plugins). All other staff which I may copy is placed in other drives. (And yes, I backup these drives but this is a different story.)

[mixyguy2]

I understand that to get idea performance, you are best with 3 drives - 1 for OS/DAW, 1 for audio recordings, and 1 for VSTs/Sample libraries - first of all, is that correct do we think?

There is no "we," really - opinions vary. If your C: drive is big enough to hold everything, that's optimal speed-wise (though I would make regular backups to an external HD).

[RirtualViot2013]

Both my C: and my external drives are SSDs, but I still use an external SSD exclusively for sounds, samples and another different SSD for my project files. I do this mainly for organizational reasons. If you absolutely want to keep your sample libraries on your C: drive, then go for it - but make sure that you have enough space for it and make sure that your C: drive is fast enough to load your samples (a 7200 RPM SSD would be the absolute minimum requirement to do so in my opinion).

My personal recommendation:
Keep your Samples and Sounds off your system drive. The size of Sample libraries can amass pretty quickly (often quicker than you manage to notice it), and by default, you will have to install the .exe files of your DAW of choice and the .vst3 files of your plugins of choice on your C: drive anyway, so these will take up space to. An external SSD is the way to go.
I cannot speak for RAID systems since I have neither the experience nor the qualification to talk about it.

[therestisnoise]

Thanks. As I mentioned, I do have the separate SSD drive (where project files - ie: recorded audio - and sample libraries are stored) and the OS stored on C: (another SSD). The query was whether the optimum setup would be a third drive, so project files and sample libraries are on separate drives. But to be honest, in the time since originally posting this, I've answered my own query in that with the 2 ssd drives I haven't yet encountered any issues! Thanks all for input.

[dawzone]

Yes...storing your VSTs and sample libraries on the D: SSD (alongside your project files) is perfectly fine with modern SSDs. The traditional 3-drive setup made sense with HDDs, but SSDs efficiently handle read/write loads. Keep essential software and required VST3s on C:, and place large libraries and VST2s (if possible) on D. Focus more on a clean, organized structure and regular backups than trying to over-optimize drive usage.

[Keekee]

My current setup is I have the daw, and actual VST program on my computer hard drive. 2TB SSD. All my drums, VST Libraries, Sample packs, and Purchased libraries are on my separate 2TB external SSD. My best stems are on a separate regular hard drive. I believe it’s 2TB. I was taught early on that we shouldn’t have the Vst libraries on the actual internal hard drive because it could burn it out (not sure how valid this statement is now), but honestly if I could upgrade it (I have a MacBook so I can’t) I would have a large internal SSD to store everything but my STEMS. And I would just have a separate drive, or cloud storage to store my drums. Don’t really buy sample libraries anymore because they all get uploaded to various sites for download. (Wavs and Tracklib)

[BlackOctopusSteve]

I prefer all internal storage so I don't have an Octopus of hard drives coming out of my computer. There's enough Octopi from my neck of the woods.

[ThomekAV]

I really wanted to have everything on internal storage too but that's way too expensive for macbooks, so I had to settle with an external SSD (though it's definitely annoying to have something plugged into the macbook).

[Steff1968]

I use the micron crucial small portable one.
1TB... I find it works well... And very fast.