MuLab 9.3.18 - VST3 plugin support

[robert_p]

This may be a good thing actually - keeping one format only should help migrate the projects from vst2 to vst3. E.g. if I try to do that in Studio One (remove vst2 from the database and add vst3 instead and open an existing project) I would get a "plugin not found" message (while MuLab would work just fine).

EDIT: I tried and it didn't work: I removed Surge XT VST3 from the plugin manager and added CLAP instead - MuLab asked me to locate VST3 when re-opening the project.

[sl23]

Yeah I had the same idea, but didn't think it would work due to the different filenames/extensions. Shame they aren't interchangeable like that though. Maybe one day...

[sl23]

I've just gone through and renamed all the VST3 plugins I added yesterday and the 'not found' issue seems to have gone.
Though all the u-he plugins are categorised as Effects for some reason. Is that info from the plugin itself, or MuLab?

[RichardSemper]

double-checked and the issue is definitely with multiple formats of the same named plugin. Same for Fx plugins.
When reloading a file saved with one of these:
- reloading the file gets a prompt for the plugin location
- drag and drop from the plugin browser to a new track or a plugin slot prompts for the location, or gets ignored completely.
- interestingly, selecting a plugin from the slot dropdown loads it properly.
Removing duplicate named plugins from the library allows the remaining one to load properly.
The above results are the same whichever format of the plugin is being selected.

Amazing update btw. So far all the vst3 plugins I have tried are working in mulab!

[FabBad]

This is incredible, finally did it! well done!

testing some plugins, and i tested one in particular, and this plugin uses some kind of internal routing based on instances. But this doesn't work as expected.

that's all for now, if I found any other misbehavior I'll let you know.

Regards.

[MuTools]

This may be a good thing actually - keeping one format only should help migrate the projects from vst2 to vst3. E.g. if I try to do that in Studio One (remove vst2 from the database and add vst3 instead and open an existing project) I would get a "plugin not found" message (while MuLab would work just fine).

Chance is low that this would work as the plugin data probably also depends on the plugin format.

Anyway, the next update will have refined behavior when there are multiple formats of the same plugin in the plugin database.

[MuTools]

Though all the u-he plugins are categorised as Effects for some reason. Is that info from the plugin itself, or MuLab?

The plugin defines whether it's a synth or effect.
For a VST3 plugin, in the Plugin Manager check the SubCategory in the info pane at the right, if it contains "Instrument" then it's a synth/instrument, not an effect.

[MuTools]

testing some plugins, and i tested one in particular, and this plugin uses some kind of internal routing based on instances. But this doesn't work as expected.

Please elaborate about this case.

[Calum]

Thank you for a most welcome update!

Just to add to the list of VST3s that are working as expected on my system:

• Vaporizer2 (Vast Dynamics)
• Wavetable (Socalabs)
• Stochas (Surge Synthesizer Team)

XT-S1 (EnergyXT) also works but I get a brief popup saying "Error while opening plugin editor" every time I load the plugin.

(Just for info, the VST2 version of Vaporizer2 instantly crashes Mulab on a MAC during the plugin scanning process.)

[FabBad]

testing some plugins, and i tested one in particular, and this plugin uses some kind of internal routing based on instances. But this doesn't work as expected.

Please elaborate about this case.

My bad.

This happens when copy that first instance (beginning of the chain) and paste by dragging.

Actually you have to insert another instance, not copy.

No problems with Mulab at all.

solved.

[MuTools]

MuLab App 9.3.3 beta for Windows 64 bit is available in https://www.mutools.com/mulab/app/lates ... /beta.html

What's changed:

• Support for VST3 plugins that change their IO setup during their lifetime.
• Support for VST3 plugins with multiple event input / output busses.
• More tight protection against VST3 plugins that would cause a serious error.
• Refined behavior when the plugin database contains multiple plugins with the same name but different plugin format. The appendixes like (1) and (2) are omitted. A plugin name will now have a plugin type appendix like "[VST2]" and "[VST3]" if there are duplicates.
• When searching for a plugin, eg upon loading a project or preset, any spaces in the plug name are always ignored, eg. "Dune3" and "Dune 3" are regarded the same.
• When a plugin was renamed while its editor was closed, then reopening its editor still showed the old name. Fixed.
• More tolerant for VST2 plugins that (falsely?) report an error during initializing their editor.
• Plugin info display: Term "Synth" has been renamed to "Instrument".

[robert_p]

MuLab App 9.3.3 beta (...)

Surge XT (CLAP) - "Couldn't create some module(s), see log file" when re-opening the project:

Log-20231005-160247.zip

[MuTools]

Apologies for this stupid bug

Fixed in MuLab 9.3.4 beta: https://www.mutools.com/mulab/app/lates ... /beta.html

Thx for reporting it!

[robert_p]

Fixed in MuLab 9.3.4 beta (...)

Everything is working fine now, thanks for the fix!

[sl23]

Thanks for the updates!