MuLab is incredible. Few newbie questions.

[kmonkey]

Hi guys. I am having a really good time. I discovered MuLab recently. Still a newbie and learning. Incredible piece of software. The quality of modules is incredible. I have a few workflow questions.

1. Is there a way for me to "automap" or auto-populate (I am unsure what word to use) the parameters of a synth in another DAW?

Example. I use MuLab as a plugin in Reaper. Say I load a preset called "Digital Organ". Which is a MuSynth actually. So in order to automate some of its parameters when I look in my DAW - I don't see any in most cases. I see MP1, MP2, MP3, and so on.

I get it. I learned from YouTube (btw MuLab desperately needs more videos) that I can click Show Modular Area. From there I can click on the synth parameter label and drag it into MP1, MP2, and so on.

My question is is there some faster way? Is there a way to click and move multiple parameters onto the area? Like grab 10 parameters and move into this MP1, and they are mapped sequentially or in random order. Or perhaps there is a way to click onto something and all parameters (or the first 128) load up into these MP1, MP2, and MP3 instantly and from there I could pick a parameter by my DAW and automate it?

2. The second question is somewhat related to the first one. Do I understand this correctly? When I load MuSynth for example. There's no actual preset list in the synth itself? There are no individual presets or "snapshots" in the loaded instrument - so to speak.

I get a fresh and empty start with no preset in the synth itself correct? It seems to me that none of the Synths have an actual preset list inside. ??

The way the MuLab paradigm is imagined is that there are no presets/snapshots in any of the creations correct?

I could load presets which are in fact single individual Mux modules. So for example in the browser some organs are MuSynth, some organs are built from some other modules, and so on.

But here comes my issue with not having a list of presets for a MuSynth for example. Say I load Digital Organ (MuSynth). I manually map some of its parameters to an MP1, MP2, etc.
And my DAW sees parameters.

Ok fast forward into my session, I decide that this organ is not working for me anymore. I need to load another preset of a MuSynth from the MuLab browser. Say for example Digital Organ 1. But when I do that all of my parameter mappings are gone - hence my question do I understand correctly, there is no preset in the synth itself, they are all rather individual designs saved in the browser.

Am I correct? Is there a way (assuming I am loading all MuSynth presets only) to keep parameter mapping sent to my DAW when I change MuSynth presets?

3. I understand VST3 preset saving is coming in the new beta and upcoming releases. But I have the VST2 plugin loaded in MuRack. Is there a way to save that plugin individual started in the MuLab browser and then drag it in another session? So far I am unable to do it. I was able to load the complete Rack with the VST2 plugin inside and then load the complete rack in another session and move the VST2 plugin out of it into where I need it, but I would love to save the preset of the individual plugin in browser and drag and drop it in another session. Possible or not?

4. In the rack slot I load - Audio Processor - Amp Distortion. I tweak some stuff there. I can not save this module anywhere, nor can I drag it into a browser. ?

[pljones]

For 1, I think there's an improvement that could be made.

"In the olden days", "MuLab Plugin" was "MUX", which is the modular area inside the project. If you open, say, Basic Synth, then open the project modular area, you'll see all the Meta Parameters (MP) are just called MP0, MP1, etc. However, if you double-click the "Basic Synth" module and look at its modular area, you'll see the Meta Parameters have names.

Ideally, the project main module - in this case "Basic Synth" - would have its Meta Parameters mapped 1-for-1 to the project Meta Parameters, including the names. Currently, you can manually go through the project MPs and map each to the main module MPs.

Once you've done that, Reaper will show all the Meta Parameters just by right-click the module, "Show FX Parameters in Panel" and picking those you want to show. Then you can use Reaper mappings as usual.

[pljones]

For 2, the mappings are part of the project - so, yes, if you want to save different mappings of the same base project, you need to save it multiple times. MuLab is modular - when you change a parameter, you're changing the settings of one or more modules at one or more levels of the modular hierarchy -- effectively creating a completely new synth from the original. In the same way you can go in and swap one module out for another or add and delete modules or change the modular routing, the settings are also part of the modular layout.

----

I'm not exactly clear what you're saying on 3 and 4.

[kmonkey]

For 2, the mappings are part of the project - so, yes, if you want to save different mappings of the same base project, you need to save it multiple times. MuLab is modular - when you change a parameter, you're changing the settings of one or more modules at one or more levels of the modular hierarchy -- effectively creating a completely new synth from the original. In the same way you can go in and swap one module out for another or add and delete modules or change the modular routing, the settings are also part of the modular layout.

----

I'm not exactly clear what you're saying on 3 and 4.

Ok, I understand the paradigm however it is a shortcoming a bit. I understand what you say. A piece of a Mux is modular and adding a module is going to change it. However... To say something is modular and it can not have preset as such is not a good excuse or argument.

Because other systems solved it. Say Reaktor for example is another modular environment and then there are other modular examples such as MaxMSP and so on. I am not getting their other features or lack of. Speaking strictly about a preset system.

In their case, you create some modular synth and call it a MuSynth. You can then showcase that synth's capabilities to the world by saving various parameters inside a snapshot system (list of snapshots or presets) that is obviously gonna work as long as those and only those modules are there. However, if you want to enrich or change them by adding another module that is also going to be saved as preset.

