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)
Reply To: Superior Drummer 3/Reaper problem version: 3.3.6 Operating system: Windows 11
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.
Reply To: Superior Drummer 3/Reaper problem version: 3.2.7 Operating system: Windows 10
This post was modified 2 years, 3 months ago by fiftywatt.
