Superior Drummer 3/Reaper problem

[fiftywatt]

Hi everyone.. longtime Toontrack user, first time post..

I’m getting the following error message when I try to view the SD3 plugin within a Reaper project:

The installed resources and the plug-in are not the same version!
Plug-in version: 3.2.7
Version of resources: 3.3.6.35757
Please reinstall Superior Drummer 3

Here’s the other odd thing. The previously built drum tracks play correctly in the main Reaper timeline
but I have no way to view the MIDI tracks, kits, mix window etc. (I’m running PC hardware and Windows 10.)
Until a couple of weeks ago, it has been smooth sailing with SD3 (which I upgraded to in 2019)
The odd thing is that my other DAW is Sonar (used mainly for remixing older legacy projects from the early 2000’s).
SD3 loads and runs flawlessly inside the Sonar environment without incident. All of the SDX’s and MIDI show up as
expected.

I’ve completely uninstalled/reinstalled all of my Superior Drummer 3 resources. Also uninstalled/reinstalled Reaper.
All of my Toontrack installs, SDX’s, MIDI packs, etc. are up to date. I am totally stumped.

Superior Drummer 3 version: 3.2.7
Operating system: Windows 10

Topic

[Mac McCormick]

This has problem has been mentioned in this forum several times over the last few years.
Here’s the original post.
https://www.toontrack.com/forums/topic/getting-error-message-after-updating-sd3-from-3-14-to-3-15-solved/

Good luck!

Superior Drummer 3 version: 3.3.6
Operating system: Windows 10

Cubase Pro, Korg Kronos, M-50, Hammond XK-1c, Toontrack SD3, EZBass w/lots of expansions, many VSL Vi's, Shreddage 3 everything, and shit-tons of FX plugins.

1

Thanked by: Scott Eshleman

[fiftywatt]

Profuse thanks Mac!

1

Thanked by: Mac McCormick

[fiftywatt]

Some progress.. but here are the new wrinkles..
I can launch older Reaper projects that I’ve spent many hours in building drum tracks with SD3.
I still get the same error message when trying to view the SD3 plug in (when I click on the track)
I can hear the drum tracks if I hit play in Reaper, but no view of the internals of the plug in.

BUT.. I can insert a new instance of SD3 and the plug in internals view just fine.
Wondering if I can recover the MIDI drum data from the old instance?
I could do a workaround from there and salvage the drum tracks.

Superior Drummer 3 version: 3.2.7
Operating system: Windows 10

• This post was modified 2 years, 1 month ago by fiftywatt.

[Olof Hermansson]

When you insert a new instance, is it a VST2 or VST3? Try inserting the other kind. If it says it’s not version 3.3.6, it’s an old copied plug-in that you should locate and delete.

Olof Hermansson - Toontrack
Coder

[fiftywatt]

Hi Olof.. I suspect I have been using the VST2 type instance in all of my Reaper projects.
It’s always worked just fine (until it didn’t and I got the error as discussed)

I can insert a VST3 instance and the SD3 workspace comes up just fine.
Any idea how I could recover the MIDI drum data from the VST2 instances?
If I cannot do that, then it looks like I will have to start from scratch building
my drum tracks anew.. (which is not a terrible thing since SD3 is such a great plug-in)

Superior Drummer 3 version: 3.3.6
Operating system: Windows 11

[Olof Hermansson]

You just need to fix the VST2 so that you don’t have an older version of it. Check the Reaper preferences what the plug-in paths are. Search in them for a “Superior Drummer 3.dll” that is not version 3.3.6. If you find it, delete it. Then see if Reaper finds the correct VST2. If it doesn’t find any, launch the SD3 standalone and select “Show Plug-In Path” from the Help menu. Add that path (but without “\Superior Drummer 3.dll”) to the plug-in paths in Reaper. (Do not move or copy this dll.)

Olof Hermansson - Toontrack
Coder

[fiftywatt]

Thanks Olof! I finally located the obsolete

.dll. Once I deleted it everything worked

fine again. Profuse thanks!

[Author]

Replies