I the VST needs a specific version of MSVC++ re-distributable that doesn't exist on the computer, some of them just silently refuse to answer Reapers call. Then they won't show up. Maybe that's it. Try running VST Scanner (just google)
If you want to verify that Reaper is seeing your VST, go to: Options Preferences Under Plug-ins, click VST At the top is the field where Reaper is looking for VST's. So, either: 1. Make sure your VST is where Reaper is looking, or 2. Add where your VST is located with the "Add" button. Hope that helps.
Except that Reaper frequently drops VST's (like Halion Player, Guitar Rig, many others) and then refuses to find the search path. These can't be anywhere else than they are because they need to be under 'Program (x86)' on Win 7 - otherwise they won't function due to compatibility issues. It gets extra annoying when they used to be available but aren't anymore. I'm not criticizing you, mixer, just saying that it's not always a stroll in the park, as has been noted many times elsewhere.
Just a thought, I've had some plug-ins load up but they come up with another name. I just figured that REAPER did'nt want to see them. Then months later I'll see something and not know what is, I open it and there's my lost plug-ins! Like I said, Just a thought. good luck
What I've been doing lately is have two folders. One for plug-ins that I use and one for all I have. I have 1 puter that is online that I download to and one for recording. I have a USB HDrive that I move back and forth. That way I can check if there clean before I move them to #2. Just last month I D/L'd something that even while I checking if it safe I got a virse that shut down my online Computer big time! Had to take it to the shop to get back online. All can say is it did'nt get to the recording Computer. This system works for me because it cut down on the start-up time as I'm not loading a ton of plug-in I might not need or use. If need one I just copy it to the right file and rescan and if I don't need it I delete it and rescan. Thanks for listening to this. Just my 1c or maybe 2. E.
------------------------------ A Retired Seven - Aussie740Limo 173K miles Brisbane, Queensland, AUST.
Makes sense, both for safety and load time. I'm mainly using just a dozen or so VSTs at the moment, since what I'm into now is just demoing material for my band. Since they're going to axe half of my material anyway I'm not gonna spend ages learning all of the guitar parts when I can get (reasonably) decent sounds with a sound font and Guitar Rig or Pod Farm 2. Drums, bass, keys get written and loaded as MIDI with appropriate VSTs for obvious reasons (I can't play them). Anyway, set up a folder system under 64 bit Reaper and had less than fun watching the whole thing fail. Several VSTs didn't load, others did but didn't work properly and a couple were ok. I noticed they were all bridged from Program x86 files, presumably because I didn't uncheck that option when installing the latest 64 bit version? Why 64 bit Reaper chose them over the folders I actually assigned I don't know - seemed like auto-detect worked for the first time, albeit without me using it, and preferred the x86 folders. I eventually gave up on the whole thing and force-fed R-32 my VSTs again, and now they seemed to stick (knock on wood). This time round it insists on loading the wrong ASIO driver, but that at least takes only three seconds to fix. If I do say so myself, I'm fairly good with some aspects of Windows, but I'm not certain what happened here. Still, a major improvement over yesterday. Cheers
One thing I love about my Mac is called "Audiounit Manager" a small app that lets you select what plug-ins will be active or inactive so you can selectively pick what you want before you run your DAW - is there a Windows app like that? It comes in handy when you have literally hundreds of plug-ins like I do.