MuLab 9.0.59 App + Plugin

[MuTools]

Bug: if you open or close the browser while composer modular area is open, the composer modular area closes itself.

Will be fixed in M9.0.18. Thanks!

[humanboeing]

Audio limiter graph vs Level compressor graph:
Not much of a bug report but a question, audio limiter's graph changes when in/out value is changed but compressors's graph does not when its parameters pre/post gain are moved around. Shouldn't there be a consistency given that a limiter is pretty much a compressor with big ratio?

[humanboeing]

Also both of these modules feature audio level meters on sides which more or less imply that the graph will show information according to them.

[humanboeing]

Nevermind, I misunderstood how the graphs work. The limiter's graph is split into x=input and y=output while the compressor's graph is not, hence the difference.

[HarmonicD]

automation just doesn't work properly compare to mux 8... (using reaper as host)
-unlike in mulab 9, when I use mux 8, Reaper immediately open new automation envelops in Latch automation mode

take a look:
mulab vs mux

same thing in 9.0.17

[MuTools]

Which option do i have to tick in Reaper to auto create automation envelope lanes when wiggling a plug parameter as Reaper doesn't do that here with MUX 8 neither.

And when i add an automation lane for a M9 main module parameter and select Latch mode and arm it then sliding the M9 main module parameter does write the Reaper automation lane, so the connection certainly is there.

Puzzled.

Please elaborate.

[HarmonicD]

Which option do i have to tick in Reaper to auto create automation envelope lanes when wiggling a plug parameter as Reaper doesn't do that here with MUX 8 neither.

I enable the latch mode and then when I move a parameter it creates an envelope.

And when i add an automation lane for a M9 main module parameter and select Latch mode and arm it then sliding the M9 main module parameter does write the Reaper automation lane, so the connection certainly is there.

from the main parent module it doesn't write automation or add automation envelopes for me
but it does write and add automation envelopes from a child module's controllers.

[MuTools]

Which option do i have to tick in Reaper to auto create automation envelope lanes when wiggling a plug parameter as Reaper doesn't do that here with MUX 8 neither.

I enable the latch mode and then when I move a parameter it creates an envelope.

Thx, works fine indeed, also with M9.0.17.

from the main parent module it doesn't write automation or add automation envelopes for me
but it does write and add automation envelopes from a child module's controllers.

Only the parameters of the M9 project's Main Module are communicated to the host DAW. If necessary you can control which module is the main module by right-clicking that module in the project modular area and do "Set As Main Module". In the example you gave that's the Basic Synth and so only the Basic Synth meta-parameters are communicated to the host DAW. In fact that's the same behavior as in MUX 8 Plugin but the difference is that you didn't see the project modular area in MUX 8 Plugin.

So it seems it works as expected now with M9.0.17 in this regard.

[HarmonicD]

I don't want to set any child module as main module, I want the main parent window to be the main module (it has controllers too)

[MuTools]

I'm sorry but that's not how it works, and that cannot be changed as that's an essential architectural aspect. Please think it thru a bit more, in fact it's quite logical.

First of all: Also in MUX 8 there was only 1 module of which the parameters are communicated to the host. Also in MUX 8 it was not possible to directly automate deeper module parameters from within the host unless you had mapped them to one of the meta parameters of the implicit M8 main module. In MUX 8 that one main module was decided for you, it was the MUX module you saw in front.

Now in M9 things work basically the same but the difference is that you now have control over that Project Main Module. It's thanks to the Main Module that MuLab 9 is so modular and flexible and that it can be a synth and/or an effect and/or a composer! Because the user can choose the type of Main Module. That creates great flexibility. And it is what merges MuLab and MUX together into 1 plugin.

I'm confident you will get used to this concept rather quickly as it only creates little overhead on the musical workflow. In many cases the main module already is defined by default or by template and you can focus on the musical flow. Eg. if you always use M9 as a synth plugin create a template for it.

Conclusion: Just keep in mind that it is the project main module (not the project MUX itself) that is connected to the host DAW. (Just like in MUX 8 )

[HarmonicD]

Ok, I don't think that I will have problem to get used to it with a template..
It's just that intuitively I tried to create automation using the project modular area. lets hope that this won't confuse newcomers

[MuTools]

I understand. Thanks for your feedback

[MightyMouse]

9.0.17 so far so good!
I have feature requests and I know this is not the right time,

So just a small one , I wish there was a dedicated preset system for every module in every module's window.

so for example, if I load musynth, I want to load and save presets for musynth from its own window.

what I mean is that currently the "presets" are more like "modules" and I want to have presets per module. I hope that you can understand this

Thanks for everything!!!

[MuTools]

Yes i understand what you mean and i agree that such feature would surely make sense. It's on the wishlist.

[humanboeing]

I wish there was a dedicated preset system for every module in every module's window.

I think this was already requested, but if not I'd like to add a tagging system so the user could tag modules, for example: "aggressive", "smooth", "soft", "dark", "analog" etc. and then browse modules by tags. Especially useful once the library of modules becomes significant and it can get quite messy.