About "Map MIDI Controller"

[sl23]

...

[sl23]

...

[MuTools]

I've just reviewed both gif's and in both the VST/Mux are both focused. You can see as the title text isn't dimmed out.

Attention: GUI focus is not the same as MIDI focus.
Read:
https://www.mutools.com/info/M10/docs/m ... llers.html
https://www.mutools.com/info/M10/docs/m ... board.html
https://www.mutools.com/info/M10/docs/m ... -info.html

[sl23]

...

[sl23]

...

[sl23]

...

[sl23]

...

[tiger001]

maybe those MIDI cc's are already assigned?
e.g. in the note action map ?
-these MIDI cc (120-127) are special ones that are working globally

[MuTools]

What ever I click on has MIDI focus, simple as that.

Wrong.
Carefully read the doc pages i linked to.

The easiest way to map a MIDI CC to a MUX module parameter is to right-click the parameter knob -> "Map MIDI Controller". This will open a dialog panel and when you tweak your MIDI controller it will automatically be recognized as the source.

Exactly what I've tried on two separate systems, doesn't work.

It surely is not what you did on your 2nd video.
You did not right-click a parameter knob to setup the MIDI controller.
Again, carefully read: https://www.mutools.com/info/M10/docs/m ... llers.html

[sl23]

...

[MuTools]

So when I click on the cog and select Map MIDI Controller, it's not the same as R-clicking a parameter?

Indeed a parameter is not the same as a module and a right-click on a parameter knob/slider is not the same as a left-click on a module's context menu.
As explained on https://www.mutools.com/info/M10/docs/m ... llers.html

So, without any indication, how are we supposed to "know" what has MIDI focus if there are no indicators for it?

In the next update hovering the Focused Module Keyboard will show the name of the module that currently has MIDI input focus.

The problem still remains. Because when I add a second parameter straight after the first, all of a sudden they both now work. So how does the mapping of the first parameter suddenly shift focus? Makes no sense.

Maybe the first time you used the module's context menu. That does not shift MIDI focus.
And the 2nd time maybe you used the parameter's context menu to map a CC, that does shift MIDI focus.

If you wanna get really pedantic about it,

Sounds insulting to me
I'm only trying to analyse what you're talking about.
You talked about bugs. We're 3 pages far and i still don't see any bugs.
However i can see your confusion about how MIDI mapping works and that's what i'm trying to meticulously sort out now.

Also tried moving any parameter before proceeding with Mapping. Which is what you are saying I didn't do and therefore is why it doesn't work.

Nope, i didn't say that.
I said you used the modules context menu to add a CC map instead of right-click a parameter to add a CC map.
Those are 2 different methods with different behavior, as explained on this doc page: https://www.mutools.com/info/M10/docs/m ... llers.html

What does this even mean:

When you use the module's context menu -> Map MIDI Controller or Edit MIDI Controller Map, then you're effectively editing that specific module's MIDI controller map, no automatic re-leveling then.

When using right-click a parm -> Map MIDI Controller then MuLab will automatically select the most relevant target module to store the MIDI mapping. That's the recommended way, as explained on that doc page.

When using a modules context menu Map MIDI Controller then the mapping will be stored in that specific module's MIDI map.

[sl23]

...

[MuTools]

That's makes no sense as to why you would even want that.

Setting up a MIDI CC into a specific module definitely is a needed function.
For example to setup automation, or modulation using a Parameter Event Generator, or events coming from a VST/CLAP plugin, or...
Many possible scenarios.

Whether you use the Cog to map or Map direct, the result should be the same

I disagree.

It appears then, that this is the issue, which you have fervently denied there being one. And the reason for my frustration. I wasn't insulting you, I was frustrated with you, as sometimes, with respect, you're a bit closed-minded.

Thank you.

Did it ever passed your mind to doubt your own view?
It's interesting to regularly do that.
I do that regularly.
I should do it even more regularly.

I expect the behaviour to be, click a module, give it MIDI focus, so I can use a specific hardware device to then map or control it.

That's what the right-click parameter -> Map MIDI Controller does.
As i'm already saying almost 4 pages long.

[sl23]

...

[sl23]

...