I've finally upgraded my computer and it took me roughly 6-8h to move and set up everything I needed: 3x DAWs, +/-100 VSTs, few folders with samples & projects.
Reason 10 and all the 3rd party REs was - obviously - a breeze, due to its closed environment and one-click-do-everything mechanism, but the rest was painful and long (some of the servers were very slow). I did everything "manually", i.e. had to log in to every website I got stuff from, download it, install, authenticate, etc. Actually this is the first time I appreciated middle-man installers from Arturia, iZotope, NI, kiloHearts, Soundtoys, Plugin Alliance or even Waves because it makes things so much easier. Or how FabFilter, despite not having a dedicated installer, allows you to authenticate all plugins with single file - brilliant! What bugs me is none of the installers gave me a choice for placement of VST3 files and many of them install 32-bit VSTs and AAX plugins without asking (I had 2GB of AAX plugins and around 1GB of 32-bit VSTs to remove!!!). Samples & projects was much easier using Google Drive, although obviously it required some preparation to have everything neatly packed into self-contained folders.
Anyway, wanted to ask for your experience & tips for the future.
Are there any Windows software solutions out there making this simpler? Any tips on where to install things for the process to be easier in the future?
Moving DAWs, plugins, samples & projects to new computer (Windows)
- Banned
- 11467 posts since 4 Jan, 2017 from Warsaw, Poland
-
- KVRist
- 128 posts since 13 Aug, 2017 from Gothenburg
I completely agree about 32-bit and AAX plugins. I really wish I had the option to skip those.
In some cases I wish I could skip VST2 and only install VST3, but I don't think anyone will allow that.
As for tips, the only thing I recommend would be to create a Windows restore point before you embark. And start with the installations that you suspect are most likely to mess up.
All my project are backed up on Google Drive in a sensible folder structure, so that part has never been any problems.
In some cases I wish I could skip VST2 and only install VST3, but I don't think anyone will allow that.
As for tips, the only thing I recommend would be to create a Windows restore point before you embark. And start with the installations that you suspect are most likely to mess up.
All my project are backed up on Google Drive in a sensible folder structure, so that part has never been any problems.
-
- KVRAF
- 10372 posts since 2 Sep, 2003 from Surrey, UK
To name but three, IK Multimedia, iZotope and MeldaProduction allow VST2 (and AAX) to be skipped.
I thought that VST3 plug-ins had to go in (a sub-folder) in C:\Program Files\Common Files\VST3 (on WIndows). But that may just be a standard that Steinberg wishes to enforce.
I thought that VST3 plug-ins had to go in (a sub-folder) in C:\Program Files\Common Files\VST3 (on WIndows). But that may just be a standard that Steinberg wishes to enforce.
- Banned
- Topic Starter
- 11467 posts since 4 Jan, 2017 from Warsaw, Poland
Yes, they do by default but they apparently don't have to - I moved all of them elsewhere and they work just fine.DarkStar wrote: Mon Apr 15, 2019 11:51 amI thought that VST3 plug-ins had to go in (a sub-folder) in C:\Program Files\Common Files\VST3 (on WIndows). But that may just be a standard that Steinberg wishes to enforce.