Posted - 01/29/2011 : 03:15:26
There was a time, in the not-too distant past, where there were two main native platforms for consideration:
Windows and Mac.
Wow, how quickly time flies!
So, here is the deal;
It would be one thing if the choice for Windows was simply 32 bit or 64 bit.
The real issues that develop are 32 bit or 64 bit, on an x64 OS?
You can run 32 bit and 64 bit plug-ins in a DAW running 64 bit on a 64 bit Windows platform.
In the olden days of 32 bit only, the typical install path was:
When changing over to x64, the decision was for the default directory for the new x64 plug-ins to be...
Wait, isn't that the same thing?
Now, my way of thinking is that a new technology would get the new pathway name, seeing that whomever has migrated to that new expensive upgrade is doing so with a large investment in 32 bit plug-ins.
Well, what happens is that all previous plug-ins before x64 upgrade/migration, are directed to the Program Files (x86)/Steinberg/Vstplugins folder, and the new x64's are placed in the one mentioned above that used to be used for 32 bit plug-ins.
You can see where this could cause issues.
So, if you are brand new to the game and just bought a 64 bit OS and DAW and the only plug-ins you have bought thus far come from the past 6 months, more than likely 1/2 of them are 32 bit and the other 1/2 64 bit. You probably have two install paths and one 64 bit host that can read both.
Imagine if you installed one 32 bit host and one 64 bit host.
You will be redirecting one of them to a different choice for vstplug-ins so they don't think that Program Files folder is for the wrong bit option.
ALL of this to say that the first release of VTM-M2 is 32 bit and belongs where you put your 32 bit plug-ins. Make sure that when you install, that you choose the location where your 32 bit plug-ins are located.
You must be logged in to see this link.
Software, Mastering, Tutorials