Yes, Reaper does have a scan log. I created a shortcut on my desktop to it.
 
On Windows, the file is located at, and called:
 
C:\Users\Primary\AppData\Roaming\REAPER\reaper-vstplugins64.ini
 
[Replace "Primary" with your username]
 
I set Windoze to default to opening Notepad for .INI files. Here's a small section:
 
SPAN.vst3=00EC7AEBB08CD201,555746558,SPAN (Voxengo)
SPL_Attacker.vst3=B63B055F1358D301,1872302934,SPL Attacker (Plugin Alliance)
SPL_Free_Ranger.vst3=00269A8E374AD301,2074663543,SPL Free Ranger (Plugin Alliance)
Tape_Multi_Track.vst3=00B127C6C35ED301
Tape.vst3=0084F6C4C35ED301,1563913648,Tape (Softube)
Tempo_Delay.vst3=00BA5C11E618D201,1791662028,Tempo Delay (Voxengo)
 
Notice that the "Tape_Multi_Track.vst3" line is incomplete, compared to the rest. That tells you that it didn't scan properly (makes sense, in this case; it's a Studio One MixEngineFX).

Michael A.D.
Another way to see ALL your VSTs is to go to View/Assets/FX Browser (or View/FX Browser)...

 
Thanks. I overlooked that menu item at the time becauses it says "FX" and I was looking for softsynths at the time. But I see that it actually includes both fx and softsynths. "Plugin Browser" would have been a more appropriate label.

TheMaartian
Yes, Reaper does have a scan log. I created a shortcut on my desktop to it.
On Windows, the file is located at, and called:
C:\Users\Primary\AppData\Roaming\REAPER\reaper-vstplugins64.ini
[Replace "Primary" with your username]...

 
Thanks. There's some useful stuff in that folder. I've now saved a shortcut to it too. However, the plugin log doesn't include the scan failures (e.g. DimPro).

Michael A.D.
...Obviously it's preferred to have all your VSTs in one convenient location, but certain products insist on installing to proprietary locations...

 
Tell me about it. I've got 9 different VST filepaths (excluding the 2 Prochannel VST folders). I keep a list of them and a set of shortcuts.

Michael A.D.
...Reaper can read both 32bit and 64bit VST, so (presuming you are using a 64 bit version of Reaper) don't bother installing any 32bit VST if given both 32bit and 64bit options when installing a VST.   If you ONLY have a 32bit VST for a certain program, then Reaper can use it without any additional bridge type programs...

 
I won't be ditching many 32-bit VSTs yet. A lot of them are used in the old Sonar projects that I want import into Reaper (using Azslow3's convertor).

Kev,
 
The plugins you mention all work rock solid in Reaper although Philharmonic 32 bit is slow to load bridged to 64 bit Reaper.. You just have to include the path to the dll in the vst preferences and hit rescan. Should fire up without problem.
What I miss in Reaper that Sonar has, is a clear indication as to where the vst/vsti dll is located. This can be an easter egg hunt otherwise in Reaper if something gets lost outside the selected paths.
Like Maartian advised, the reaper-vstplugins.ini file is a life saver troubleshooting whether or not a vst is missed, or registered and blacklisted.
And of course, Azslow's comments as well.
Can guide you step by step to get the plugs working if needed.
 
John

JohnKenn
The plugins you mention all work rock solid in Reaper although Philharmonic 32 bit is slow to load bridged to 64 bit Reaper.. You just have to include the path to the dll in the vst preferences and hit rescan. Should fire up without problem...

 
I've already added all the VST filepaths (including the one containing the philharmonik dll). By now I've run the scan several times. Philharmonik does not show up in Reaper. Neither does SampleTank and several IKM effects. These same plugins also don't work in Mixbus32C or Digital Performer and only work in Sonar if Sonar is run as admin.

UPDATE: DimPro
I didn't have DimPro 64 installed before, but I've installed it today. Reaper has substituted it in place of the 32-bit version for all my imported projects. That's one problem solved.

The folder mentioned is simpler to find by "Options/Show Reaper resource path...". That works independent from normal/portable install. These INI files are not "logs", they are configuration files
 
Philharmonik works for me in user mode (Reaper). Thy this: http://forum.cakewalk.com/FindPost/2648830  , including Philharmonik.ini, with mentioned content. I have also made INI file writable by user (not sure how important that is, but the whole story with "Run as admin" is about rights).
I hope you manage that, if not I can try to install MP on another PC to see what else should be done.
 
VSTs are identified by IDs, 32bit and 64bit versions use the same ID (at least I have not hit exceptions yet). Otherwise projects created in 32bit DAW version could not be opened in 64bit DAW version without all plug-ins bridged.
 

I've got Philharmonic working now. Most VST's DLL files have their own individual subfolder within the vstplugins folder, but Philharmonic's DLL and INI files were in the top level alongside  several other DLL files belonging to various other VSTs. I moved them to a new subfolder of their own and Reaper has now detected them after a rescan. I'll try moving some of the other loose DLLs to their own subfolders too and see if that makes a difference.