Latest Update Killed My Old Projects

Official support for: kv331audio.com
Post Reply New Topic
RELATED
PRODUCTS

Post

The latest version shows up in Reaper as "Synthmaster 2.6 Instrument". The previous version showed up as "Synthmaster 2.5 Instrument", even though it was actually 2.6.something. So now, when I try to open a project with the last version, it says "Plugin not found" and loads without any Synthmaster instances. I have no idea what any of the patches were, either. So… that's less than ideal.

Post

Copy-paste the dll into a different folder, rename to 2.5 and move back to where it was. See if works.

Post

The plugin ID did NOT change. That's Reaper's problem if it is sorting plugins by their names.
Works at KV331 Audio
SynthMaster voted #1 in MusicRadar's "Best Synth of 2019" poll
SynthMaster One voted #4 in MusicRadar's "Best Synth of 2019" poll

Post

toothnclaw wrote:Copy-paste the dll into a different folder, rename to 2.5 and move back to where it was. See if works.
No please do not rename the DLL.
Works at KV331 Audio
SynthMaster voted #1 in MusicRadar's "Best Synth of 2019" poll
SynthMaster One voted #4 in MusicRadar's "Best Synth of 2019" poll

Post

So if we use Reaper we're just out of luck?

Post

Well I really dont know how Reaper handles the "uniqueness" of plugins. The VST standard defines a "plugin ID" for that purpose. I havent changed the ID between v2.5 and 2.6 and wont do that for v2.7
Works at KV331 Audio
SynthMaster voted #1 in MusicRadar's "Best Synth of 2019" poll
SynthMaster One voted #4 in MusicRadar's "Best Synth of 2019" poll

Post

I'll try to restore v2.5 on the server so you guys can download v2.5 as well.

and will test upgrading from 2.5 to 2.6 on hosts like Reaper and FLStudio.
Works at KV331 Audio
SynthMaster voted #1 in MusicRadar's "Best Synth of 2019" poll
SynthMaster One voted #4 in MusicRadar's "Best Synth of 2019" poll

Post

Okay, I found a workaround, thanks to some help on the Reaper forum. If I open the Reaper project in a text editor and run Find and Replace to change each instance of "SynthMaster 2.5" to "SynthMaster 2.6", the projects now open properly. I have to say, I've been using Reaper for several years, and have hundreds of plugins, and this is the first time this has happened. I don't know where the issue is, because you say the ID hasn't changed, and the filename is just "SynthMaster2.component", so where it's getting the "SynthMaster 2.6 Instrument" as the plugin name within Reaper is a mystery to me. It would be great if this could get resolved so it doesn't happen again, though! :wink:

Post

This is very odd. I just tested this myself by loading an old Reaper project that I'm pretty certain was done with 2.5 and it seemed to load fine?

Post

AU or VST? This project was AU.

Post

Ah...sorry. VST.

Post

No worries, it helps narrow down the problem!

Post

i'm totally confused?

Reaper is happy to load my older projects

would like to know how the description name change messed up Reaper!

if the dll had a different name that would make sense!

Subz

Post

Maybe because, as has been established, my project was using the AU.

Post

The plugin reports its name to the host, BUT, it's the plugin ID that the host should care.
Works at KV331 Audio
SynthMaster voted #1 in MusicRadar's "Best Synth of 2019" poll
SynthMaster One voted #4 in MusicRadar's "Best Synth of 2019" poll

Post Reply

Return to “KV331 Audio”