MuLab 10.0.85

[FabBad]

Which steps do i have to take to repeat this crash?
Please also email me the MuLab log file of that crashed session.

Mail sent

[humanboeing]

Hello there, just reporting that default rack setting doesn't work in M10 for me. In M9 one could name a rack preset "New.MuRack" and this preset would be used when creating a new rack. I suspect it's because the file format of rack preset has changed to standard .mux.

By the way, I'm really happy with how Mulab progresses, keep it up Jo!

[pljones]

Ah right - so this menu just saves a normal ".Mux" file and nothing to filter by to indicate it's a Mux Rack Preset -- you'd have to use a favourite folder for them...

[MuTools]

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

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

What's changed:

• On startup MuLab 10 will check if there are any legacy MuRack presets in your user library and propose to move them to the new MuLab 10 compatible user folder.
• Due to a recent new bug in M10.0.53, opening audio clips could cause a crash. Fixed.
• In some cases, empty audio clips could show a wrong waveform. Fixed.
• Changing an audio clip's end in the composer while it's also opened in a floating editor window did not immediately update the active play region in the floating editor. Fixed.
• Polished some UX aspects in the Multi-Form Oscillator editor.
• Other small improvements.

[MuTools]

Hello there, just reporting that default rack setting doesn't work in M10 for me. In M9 one could name a rack preset "New.MuRack" and this preset would be used when creating a new rack. I suspect it's because the file format of rack preset has changed to standard .mux.

Indeed.

In MuLab 10, the default location for your rack presets is the "User/Library/MUX/Racks" sub-folder. If that sub-folder also contains a "New Rack Templates" sub-folder, you can save several rack presets there to be used whenever a new rack is needed.
If it contains "New Rack.Mux" this one is your most default new rack and it will be used when you click the + rack button in a rack desk. If the "New Rack Templates" sub-folder contains several new rack presets for your various use-cases, then Shift+click the + rack button to popup a list with all these rack presets.

Starting with MuLab 10.0.54, on startup MuLab 10 will check if there are any legacy MuRack presets in your user library and propose to move them to the new MuLab 10 compatible user folder.

By the way, I'm really happy with how Mulab progresses, keep it up Jo!

Thanks

[FabBad]

Changing an audio clip's end in the composer while it's also opened in a floating editor window did not immediately update the active play region in the floating editor. Fixed.

That is fixed now, great.

Now I have a little request, I don't know if is easy or not, but what I noticed is that the module Parameter Event Generator is not audiorate.
many 3rd plugins has audiorate modulations and this module is the only door to access them for modular works. Please can you make it audiorate? would be inmense help.

[bibz1st]

Jo, just downloaded latest version and getting another virus warning...

Screenshot 2025-04-29 210251.jpg

[MuTools]

Ignore that false virus alert.
Feel free to doublecheck it on VirusTotal.com, it's totally green = ok there.

[bibz1st]

Dont worry I didnt doubt it, just thought you should be aware

[pljones]

Changing an audio clip's end in the composer while it's also opened in a floating editor window did not immediately update the active play region in the floating editor. Fixed.

That is fixed now, great.

Now I have a little request, I don't know if is easy or not, but what I noticed is that the module Parameter Event Generator is not audiorate.
many 3rd plugins has audiorate modulations and this module is the only door to access them for modular works. Please can you make it audiorate? would be inmense help.

MuLab modulators are audio frequency but MIDI (i.e. Parameter Event) is not audio rate, so it doesn't really make sense to turn it into events. You can, though... Audio -> Modulator -> Parameter. There's converter modules, it I remember correctly.

[FabBad]

Now I have a little request, I don't know if is easy or not, but what I noticed is that the module Parameter Event Generator is not audiorate.
many 3rd plugins has audiorate modulations and this module is the only door to access them for modular works. Please can you make it audiorate? would be inmense help.

MuLab modulators are audio frequency but MIDI (i.e. Parameter Event) is not audio rate, so it doesn't really make sense to turn it into events. You can, though... Audio -> Modulator -> Parameter. There's converter modules, it I remember correctly.

Pity
On converters there're audio and modulation options but not events except controller and note to modulation that for this case is no usable.

I downloaded a plugin that they claims to be audiorate modulation parameters, so I went to test on FL Studio with a LFO ramp generator (peack controller), and its has a sharp 1 sample change (which is as expected), but FL Studio is not audiorate, so I went to MuLab as it is audiorate, but sadly the only module that allow automating external plugin parameters is PEG which is at MIDI clock?


I leave a mux that demonstrate this.

[dakkra]

Hey, been a minute since I've said hi on here

Just wanted to drop by and sing some praise! From M4 through M9 I've been doing sidechain compression via the (what was project area back then but now) composer modular area and it was always a pain point to open into that modular area every time I wanted to change things. With the new modular racks and their new UIs, I can make a sidechain rack and have an easy button to open the compressor.

MuLab_ccOBuPXFXR.png

Such a great improvement!

[audiojunkie]

Is there a list anywhere of the instruments and effects that come by default in the plugin version of Mulab? For example, I know that there is a sampler of some sort. Being a Linux user, I want to use as many native compiled plugins as possible, and I realize that using Mulab as an instrument(s) will likely be the best way for me to integrate Mulab into the rest of my system as a Windows plugin, rather than starting to incorporate other windows plugins into Mulab.

[pljones]

The library is exactly the same between MuLab App and MuLab Plugin -- see the documentation (which will get updated for 10.x when it's released). More of the plugins are becoming modular, so I'm not sure what you mean by "native compiled plugins" -- do you mean Linux-native?

What kind of workflow are you looking for?

[audiojunkie]

The library is exactly the same between MuLab App and MuLab Plugin -- see the documentation (which will get updated for 10.x when it's released). More of the plugins are becoming modular, so I'm not sure what you mean by "native compiled plugins" -- do you mean Linux-native?

What kind of workflow are you looking for?

Thanks for your help! Sorry I wasn’t clear. I prefer native-Linux plugins. Occasionally, there are things that I would like to use in Linux that don’t have a native Linux binary—such as Mulab. I realize that the best way (for me) to do this would be to use Mulab as a plugin, through WINE and either yabridge or LinVST3. However, I don’t like to use Windows compiled plugins any more than I absolutely have to, so I prefer to use MuLab as a sort of modular plugin instrument, rather than a host for Windows plugins. Therefore, I’m interested in what instruments and effects have been built with MuLab’s modular capabilities that can be run natively in Mulab. For example, I’ve heard talk of a sampler, drum synth/sampler, multiple effects, etc. In other words, I’m thinking of using MuLab more like a Native Instruments Reaktor plugin for its instruments and effects, than as a DAW. Does that make better sense?