Hey guys, hope you all are well.

AFAIK Reaper stopped its support for x86 plugins a few updates back (must have been around June or July iirc)
So...is there a workaround this? I had quite a few very nice plugins in just this form, that unfortunately do not have a x64 version as they are not being developed anymore.
I must install a previous version of REAPER i guess?

 

I'm using version 6.34 and I can still open x86 plugins

 

Reaper x64 supports 32 bit plugins via its internal bridge.

Reaper 64-bit should auto bridge 32-bit, but make sure the directories involved are in the vst setup of directories in preferences.

 

REAPER can bridge both x86 and x64 plugins; I'm using version 6.29 (I haven't updated yet), where did you obtain this information?

EDIT: I was ninja'd lol

 

I also have some eighth or nine irreplaceable x86 plugins and when needed I open them in my old trusty Cubase 5.1.2 by dear Team AiR. I don´t like bridging at all.

 

Even vst2 is being discouraged for development. All operating systems are heading towards 64bit, RAM is heading towards larger sizes as are Hard disks. I understand preferences even though 32bit can only use 4GB RAM and I am sure DAW developers will hold off for as long as they can and maintain compatibility. However, at some point in the likely not too distant future, 32bit and most things associated with it will not be supported.

 

I[m not a reaper user, but if Reaper has stopped supporting 32 bit plugins, you could use Jbridge. I use it with Cubase 5 to read 64 bit plugins and with Cubase 11 to use 64 bit plugins too. Works well.

EDIT: should say: with Cubase 11 to use 32 bit plugins too.

 

Last edited: Aug 25, 2021

I'm not a reaper user either, but try Blue Cat's PatchWork this may solve your issues, maybe it's time to switch to 64bit unless you can't replace your 32bit plugins with something else newer

 

Just to be clear, to use 32 bits (x86) on a x64 program always needs some kind of bridging.
In Reaper is a feature, with other DAWs you need JBridge or another workaround.

JBridge worked like a charm, but hasn't been updated in a long time.

 

"Terminate REAPER immediately if a plug-in causes a corrupt heap."
... he he ... as if it will fall over and die, if a plugin does a bad turd !

 

If the plugin is running within the host process then yes, you'd want it to die as fast as you can. A corrupted heap is nothing to fuck with even if it's not malicious. That is, if you like your projects unmolested.

 

That reminds me that Reaper also can "firewall" plugins. Haven't tested it but I bet it makes the plugins independent processes so they can crash as hard as they like without crashing Reaper. Like Chrome's tabs, each page runs in its own process.

Damn, that's a sick feature.

 

You have three options here with Reaper, a) run everything within the host process <- I'm pretty sure this is the default as it's the most performant one but don't quote me on that, then you got two isolation options: b) a separate process for all plugins so a fucked plugin only takes down that process, i.e. all of your plugs, but not Reaper itself. Then you get the hardcore option, c) a process per plugin (safest, but eats most resources).

Every DAW should have this really.

 

Example.

 

Yes, it should.