KVR Audio

SHall1000 · Post by **SHall1000** » Mon Nov 14, 2022 10:48 pm

On launching an Ableton Live project, Monoment is showing the user preset (saved within the plug-in) I was using when the project was saved, but is playing a different sound (close but different). I’ve not been able to identify any difference in the plug-in settings from my original preset so far.
If I re select my user preset in Monoment browser the original sound is restored.
Any ideas?
Live 11, Windows 10, VST3.
Thanks.

JonSolo · Post by **JonSolo** » Tue Nov 15, 2022 2:03 am

Running as administrator?

BONES · Post by **BONES** » Tue Nov 15, 2022 2:11 am

I bet it doesn't happen with the VST 2 version. There seems to be something about preset management in VST 3 that causes problems. I get similar things with all kinds of plugins in Studio One and switching to a VST 2 version always seems to fix it.

mholloway · Post by **mholloway** » Tue Nov 15, 2022 5:49 am

SHall1000 wrote: Mon Nov 14, 2022 10:48 pm On launching an Ableton Live project, Monoment is showing the user preset (saved within the plug-in) I was using when the project was saved, but is playing a different sound (close but different). I’ve not been able to identify any difference in the plug-in settings from my original preset so far.
If I re select my user preset in Monoment browser the original sound is restored.
Any ideas?
Live 11, Windows 10, VST3.
Thanks.

I have the same issue with their Model-82 synth. This goes beyond Monoment. Bones may be right that it's a VST-3 thing only, I should check (let me know if using the VST 2 version solves it for you as well).

Sort of an aside, but my experience with VST3 has been:
Cons:
• more bugs
• *much* higher CPU usage in some daws (notably Bitwig)
Pros:
• not a single one I can think of. It offers me literally nothing over the less buggy, less CPU intensive VST 2 versions. woooo.

aMUSEd · Post by **aMUSEd** » Tue Nov 15, 2022 8:33 am

Was the original project made with the VST2 version but now being opened with the VST3? Softube plugins don't currently support VST migration so that might be the issue

SHall1000 · Post by **SHall1000** » Tue Nov 15, 2022 9:30 am

Thanks guys, will check if it is a VST3 problem. Resaving the preset in the VST3 doesn’t solve it.

aMUSEd wrote: Tue Nov 15, 2022 8:33 am Was the original project made with the VST2 version but now being opened with the VST3? Softube plugins don't currently support VST migration so that might be the issue

Yes it was. Can’t get my head round why that would be a problem. What info about the Plug-in state does The Live project store? I have resaved the project with the corrected VST3 preset loaded but it does not help so you could be right.

aMUSEd · Post by **aMUSEd** » Tue Nov 15, 2022 9:32 am

It's probably not Live unless it is one of the few hosts that don't support migration - in my tests none of the Softube plugins support migration (ie data saved with the VST2 in a DAW or project recalls successfully when the VST3 is substituted). It is probably because param Ids between the VST2 and 3 versions are out of sync. This is something only Softube can fix (I assume these days most hosts support migration but the plugin needs to as well)

SHall1000 · Post by **SHall1000** » Tue Nov 15, 2022 1:26 pm

Had this response from Softube supoort:

"I'm sorry to hear about your issues. There seems to be a bug in the latest version of Ableton (11.2.6)
This is an issue that we are looking into and I just wanted to confirm that I have added your information to our bug-tracking software.
In the meantime, a workaround is to use VST2 or revert back to 11.1.6.
Thanks a lot for your patience and support!"

aMUSEd · Post by **aMUSEd** » Tue Nov 15, 2022 8:55 pm

OK but it's still there case that none of their plugins support VST migration in any host

SHall1000 · Post by **SHall1000** » Tue Nov 15, 2022 9:14 pm

From my tests I can confirm this is a VST3 problem and it applies to all three of the Softube instruments I tried (Monoment, 72 and 84). The default preset is loaded on opening a project regardless of the preset loaded when the project was saved.

Interesting they say it’s a bug in Live. Not seen this in any other devs instruments that I’ve tested so far.

sacer · Post by **sacer** » Fri Nov 18, 2022 8:47 pm

It’s only Ableton 11.2.6, on beta 11.2 it works well.
Also if you load only the single track from an other project it works as expected. It only appears when opening a Ableton set.
There is also a bug with Ableton and PSPaudio which freezes Ableton on opening a live set. PSPaudio comment it’s only vst3 but I have these problems also with vst2. Ableton is very very buggy

SHall1000 · Post by **SHall1000** » Wed Mar 01, 2023 12:17 pm

Softube have released an update that appears to fix the recall problem……at least in Monoment Bass which I have tested.

mholloway · Post by **mholloway** » Sat Apr 08, 2023 4:37 pm

SHall1000 wrote: Wed Mar 01, 2023 12:17 pm Softube have released an update that appears to fix the recall problem……at least in Monoment Bass which I have tested.

Model-82, annoyingly, still has this problem with the VST3 version. I have to remember to only use the VST version. The VST3 will load up in Ableton sessions without recalling what was last programmed into it --- which is, as you can imagine, disastrous.

SHall1000 · Post by **SHall1000** » Sat Apr 08, 2023 10:00 pm

mholloway wrote: Sat Apr 08, 2023 4:37 pm
SHall1000 wrote: Wed Mar 01, 2023 12:17 pm Softube have released an update that appears to fix the recall problem……at least in Monoment Bass which I have tested.
Model-82, annoyingly, still has this problem with the VST3 version. I have to remember to only use the VST version. The VST3 will load up in Ableton sessions without recalling what was last programmed into it --- which is, as you can imagine, disastrous.

Have you reported it? I only tested Monoment Bass when the update was released and haven’t used any of the other synths since, although IIRC they all had an update.

Softube Monoment Bass not recalling preset properly. Solved.