MuLab 9.2.22 (CLAP plugin support)

Official support for: mutools.com
Post Reply New Topic
RELATED
PRODUCTS

Post

syntonica wrote: Thu Jul 06, 2023 8:32 pm Now that this has been upgraded to beta status, can we get the Mac version? :pray:
Soon!
I'm getting bored as I haven't crashed MuLab for a few days... :lol:
The next M9.2.7 contains some serious code changes so maybe there will be some new bugs ;)
Though i'm doing my best to avoid that.

Post

rickpress wrote: Fri Jul 07, 2023 8:47 am what the plans are for 9.3?
Can't give info on that yet.
Currently focused on MuLab 9.2.

Post

RichardSemper wrote: Fri Jul 07, 2023 11:24 am No crashes here either. Been loading some older projects with vst's and audio - all fine!
:tu:
Not significant but a couple of log files attached showing VPM errors with vst plugins:
1: loading Dune 3 - this error did not occur with mulab 9.1
2: loading Tyrell N6 - this error also occurs in mulab 9.1 but not with mulab 8.x
I don't know what the error means, it seems to have no material effect with the plugins or the sounds, but it may highlight something useful so posted here.
About the Dune VPM error: When does that happen? Is it with specific presets?
I've the impression it occurs when Dune is outputing events to MuLab but don't know how to repeat that. Maybe Dune can send its arp notes to the host? Any tips?

Post

mutools wrote: Fri Jul 07, 2023 2:02 pm About the Dune VPM error: When does that happen? Is it with specific presets?
I've the impression it occurs when Dune is outputing events to MuLab but don't know how to repeat that. Maybe Dune can send its arp notes to the host? Any tips?
This error happens when loading a new instance of Dune 3. In the error log saved that was the only action taken.
The Dune 3 default preset is an arp patch, so just to check I started a new project, loaded dune, switched off the arp and saved the project. Closed mulab, re-opened and loaded the saved project. On closing still getting the same error in the log file.
Just to be sure, I have also removed all other plugins and tracks (I usually have limiter and mudrum in my standard template file) then resaved the file so its only one instance dune3 with arp turned off. Fresh load of mulab and this file - result: the error still appears in the logfile.

Post

Which version of Dune?

Post

mutools wrote: Fri Jul 07, 2023 2:45 pm Which version of Dune?
Dune 3.512

Now downloading the latest 3.55 I will see if the error persists
Last edited by RichardSemper on Fri Jul 07, 2023 2:56 pm, edited 1 time in total.

Post

Strange i can't repeat it with the current Dune Demo 3.51.
Anyway, i've now slightly finetuned MuLab's VST2 engine and possibly the error won't show anymore in the next M9.2.7. If it still does pls let me know.
The next M9.2.7 will be available tomorrow, i expect.

Post

The VPM error wrt Tyrell N6 will be gone in the next M9.2.7.
Thx for reporting that. It was nothing dramatic but no error at all is better of course.

Post

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

What's changed:
  • MuLab now supports rescan of CLAP plugin audio ports.
  • MuLab 9.2.4 and MuLab 9.2.5 did not launch on Windows 7 anymore. Fixed.
  • Quitting MuLab from inside a CLAP plugin editor could lead to a crash in certain conditions/with certain plugins. Fixed.
  • Fixed a small memory leak at the end of a CLAP plugin instance life cycle.
  • Speed optimization when sending parameter automations to CLAP plugins. (now supports 'clap.param.cookie')
  • Improved VST2 engine.
  • Specific shortcuts to the "Module" group did not work. Fixed.
  • Important CPU stack usage optimization. This results in increased stability because of a seriously decreased chance on a stack overflow. This modification is also important for MuLab Plugin as it uses the stack of the host DAW, like every plugin. This modification may also result in a tiny little bit more snappy GUI, especially on older computers and/or upon heavy audio DSP CPU usage.
  • Other small fixes & improvements.
Due to the technical works on the improved stack usage, some code has been modified, and thus there is a small risk on new bugs, although it has been tested quite well. In fact during these tests some other bugs have been fixed that stayed under the radar in previous versions.

MuLab 9.2 for Mac & MuLab 9.2 Plugin will follow soon.

Post

Also MuLab 9.2.7 Plugin beta for Windows 64 bit is available:
https://www.mutools.com/mulab/plugin/la ... /beta.html

This includes all latest improvements and thus also includes support for CLAP plugins.

Mac versions coming in a couple of days, still some todos there.

Post

Hi, 4 VSTs unrecognized (probably not the most recent versions but I don't want to update them yet - I need to check the compatibility with my old projects first to avoid potential surprises). They're not buggy and they run fine with all other hosts (Including MuLab 9.1.28).
---
VSTi2.jpg
---
P.S. Reverting to 9.1.28 clears up the whole plugins list (fortunately, I had a backup of "VstPlugins.Xml").
You do not have the required permissions to view the files attached to this post.

Post

robert_p wrote: Sat Jul 08, 2023 11:09 pm Hi, 4 VSTs unrecognized (probably not the most recent versions but I don't want to update them yet
I very recently checked Dune 3 and it loaded fine in M9.2.7.
Please try rescanning these plugs. If they don't scan succesfully then please forward do MuLab menu -> Tools -> Keep Log and email me the log file. Thx.
Reverting to 9.1.28 clears up the whole plugins list (fortunately, I had a backup of "VstPlugins.Xml").
I can't repeat this. I repeated this case using MuLab App 9.2.7 and then reverting it to MuLab App 9.1.28, all worked fine as expected, plugin database stayed intact.

Post

mutools wrote: Sun Jul 09, 2023 8:34 pm I can't repeat this. I repeated this case using MuLab App 9.2.7 and then reverting it to MuLab App 9.1.28, all worked fine as expected, plugin database stayed intact.
I added two CLAP plugins to 9.2.7 (Surge XT and Vital) that were obviously absent after reverting to 9.1.28 (I had however Vital VST2 installed and MuLab 9.2.7 showed both of them as Vital(1) and Vital(2) - could that be the reason the database was cleared?
Please try rescanning these plugs. If they don't scan succesfully then please forward do MuLab menu -> Tools -> Keep Log and email me the log file. Thx.
Ok, I'll do it when the next MuLab Beta is out - I don't wat to mess up with my current project right now.

P.S. I found the log file - I'll email it to you in a minute. I remember that those 4 plugins showed errors when I tried to load them and later on (after rescanning) were marked as "unrecognized".
Last edited by robert_p on Sun Jul 09, 2023 10:58 pm, edited 1 time in total.

Post

robert_p wrote: Sun Jul 09, 2023 10:44 pm I added two CLAP plugins to 9.2.7 (Surge XT and Vital) that were obviously absent after reverting to 9.1.28 (I had however Vital VST2 installed and MuLab 9.2.7 showed both of them as Vital(1) and Vital(2) - could that be the reason the database was cleared?
No.

Post

MuLab App & Plugin 9.2.8 for Windows 64 bit are available:

App: https://www.mutools.com/mulab/app/lates ... /beta.html

Plugin: https://www.mutools.com/mulab/plugin/la ... /beta.html

What's changed:
  • Finetuned the "Setup Rack Sidechain" tool in various aspects.
  • Option to insert a "Send To Nothing" send into a rack slot, which can then be connected to a sidechain input using "Setup Rack Sidechain".
  • Fixed a recent new bug in the VST2 engine.
  • More stack usage optimizations.
  • Other small yet important fixes & improvements.

Post Reply

Return to “MuTools”