MuLab 9.3.18 - VST3 plugin support

[RichardSemper]

Less important these days as most plugins have their own method for patch saving and recall:

mulab can save and load patches for vst2 format plugins (options in the top bar), but this facility is missing for the vst3 and Clap variants:

PatchSaving PluginFormats.jpg

[MuTools]

MuLab App 9.3.10 beta is available on https://www.mutools.com/mulab/app/lates ... /beta.html

MuLab Plugin 9.3.10 beta is available on https://www.mutools.com/mulab/plugin/la ... /beta.html

What's changed:

• VST3 plugins: Misc. improvements.
• When using a shortcut to New/Open/Revert Project from inside a plugin editor could cause a crash with some specific plugins. Fixed.
• MacOS: Doing Cmd+Q from inside a plugin editor could cause a crash. Fixed.
• Dropping REX files did not work anymore. Fixed.
• Other small improvements.

Both Windows and Mac versions are available now.

FYI: Beta versions M9.3.6 to M9.3.9 were unpublished.

[tatanka]

Less important these days as most plugins have their own method for patch saving and recall:

mulab can save and load patches for vst2 format plugins (options in the top bar), but this facility is missing for the vst3 and Clap variants:


PatchSaving PluginFormats.jpg

Ok, thanks, will try the vst2 version if there is one (I am not sure).

[sl23]

It's difficult to predict the future. One thing is sure: 32 bit and VST2 will be a dead end. MuLab will keep supporting 32 bit and VST2 as long as it sufficiently makes sense, but anyway they will be a dead end.

that's why I'm switching now!
Personally, I hope CLAP becomes the new standard. It's early days though!

[sl23]

Less important these days as most plugins have their own method for patch saving and recall:

mulab can save and load patches for vst2 format plugins (options in the top bar), but this facility is missing for the vst3 and Clap variants:

This isn't important for me. I'm pretty certain that every plugin I have has its own way of saving, loading and navigating presets. But it's a good point for those that don't...

[sl23]

Thanks for the update Jo.

[robert_p]

MuLab Plugin 9.3.10 beta is available (...)

Thanks for the plugin update! The Limiter Module - input gain meter shows "pre-fader" values, which is inconsistent with output gain "post-fader" meter. It has this behaviour since I remember. I believe that "post fader" input metering would have more sense (it would reflect the "Input Gain" knob level).
---

Limiter.jpg

[syntonica]

Now we're spoilt for choice! But which version is best to use? Some plugins come in many formats, so what do you think is the best format that's future proof, reliable, stable, etc. Does it matter?

I would say CLAP > VST2 > VST3, in all ways. I'm sure somebody will have a different opinion, of course.

CLAP is designed to support both MIDI and audio as equals with sample-accuracy. VST2, while officially dead, can be made to do the same. VST3 has very poor MIDI support and can suddenly go the way of the dodo (a.k.a. VST2) when SB gets around to it. There's a reason why VST3 adoption has been glacial, at best.

[pljones]

Thanks for the plugin update! The Limiter Module - input gain meter shows "pre-fader" values, which is inconsistent with output gain "post-fader" meter. It has this behaviour since I remember. I believe that "post fader" input metering would have more sense (it would reflect the "Input Gain" knob level).

Isn't the point that the meter on the left is entirely before processing and the meter on the right entirely after processing by the module? (You may have no other meters close to the module, so they're useful.) I'd not want them to change. Otherwise you might as well argue for having a meter after the input gain and before the output gain, so the gain faders were taken out of the comparison (after all, both could be replaced by meters just before and just after the module, whereas the post-input gain and pre-output gain can't).

[tatanka]

Less important these days as most plugins have their own method for patch saving and recall:

mulab can save and load patches for vst2 format plugins (options in the top bar), but this facility is missing for the vst3 and Clap variants:


PatchSaving PluginFormats.jpg

Ok, thanks, will try the vst2 version if there is one (I am not sure).

Gladly the vst2 version works and shows the preset as in you screens

As lot of the useability of these bx plugin really lies in the knowledge that goes into the presets I am really happy I can go on using them with the vst2 version.

[sl23]

I would say CLAP > VST2 > VST3, in all ways. I'm sure somebody will have a different opinion, of course.

CLAP is designed to support both MIDI and audio as equals with sample-accuracy. VST2, while officially dead, can be made to do the same. VST3 has very poor MIDI support and can suddenly go the way of the dodo (a.k.a. VST2) when SB gets around to it. There's a reason why VST3 adoption has been glacial, at best.

Ok, now I'm confused! So are you saying VST3 is not a good idea to adopt yet? And It's better to stay with VST2 until it's really dead?

[robert_p]

Thanks for the plugin update! The Limiter Module - input gain meter shows "pre-fader" values, which is inconsistent with output gain "post-fader" meter. It has this behaviour since I remember. I believe that "post fader" input metering would have more sense (it would reflect the "Input Gain" knob level).

Isn't the point that the meter on the left is entirely before processing and the meter on the right entirely after processing by the module? (You may have no other meters close to the module, so they're useful.) I'd not want them to change. Otherwise you might as well argue for having a meter after the input gain and before the output gain, so the gain faders were taken out of the comparison (after all, both could be replaced by meters just before and just after the module, whereas the post-input gain and pre-output gain can't).

To see the metering before the processing you could simply set the input gain to 0dB. (the same way you currently set the output gain to 0dB to see output gain metering after the processing). There is no visual feedback/limiting indicator and there is no way to properly "drive" the limiter (e.g. if the "brickwall" limiting is needed with the threshold 0dB and the input signal is significantly higher or lower - how you gonna gain stage it without the metering?)

[robert_p]

P.S. Another solution would be adding a gain reduction meter.

Example: VC76 compressor meter has a switch: In-Gain reduction-Out. Input meter follows Input Gain knob:
---

Compressor.jpg

[syntonica]

I would say CLAP > VST2 > VST3, in all ways. I'm sure somebody will have a different opinion, of course.

CLAP is designed to support both MIDI and audio as equals with sample-accuracy. VST2, while officially dead, can be made to do the same. VST3 has very poor MIDI support and can suddenly go the way of the dodo (a.k.a. VST2) when SB gets around to it. There's a reason why VST3 adoption has been glacial, at best.

Ok, now I'm confused! So are you saying VST3 is not a good idea to adopt yet? And It's better to stay with VST2 until it's really dead?

If you have a choice of formats, then choose in that order. Unfortunately, new plugins are only being released in VST3, so it is indeed necessary. For now.

[SeanTypedThis]

Works great with all SWAM Audio Modeling VST3 plugins I've tested so far, will report if there are any hiccups!

One place, at least in REAPER, where VST3 still has an advantage is the ability to use MIDI Busses. This mostly comes in handy for people making use of large orchestral templates where they're working with hundreds of virtual instruments at a time; I'm not one of those people, but MIDI busses do help me stay organized, as I generally use a separate bus for each controller.

All that to say, is that implementation something that would be easy to enable or their is already access to that I may be missing? Though I use the plugin version, and it's easy enough to just have multiple instances on multiple tracks, and I could see their being a limitation there as the plugin itself is not VST3 and probably wouldn't recognize busses.

In any case, great great update as always, can't wait to restructure a few more instrument racks with autobypass!