There is another aspect to this. Say someone created a synth in Mulab. Let us imagine MuSynth XXL for example. In case there's a snapshot preset system someone who created that synth with a preset system could show the world what the synth/creation/Mux is capable of.

Then there is another aspect. A 3rd party could create free or commercial banks for that specific synth keeping everyone happy. And making the community active. Even the banks which could include MuClips. I understand that the market for presets is oversaturated but still, people purchase banks and presets.

I suggest (and it is not demand) that MuLabv developer(s) rethink paradigm for the version 10.

Some kind of snapshot system for a synth should be done. And while we are at it "genetic" of a preset or snapshot morphing should be added to the list. Where you select one to five presets, add them to the "genetic" pool, and then press randomize and various presets are delivered based on parameters from the "genetic" pool. Look at Dune 3 for a nice example of how it is done.

For 3 and 4 - ok it is simple.

Load MuLab. In one of the rack slots (where you load FX) do this:

Insert Module (Mulab browser pop-ups). From the module list go to Audio Processors and then pick module "Amp Distortion". When it loads - how do you save this module as a preset?

[MuTools]

1. Is there a way for me to "automap" or auto-populate (I am unsure what word to use) the parameters of a synth in another DAW?

Example. I use MuLab as a plugin in Reaper. Say I load a preset called "Digital Organ". Which is a MuSynth actually. So in order to automate some of its parameters when I look in my DAW - I don't see any in most cases. I see MP1, MP2, MP3, and so on.

I get it. I learned from YouTube that I can click Show Modular Area. From there I can click on the synth parameter label and drag it into MP1, MP2, and so on.

Each project has a main module.
If you want to use MuLab Plugin as a typical DAW/composer then use a Composer module as main module.
If you want to use MuLab Plugin as a typical synth plugin then use a synth module as project main module.
If you want to use MuLab Plugin as a typical effect plugin then use an effect module as project main module.
More details here: https://www.mutools.com/info/M9/docs/mu ... oject.html

MuLab Plugin exposes the parameters of the main module to the host DAW.
So if you have a MUX Modular based synth as main module, it are that MUX's Meta-Parameters that are exposed to the host DAW.
More details on MUX Modular / Meta-Parameters here: https://www.mutools.com/info/M9/docs/mulab/mux.html

Note that a MUX Modular front panel, eg. MuSynth, can contain many parameters of the deeper modules that are inside that MUX Modular. These deeper parameters are not yet exposed to the host DAW, you need to map such deeper parameters to the main MUX meta-parameters.
Mapping a deeper parameter to a meta-parameter is as simple as dropping that deeper parameter on the meta-parameter knob. Also in MuSynth there are 3 meta-parameters sliders embedded in the front panel, in the "META" frame. You can also drag-drop other MuSynth front panel parameters onto those MuSynth meta-parameters to map them, and if that MuSynth is the project's main module that will also make them usable in the host DAW.

[MuTools]

btw MuLab desperately needs more videos

I fully agree!
It's on the Todo.

[MuTools]

In their case, you create some modular synth and call it a MuSynth. You can then showcase that synth's capabilities to the world by saving various parameters inside a snapshot system (list of snapshots or presets) that is obviously gonna work as long as those and only those modules are there.

There is another aspect to this. Say someone created a synth in Mulab. Let us imagine MuSynth XXL for example. In case there's a snapshot preset system someone who created that synth with a preset system could show the world what the synth/creation/Mux is capable of.

Then there is another aspect. A 3rd party could create free or commercial banks for that specific synth keeping everyone happy. And making the community active. Even the banks which could include MuClips. I understand that the market for presets is oversaturated but still, people purchase banks and presets.

I suggest (and it is not demand) that MuLabv developer(s) rethink paradigm for the version 10.

Such snapshot system already is on the wishlist.
Fully agreed it is something needed to complete the current MUX Modular preset system.
So it's not about rethinking the current MUX Modular preset system, it's a matter of extending it so that each MUX front panel can also have many snapshots.

[MuTools]

Insert Module (Mulab browser pop-ups). From the module list go to Audio Processors and then pick module "Amp Distortion". When it loads - how do you save this module as a preset?

In MuLab 9 not each and every module can save it's own presets, only the bigger modules support that.

[pljones]

Insert Module (Mulab browser pop-ups). From the module list go to Audio Processors and then pick module "Amp Distortion". When it loads - how do you save this module as a preset?

1. Insert a MUX Modular first
2. Switch to the modular view
3. Insert the Amp Distortion
4. Rewire the Audio In to the Amp Distortion audio input
5. Wire the Amp Distortion audio output to the Audio Out
6. Wire the MIDI In to the Amp Distortion MIDI in
7. Edit MP1 and map it to Amp Distortion Input Gain
8. Edit MP2 and map it to Amp Distortion Output Gain
9. Switch back to front panel view
10. Adjust the parameters to the values you want for your first preset
11. Save the preset to your User Library

