More problems with 64 bit.

I'm trying to switch to Reaper 64 bit, and having lots of trouble. I currently still have almost all 32-bit plugins, as I want to do a little bit at a time. The only plugin I did install as 64 bit is the Waves collection. I de-installed Reaper X86, and then installed Reaper-64. When I try to launch Reaper, even a basic new session, I get this problem: * As it launches, I get several prompts that say " This plug is dedicated to the Reaper host. Bye!" I have to click through these, but then the session does open. * Once a BASIC Reaper session is open, If I do a cache re-scan, I get the same prompts. !!! If I open a PRE-EXISTING session & then do a cache re-scan, Reaper CRASHES once it reaches any midi plugin. I've taken all the midi Dll's out of my vst folder, but Reaper still crashes on the ones elsewhere. (The hidden folder, I assume.) I could find & remove these also, but I NEED them. -------------------- So what's going on here? Even if those midi plugins are old and not 64-bit, shouldn't Reaper just bridge them as it's bridging the other plugins? Also, when can I find newer versions of these? It's been so long that I've forgotten, and a search has turned up nothing. - thanks.

Is Reaper set to automatically bridge? You might install 64bit as a portable version which will be a little easier to deal with troubleshooting wise as you don't need to formally uninstall etc. How do you have your VST scan paths set in 64bit?

Thanks, Karbo. I have auto bridging checked. I have the scan set for 2 separate folders: the original 32-bit one, and a new one in the 64-bit programs folder, which I re-labeled "VST-64" I don't need a portable version, & I don't understand how that would help? ----------------- It just seems like Reaper-64 can't deal with these older midi plugins, and evidently the hidden ones do not get removed when you uninstall the 32-bit version of Reaper. I guess. I could theoretically start from scratch with a fresh OS install, but I really want to find the answers first. (Plus, there's no guarantee that that would work, anyway.)

Does the Reaper uninstaller NOT remove all old plugins, in the hidden folder? And, perhaps, are new versions of these plugins incorporated into the main Reaper installer (I haven't seen this mentioned anywhere) and thus are causing some kind of conflict? Could this be part of my problem?

Ah, thanks. I guess that might help diagnose, though it still won't actually fix the problem. Anyway, where do I get portable Reaper? I don't see it on the Cockos site, and I don't really trust third-party sites. -------------------------------------------------------- - AND CAN ANYONE TELL ME WHAT'S ACTUALLY GOING ON HERE? This can't possibly be the first time it's happened to someone.

Phasers? You've got 'em 

Just remember... after you select 'portable install' then select the path.. Reaper is then installed to one folder (instead of using the app data folder also). :cool:

Thanks. I figured out how to do a portable install, and yes, this problem goes away. But now what? I don't WANT a portable install, and I NEED those midi plugins! =============== As an additional test, I deleted all the invisible files in apps data - roaming (except the reaper setup file) and ran the full 64-bit version. the problem STILL happens. - And I see it happening after the cache re-scan sees midi rearoute. - Except that plugin should no longer BE in my system! WFT is going on here? Where could MidiRearoute be hiding? - And why can't I use it? This is now serious. I have no more time to deal with this & have to start a big project.. Ughh ...

I did the portable install and had difficulties with it until I remembered to delete the original folders. What worked for me: copy the entire %appsdata% for reaper (I renamed it to be safe) install the portable version overwrite the portable install files, not the whole renamed folder, with the old files (keeps all settings you made etc)I don't think you need to overwrite all of it but I can't remember the ones you need to do - ie,themes etc etc) A small but excellent video for how to do it if you are unsure

Well, I definitely learned something from this thread, so thanks to all. However, I could not completely eradicate the problem (I suspect I must have copies of those plugins, hidden somewhere on the drive) so I did a full OS install. No problem now, and now I know not to re-install those suspect midi plugins. THANKS !