MuLab 9.0.59 App + Plugin

[xbitz]

Indeed a Parameter Event Generator can't see outside its parent.
I understand you want to make reusable blocks and in that contaxt, as a draft thought, i would convert it to MIDI CC as that's module independent, and only convert it back to a concrete module parameter in the target context.

it can see out, so the modulation still working just its target can't be changed anymore(so the target list generator can't see out ...), this is why I've reported it, it's in-between the working and non-working states , btw. I think the CC one isn't an audio-rate one

[MuTools]

it can see out, so the modulation still working just its target can't be changed anymore(so the target list generator can't see out ...), this is why I've reported it, it's in-between the working and non-working states

I'm sorry but i don't understand what you mean.
Please explain in more detail, step by step.

btw. I think the CC one isn't an audio-rate one

Both MIDI CC and Parameter events are events, and not suited for audio rate modulation, only audio (red signals) and modulation (green signals) are suited for audio rate.
So maybe better that you make your reusable MUX blocks output modulation signal and when you insert them in a concrete patch then hook up a Parm Event Gen into it and connect your reusable block green mod output to the green mod in of the Parm Event Gen, which then can be setup for a concrete target parm.

[humanboeing]

A somewhat related question, is there a reason why automation lanes are considered events instead of modulation?

[xbitz]

it can see out, so the modulation still working just its target can't be changed anymore(so the target list generator can't see out ...), this is why I've reported it, it's in-between the working and non-working states

I'm sorry but i don't understand what you mean.
Please explain in more detail, step by step.

^^^ voilà

wanted to wrap it, then...

[MuTools]

Cfr earlier post: A Parm Event Gen can only see the parameters of the module it is connected to. So if you wrap it into a MUX and the Parm Event Gen is only connected to the event output module of that MUX wrapper, then you indeed don't see any parameters as an event output module has no parameters.

[robert_p]

it can see out, so the modulation still working just its target can't be changed anymore(so the target list generator can't see out ...), this is why I've reported it, it's in-between the working and non-working states , btw. I think the CC one isn't an audio-rate one

This is true, you can see it working in my DR32MS Mux I shared some time ago:
There is a parameter event generator linked to 32 Multi Sample players that controls the Velocity Sensitivity:

Parameter Generator.jpg

[MuTools]

This is true, you can see it working in my DR32MS Mux I shared some time ago:
There is a parameter event generator linked to 32 Multi Sample players that controls the Velocity Sensitivity

I'm not sure if i can follow, so let me doublecheck: Am i missing a bug report here?

[robert_p]

I'm not sure if i can follow, so let me doublecheck: Am i missing a bug report here?

I don't know if it's a bug - it just works (and theoretically it shouldn't work:))

[MuTools]

MuLab App 9.0.57 is available in https://www.mutools.com/mulab/app/latest-binary

MuLab Plugin 9.0.57 is available in https://www.mutools.com/mulab/plugin/latest-binary

This update fixes a recent new bug in the plugin system that caused an error alert upon quit when using multiple instances of the same plugin.

This M9.0.57 update is for Windows. The respective Mac update will follow soonish.

Also the M9.0.57 for Mac versions are available now on those "Latest Binary" pages.

[MuTools]

I don't know if it's a bug - it just works (and theoretically it shouldn't work:))

It's indeed a kind of bug and so it works by accident.
Please note that a Parm Event Gen should always use a real concrete parameter.
If not, like in the DR32 patch, it's an unsupported use case which could stop working in future updates.

[MuTools]

PS: What is ok to do is to use a Parm Event Gen and connect it to a module, then in the Parm Event Gen select the target parm, and then connect the Parm Event Gen to multiple modules of the very same kind so that the outputted parameter events are targetting all the same parameter.

[robert_p]

It's indeed a kind of bug and so it works by accident.

This reminds me of a "Pultec EQ low end trick" story, where the user guide states "not to boost and cut the frequency at the same time". So, obviously it was the first thing the curious audio engineers did and they quickly discovered that it sound really good:)) Similarly, "All Buttons In unique sound" was discovered in "1176 FET Compressor". So, MuLabs "Event Parameter Generator" trick is just another "secret weapon" we can use:))

[robert_p]

A somewhat related question, is there a reason why automation lanes are considered events instead of modulation?

Because we can place some "MIDI CC Messages" there, and then they can be monitored with the "Event Monitor"?

[humanboeing]

A somewhat related question, is there a reason why automation lanes are considered events instead of modulation?

Because we can place some "MIDI CC Messages" there, and then they can be monitored with the "Event Monitor"?

I'm stupid

[FabBad]

Jo, the problem with drag an element outside of its slot still there.
But not when draggin on its own slot but when drag to inter-slot or outside in rack. This is not new btw.