Ideally a lot of this repetitive process could be simplified if there was a way to make "Amp Distortion" the main module of the MUX and have MuLab automatically wire the ins, outs and MPs to the main module. Once you've saved the first preset for your wrapped up Amp Distortion, though, you just twiddle the knobs on the front panel and save a new preset if you want to keep it specially.

(Obviously, any MUX Modular could have multiple component modules within it and a "main module" might not make any sense, so always doing this wouldn't make sense either - nor would saving presets for those components modules, like the Amp Distortion here, in my view. I'd prefer it if there was a clear distinction kept between loading a MUX Effect or Synth, with its settings, and the component modules, which would have their fixed defaults. Of course, any MUX Effect or Synth can be treated as a component in another MUX Modular creation -- and it would load its own "defaults" - i.e. the settings it was saved with - in exactly the same way as "loading" a built-in component module.)

[kmonkey]

Insert Module (Mulab browser pop-ups). From the module list go to Audio Processors and then pick module "Amp Distortion". When it loads - how do you save this module as a preset?

1. Insert a MUX Modular first
2. Switch to the modular view
3. Insert the Amp Distortion
4. Rewire the Audio In to the Amp Distortion audio input
5. Wire the Amp Distortion audio output to the Audio Out
6. Wire the MIDI In to the Amp Distortion MIDI in
7. Edit MP1 and map it to Amp Distortion Input Gain
8. Edit MP2 and map it to Amp Distortion Output Gain
9. Switch back to front panel view
10. Adjust the parameters to the values you want for your first preset
11. Save the preset to your User Library

Ideally a lot of this repetitive process could be simplified if there was a way to make "Amp Distortion" the main module of the MUX and have MuLab automatically wire the ins, outs and MPs to the main module. Once you've saved the first preset for your wrapped up Amp Distortion, though, you just twiddle the knobs on the front panel and save a new preset if you want to keep it specially.

(Obviously, any MUX Modular could have multiple component modules within it and a "main module" might not make any sense, so always doing this wouldn't make sense either - nor would saving presets for those components modules, like the Amp Distortion here, in my view. I'd prefer it if there was a clear distinction kept between loading a MUX Effect or Synth, with its settings, and the component modules, which would have their fixed defaults. Of course, any MUX Effect or Synth can be treated as a component in another MUX Modular creation -- and it would load its own "defaults" - i.e. the settings it was saved with - in exactly the same way as "loading" a built-in component module.)

Thank you!!!

[kmonkey]

Such snapshot system already is on the wishlist.
Fully agreed it is something needed to complete the current MUX Modular preset system.
So it's not about rethinking the current MUX Modular preset system, it's a matter of extending it so that each MUX front panel can also have many snapshots.

Awesome! One more thing. I tried to learn on your website but it's unresponsive on mobile phones. Ie it doesn't adapt to the (mobile) screen. You better focus on MuLab instead of course. Just saying. If you are sketching your tasks. Sometimes I only have time to learn when I poo in my poo room

But your website isn't adapting to the mobile or tablet screens.

I just realized MuLab is a one-man showtime - so it is virtually impossible to maintain a DAW and focus on public appearance - that much I can realize.

With everything in mind, I have only one thing to say about what you did in complete: Amazing.

[MuTools]

One more thing. I tried to learn on your website but it's unresponsive on mobile phones. Ie it doesn't adapt to the (mobile) screen.

Strange. MuTools.com works fine on my android phone & tablet. What mobile/tablet do you use, and which browser?

With everything in mind, I have only one thing to say about what you did in complete: Amazing.

Thank you!

Please help making MuLab more known by sharing many MuLab tracks, presets and videos and mentioning MuLab by MuTools.com!

[kmonkey]

One more thing. I tried to learn on your website but it's unresponsive on mobile phones. Ie it doesn't adapt to the (mobile) screen.
Strange. MuTools.com works fine on my android phone & tablet. What mobile/tablet do you use, and which browser?

Apologies for not being clearer. Your website works fine. I said I tried to learn hence I visited your Doc area. That area is looking awful on mobile screens. I checked on my phone, and my sister's phone, and used Firefox tools to confirm.

Arguably, the most useful area to learn from isn't scaling fonts at all.

https://www.mutools.com/info/M9/docs/index.html

In order for me to actually read anything there (while on the phone) I need to pinch in and then as I read I need to move content with my fingers from left to right, unlike everywhere else on any page I visit whatsoever - where pages scale their fonts based on the screen. For example, your main page looks fine.

Docs are incredibly small. See the screenshot taken in Firefox mobile screen emu - which reflects what I see on my phone or any phone I tried :



If you go to any online test tool (like page speed) you'll see that the accessibility score for any page in your Doc area is below average.

[kmonkey]

Btw it is no problem to spread the word because the tool (MuLab) is quite amazing.

I somehow stumped on creations from Mister FSM77 in your google drive. And I am like...no way this is for real

[MuTools]

Apologies for not being clearer. Your website works fine. I said I tried to learn hence I visited your Doc area. That area is looking awful on mobile screens.

Ah, ok, it's about the docs.
Indeed they're not yet responsive to mobile/tablet context.
MuLab itself also doesn't work on mobiles/tablets yet, so you need a pc anyway.