MuLab 9.3.18 - VST3 plugin support

[syntonica]

Attached is a Mac crash report from z3ta+2 on instantiation.

I hope this is a you problem and not a Cakewalk problem only because this plugin will probably never be updated.

[pljones]

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?)

So you are arguing that the meters should be post-input gain and pre-output gain, as those adjustments don't affect the limiter itself? I can see sense in having both sets of meter, rather than lose either, though.

[robert_p]

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?)

So you are arguing that the meters should be post-input gain and pre-output gain, as those adjustments don't affect the limiter itself? I can see sense in having both sets of meter, rather than lose either, though.

Input Gain affects the limiter itself but the level adjustments results are not shown on the input meter. I suggested post-input gain meter (currently pre-input gain meter) and post-output gain meter (as it is now). I'll attach my concept limiter (MUX) later on.

[robert_p]

(...)

• post-input gain meter

• gain reduction meter

• post-output gain meter

Limiter.jpg

---

Limiter.zip

[dakkra]

Hmm as of 9.3.10 the ToneBoosters plugins are now failing to load Just get a could not create instance error.

[dopet]

Excited for this development. Keeping an eye on MuLab now….

[MuTools]

Hmm as of 9.3.10 the ToneBoosters plugins are now failing to load Just get a could not create instance error.

Tried TB Barricade 4.7.2 in M9.3.10 and it works fine here.
Anyone else having issues with Toneboosters VST3 plugins?
Dakkra, please email me the log file.

[sl23]

Oh should've posted, I tried two demos last night barricade and eq, they worked for me too.

[sl23]

OK, so I've been doing some research into the VST2 vs VST3 debate, and found several sites about it. The only one that I found giving, what appears to be, impartial judgement, is BlueCatAudio.

I can only see one genuine reason not to switch to VST3. That is the part described under limitations...

Limitations

The VST3 standard has however one major limitation regarding MIDI events: plug-ins can no longer process MIDI data directly. The main consequence with our plug-ins is that when used as VST3s, they cannot output MIDI CC events like with other plug-in formats. So if you intend to use the advanced MIDI output capabilities of our plug-ins, you should use the VST2 version instead.

[EDIT 2021: this limitation has been removed in the VST3 SDK but many hosts still do not implement it properly]

So what exactly does this mean? Surely VST3 can control midi CC's? Seems ridiculously stupid not to! And why would hosts not implement it properly? Again, isn't this a fundamental part of midi?

Any thoughts?

[Michael L]

I would say CLAP > VST2 > VST3, in all ways.

Yep. For the sake of stability & familiarity & if-it-ain't-brokeism

[MuTools]

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

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

What's changed:

• VST3 plugins: Support for selecting internal programs.
• MacOS: Possible issues on Quit. Fixed.
• Other small improvements.

[tatanka]

Thanks for trying to implement the selecting of internal programs for vst3 but it does not seem to work on the PA bx plugins.

I did a rescan of the bx_masterdesk true peak and then tried the bx_masterdesk but both does not show the internal presets.

The vst2 version works and shows presets.

Do I maybe have to do a complete rescan of the vst3 directory ?

[FabBad]

Can we known what

Other small improvements.

are?

Just curious.

[MuTools]

I didn't log them. It are aspects that do improve things but are too technical / detailed to log.

[MuTools]

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

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

What's changed:

• Improved VST3 engine. Cakewalk Z3ta now also plays fine.
• Plugin Manager was still using term "Synth" instead of "Instrument". Fixed.