I'm baffled by all of this trouble just to use some ancient dx plugins that could easily be replaced by free equivalents that are probably better in every way.

Anderton
There are some unique features in the Delay...

Agree. All the Sonitus plugs are good. My go-to delay is the Sonitus.
I have not found a suitable replacement for the Sonitus delay yet.
It can do Haas effect delays in .1 mS steps with the ability to mix in the dry signal, offset slap-backs or echos for stereo width, all the usual tempo related echos, Ping-Pong, EQ high and low filters, option for diffusion on the echo, etc.
  

azslow3
For Reaper. In case someone want Sonitus Compressor and Gate,
find the following in %APPDATA%\REAPER\reaper-dxplugins64.ini
and make sure "Load=1" is set for both (Reaper set it to "0")

[{C54E2D60-F9CA-11D2-8C30-00805FE9FC03}]
Name=Sonitus:fx Compressor
Load=1
[{C54E2D90-F9CA-11D2-8C30-00805FE9FC03}]
Name=Sonitus:fx Gate
Load=1

 
Notes:
* no side chaining
* if you force Reaper re-scan DX plug-ins, they will be reset to "0" (but continue to work in existing projects)
* the compressor adds one buffer delay (not Reaper specific, just simpler to see in it).

Same for
rgc:audio Pentagon I
Dimension LE
Roland GrooveSynth
 
I haven't tried these since I no longer have Reaper installed.

Thanks for the great tip Craig!!! Now I can use all of the Sonitus plugins in Studio One3!!!

I had installed these shells with Studio One and they appeared to work fine. However, having installed CbB I see that I now have, for instance, all the Sonitus plugs appearing twice, once as DX and once as VST2 (in their wrapper). Just for kicks, I loaded one instance of each version of Sonitus Compressor and selected the same preset, so that I could A/B them. Routing the same signal to them would make it hard to tell them apart, so I thought. In fact, the one wrapped as a VST actually sounded terrible; to my ear, it sounded like some kind of severe bit reduction. I carefully checked the setup to make sure that I had created identical parallel setups and I had. FWIW, the graphics on the wrapped one seem sluggish and wrong, too. Anybody know/guess why the wrapped version misbehaves in CbB? (I know this is not really a significant issue, but it has piqued my curiosity).

CakeAlexSHere

sharke
I'm baffled by all of this trouble just to use some ancient dx plugins that could easily be replaced by free equivalents that are probably better in every way.

Jeeze why am I always agreeing with you.. exactly.. time to move on.. there's a billion out there this is ancient tech and who knows when it will stop working. It's certainly not supported in any way.

As a rule I try to stay away from anything that is built on the x86 framework, anything that has been discontinued, and anything that even appears half baked. As a rule. It just makes my life in the studio simpler.

But there are a couple reasons to try to salvage plugins that fall into one or more of those categories:
1) they exist in old projects, and for some reason I need to briefly revisit that old project, and I don't want to spend time swapping plugins.
2) the old plugin has a feature that I have not yet found in a current plugin. Examples, for me, would include NI Vokator and Spektral Delay, and yeah, the danged Sonitus delay.
 
That doesn't mean I would stop my hunt for replacements, I'd dearly love to have a 100% x64/VST(3) system, but there are reasons to keep the dinosaurs, at least for a little while longer!
 
Now I've found a decent work-around for x86 VST instruments - VEPro has an x86 server that does a very nice job of hosting the older instruments. I suppose I should try it with old processors now?