Posted - 01/29/2011 : 00:01:56
Initial scan in Reaper failed.
Not sure the reason. It was on Win XP which typically has been extremely easy to resolve.
Important instructions to follow:
Make sure all audio programs/hosts/daw's are closed. Then, install.
If using x64, IMPORTANT!
Windows hasn't exactly done us any HUGE favors with their handling of new operating system choices.
In numerous ways, we'd all be better off if they simply made the unlimited memory update to 32 bit and let us concentrate on faster processing and more parallel cores.
Anyway, If you are on 32 bit XP using the first V1.0 VTM-M2 32 bit:
Make sure all audio programs are closed when installing.
When the eLicenser comes up click demo.
Then close the eLicenser, and load your host.
Reaper has worked 100% of the time in testing if these steps are taken.
If you are on an x64 platform, here is where the fun begins.
Every since a late version of Vista, the fine folks at Microsoft wanted to make sure that everything you put anywhere in a folder on your computer, copy, paste, or move suddenly got treated like a level one threat to your system. OK, maybe that is a slight exaggeration, but I know a LOT of people have spent a LOT of money 'upgrading' to Win7 and x64 options, with a lot of memory and resources, and in many cases spent a lot in software upgrades, thinking double memory, processing, and expense should mean much faster and more instances to everything.
Well, the first thing to know is that the best chance for good first results on an x64 system is to sign on as administrator and then lower the level of protection in UAC so that Windows allows files to be installed, placed where they need to go, and that your DAW will allow what it needs to scan instead of treating everything we want to give you to place in your vstplugins folder as a threat.
Next, your x64 DAW is probably now re-assigning your plug-in collection to a folder called Program Files (x86) and reserving the traditional default plugin location to work with x64. To handle 32 bit plug-ins, there is a bridge to the x64 host and most of these have been tested and are working.
Make sure that you know your DAW's chosen path directories.
x86 path means 32 bit. Regular vstplugins path that used to be 32 bit is now used for x64.
If any conflicts occur in an x64 environment, close everything and re-install using 'right click' 'run as administrator' and then open your DAW 'right click' 'run as administrator.'
You must be logged in to see this link.
Software, Mastering, Tutorials