sampletank 3 default instrument location

#Sampletank 3 default instrument location install
#Sampletank 3 default instrument location update

When I updated the machine, the biggest internal drive available was a 1TB SSD. Previous to my nMP I had a 2TB boot drive partitioned with the system and then non-music/video files. I suppose it all depends on how much stuff you have and where it needs to reside. I'm already seeing almost 100 GB worth of data associated with installers that I can't currently run, that I doubt would be worth the effort to try to trick off the system drive, and certainly it couldn't be done until AFTER installation anyway. Having a better feel for what is best practice in the current context, will help me decide how big my next system drive upgrade needs to be.

#Sampletank 3 default instrument location install

I can't even install Studio One v3 in full yet because it requires 36 GB of system drive space! Rhapsody Pro can't be installed either as it does really bizarre and incorrect stuff (including hiding the installed files, which are put in a temp directory) if you specify an off-system drive. Kontakt) and stuff like Vienna Symphonic Library, where the vendors have of course assumed from the get go that you will store the libraries on a separate drive, should remain so. Obviously the bulk of our sample libraries in more general formats (e.g. In fact, maybe performance would even improve in many cases vs. As the main reason I have tried to keep all app data on separate drives has been that it adds up quickly and gets larger all the time and thus will lead to a quicker need for a larger system drive, I'm wondering whether this old set of criteria is out of date at this point and whether there is no other reason to do this. Up until a few years ago, many of us made less than ideal choices in other areas (such as choice of sample rate and/or bit depth) due to the expense (at the time) of mechanical hard drive space. Given that prices WILL come down, is this a lost battle not worth fighting anymore? From a stability and performance point of view, is there an advantage in doing whatever possible to keep all app data on a separate drive? These have usually been too expensive to buy in large sizes, and apps themselves (as well as plug-ins) continue to grow, so even spending a huge amount of time moving things off the system drive only bides time anymore. I am speaking in the context of a fast SSD system drive. Given this issue, have people found it best to leave the default data path - especially in cases where it either can't be set at installation time, or botches up in various ways and isn't reliable after trying to rectify paths post-installation?

#Sampletank 3 default instrument location update

I am finding more an more installers insist on installing all app data (in most cases, read this as sample data in their proprietary format) on the system drive, and even if you can jump through hoops to move and redirect it later, often the next update will obliterate this move or cause other problems.