Quote:
Originally Posted by inarisound
Recently I switched from OSX to Windows platform and I can't figure out why lots of my 64 bit plugins like Battery 4 or Alloy are not visible by Reaper.
|
Can you maybe copy & paste your VST Plugin path listed under Preferences > Plug-Ins > VST here, so we can see how it currently looks like?
Quote:
Originally Posted by inarisound
How can you tell if it's 64-bit or 32-bit dll ?
|
Some developers (like NI) are using the same file name for both the 32- and 64-bit .dll files. So one option here to find out the version is to
Right-Click > Properties > Details on a .dll file in Windows File Explorer and check the product version there. As example for the Battery4.dll: if it says
x64 (for 64-bit) or
IA32 (for 32-bit).
If you have both the 32- and 64-bit paths added in Reaper's plugin path at the same time and both .dll versions also have the same name, Reaper will only see one of the two plugin versions (if I remember correctly the one which is last added in Reaper's plugin path).
As others already mentioned above, some developers install their plugins to default locations regardless (without the option to choose a different install path). And there are also some plugins (like MPC Essentials) which require to be installed to a specific location in order to work properly. So it usually can't be avoided (to some degree) to have plugin files scattered over multiple locations ...
----------------
As a side note:
Although the example in this article uses Ableton Live, the shown plugin organization procedure via shortcuts (pointing to the original install location) in a custom folder can also be used with other DAWs like Reaper:
https://music.tutsplus.com/tutorials...e--audio-10021
This can be useful for organizing some plugins which cannot be installed/moved to a different custom location without breaking anything ...