MuLab 9.2.22 (CLAP plugin support)

[robert_p]

I reverted to 9.2.11 and opened Studio One session containing tracks created with 9.2.14. The MuLab's pop-out window informs me that the files were saved with the newer version, but the whole project loads and plays correctly. I remember having problems with this a while back (the session couldn't be loaded) and it's good to see that it works differently now.

[MuTools]

It doesn't work - the VST Editor is being minimised to the dock bar even if I use the button at the right of the rack slot.

Yes but if you open it using the rack slot button it works.

And then when I close and reopen the main MuLab GUI the VST Editor disappears from the bottom bar but it's window is blank when I open it again.

Ok that's a related but different issue. Will fix that too.
It's all related to the new way of opening/closing plugin editors, which is a consequence of adding CLAP plugin support. Hope you agree adding CLAP plugin support is a right choice. At least it gives a solid plugin future to MuLab!

[MuTools]

I reverted to 9.2.11 and opened Studio One session containing tracks created with 9.2.14. The MuLab's pop-out window informs me that the files were saved with the newer version, but the whole project loads and plays correctly. I remember having problems with this a while back (the session couldn't be loaded) and it's good to see that it works differently now.

No it has not changed.
Generally project/preset files are not downwards compatible.
But that only effectively happens when the file format changes.
The file format didn't change from M9.2.11 to M9.2.14.

[robert_p]

(..) I remember having problems with this a while back (the session couldn't be loaded) and it's good to see that it works differently now.

No it has not changed.
Generally project/preset files are not downwards compatible.
But that only effectively happens when the file format changes.
The file format didn't change from M9.2.11 to M9.2.14.

I see, so I was just lucky this time

[MuTools]

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

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

What's changed:

• Fixed a couple of issues with opening/closing plugin editors from the window dock bar, or when closing the main MuLab Plugin window in the host DAW.
• Refined behavior in case the User folder is not found/writable.
• Multi-Point Envelope editor: Unintended value field obstructing the editor. Fixed.
• Other small improvements.

[robert_p]

• Fixed a couple of issues with opening/closing plugin editors from the window dock bar, or when closing the main MuLab Plugin window in the host DAW.

GUI Bug not fixed:
---

[MuTools]

That specific plugin editor window bug reported earlier has been fixed. You can check it in Reaper. What's shown in the new video is specific to Studio One as it does things in a different way. There is a lot of ambiguity / poly-interpretation in the host <-> plugin world I'll try to find a solution for that case too. Thx for reporting it.

[robert_p]

What's shown in the new video is specific to Studio One as it does things in a different way.

The same problem exist in Cakewalk by BandLab

[MuTools]

I meant: There is a lot of ambiguity / poly-interpretation in the host <-> plugin world
Reaper (and maybe others) does it one way, Studio One (and maybe others) another way. Plug X does things one way, plug Y another way. It's a mess. And now also: VST2 does things one way wrt editor windows, CLAP does things another way wrt editor windows.

[robert_p]

I see. Wouldn't it be better to revert "code to open / close VST2 and CLAP plugin editors" as it was in ver.9.2.11, do some more tests and then update it if everything works well? Or are there some other issues in 9.2.11 that I'm not aware of (I didn't notices any issues on my system and this is the version I use)?

[MuTools]

I'm indeed also thinking about reverting part of the last developments as it seems that the host <-> plugin world is too jittery/unpredictable to do refined optimizations. Will research it a bit further but i also want a solid solution asap.

[MuTools]

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

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

What's changed:

• Improved behavior wrt plugin editors when closing the main MuLab Plugin window in certain host DAWs, eg Studio One.
• Extra crash protection against unstable plugins.
• Other small improvements.

[robert_p]

• Improved behavior wrt plugin editors when closing the main MuLab Plugin window in certain host DAWs, eg Studio One.

[MuTools]

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

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

What's changed:

• Bug fix in the VST2 plugin interface, more specifically when unplugin a VST2, which could cause issues upon quitting MuLab or opening another project.

[RichardSemper]

Mulab 9.2.17 and mulab 9.2.16 (App), with Dune v3

A difficult one to report as the results are inconsistent. Sometimes the following happens:

When opening the Dune 3 interface it is sometimes not working properly:-
1. The middle box with the patch names and settings not displaying the patch name, and the arrows to move through the patch selection jump to a couple of patches without changing the name displayed. Patch can still be found using the browse button, but changing it any other way fails.
2. Also the Dune Keyboard not working when the above fails. Press one key and it visually stays pressed, although the sound stops as it should when released.

Sometimes loading another synth (on a different track) seems to correct the situation i.e. when re-opening the failing instance of Dune 3 all works as it should. Sometimes the opposite happens i.e. re-opening an instance which previously worked now fails.
Opening a new instance of Dune 3 in a fresh clean project will sometimes work fine and other times fail as above. Loading new instances to new tracks - may load 3 or four properly before one fails - and re-opening the first ones may then all fail too.

I tried the mulab plugin version in Bitwig Studio, and found the same intermittent issues with Dune 3 interface there also.

I tried a number of other synth plugins, but found no similar issues so far - except for the now discontinued Linplug Spectral, which does have the same intermittent kind of problem with its patches screen.

Reverting to mulab 9.2.14 and both of these plugins work properly and as expected. Nor have I seen similar issues with these plugins run natively in other DAWs

Interested to know if anyone else can verify these issues?