About "Map MIDI Controller"

[MuTools]

Well, after all that, the original issue was indeed a shortcut.
I've used my Akai Mini Plus transport controls to control MuLab, it uses CC115-CC119.

Now we're talking.
Thx for posting this.

Though the issue I encountered after that with the new install still stands...

It still stands in your head.

Whether you use Module/Map or R-click/Map shouldn't matter.

About closed-mindedness...

I using the Module/Map method and you select the parameter, it should move. It isn't, until you assign a new Map on a different parameter of that module. This, I can repeat, over and over. but if you think that's ok... I'll say no more!

You should simply right-click the parm and use its Map MIDI Controller.
How many times did i already say this? 6, 7, 8?

I'm not saying this MIDI CC map topic is an easy topic, and i understand there can be confusion, that's why i've given this topic a lot of attention. I'll keep on improving MuLab and the docs so to make everything as easy as possible.

But now i'm going to leave this topic as it is my responsability towards other users to carefully spend my time. I'm convinced i've given you more than reasonable attention.
Hope you now see the light in how MIDI CC mapping works.

[MuTools]

So what do you do when a VST doesn't have that R-click menu on knobs?

Give the plugin parm a little tweak in the plugin editor, that will map this plugin parm onto the focused parm at the top of the plugin editor, in MuLab's plugin top control section. There you can right-click the parm and do Map MIDI CC.

As explained on https://www.mutools.com/info/M10/docs/m ... ugins.html

[sl23]

...

[sl23]

...

[sl23]

...

[MuTools]

Now who's being insulting?
Now who's Closed-minded?
Now who's not listening?
Look I'm not getting shitty...

Such a bad post

In contradiction with the general vibe on this forum.

[sl23]

...

[bibz1st]

Cmon guys,
I think it should end there

[sl23]

Though it was a mistake on my part, due to confusing the two functions being the same, I think the context menu option should be renamed to avoid this issue in future.

[MuTools]

Thanks sl23 for your message.
This was an exhausting and frustrating topic.
I hope this will never ever happen again.

Thanks for your constructive point that it can be confusing that parameter->Map MIDI Controller and module->Map MIDI Controller are functions with the same name but with different behavior and results. For that reason, in the next MuLab update the module's Map MIDI Controller function will be removed, and only the module's Edit MIDI Controller Map will remain.
That's an UX optimization that avoids the confusion as well as some redundancy because the module's Edit MIDI Controller Map also covers the removed module's Map MIDI Controller functionality.

Glad we can close this topic with on a constructive and positive note.

[sl23]

Thanks Jo! Again, sorry for the mix up!

I have just been trying it out again, but I'm again having trouble, sorry. This time I am using the Right click Map MIDI Controller.
I have previously been trying the other issue out and inadvertently saved several mappings to a project, but I am unable to find out where it has been saved. The Cog Menu Edit Mapping doesn't show it. So I went to the EQ Killer Mux that is a part of the main MuX, and it's not there either!

How do I locate it?
It doesn't appear in the Project mappings or anywhere in the Mux or it's descendants.

Sylenth has an option to "MIDI Forget", could that be added to MuLab? Call it, MIDI Unlearn, MIDI forget, Remove Mapping, I think the last one is best.

Also, Could we have the "Edit MIDI Controller Map" menu option add to the Right Click menu of a front panel object please. Ideally remove it from the context menu and just have it alongside "Map MIDI Controller" in the Right Click menu.

EDIT: I managed to unmap by remapping and selecting NONE for each parameter.

[sl23]

Also, if you remove the Map MIDI Controller from the Cog Menu, how will you access it if you can't R-click a VST know to Map it?
Several VST's don't have this option built in, but may still allow Mapping. The only way to Map a controller then, would be using the Cog Menu option. Unless there's another way?

EDIT: Ah ok, I see it can be done via the Title bar if it isn't collapsed. Another good reason to add that knob to the collapsed title bar.

[ortseam]

Hello!

I put my naive question here not to create a special topic.

It's about an interaction between MIDI messages that travel "normally" through the blue wires and the ones that are received by modules via MIDI-mapping table. If I understand it right, when some given kind of message (e.g. Modulation CC, channel 2) is mapped to some parameter of an instrument inside a MUX module, this MUX module stops receiving this kind of messages through it's blue Event input. Right?

Is there a way to get them in blue Event input "in parallel" with MIDI-mapping table assignment?

Thank you!

[MuTools]

It's about an interaction between MIDI messages that travel "normally" through the blue wires and the ones that are received by modules via MIDI-mapping table. If I understand it right, when some given kind of message (e.g. Modulation CC, channel 2) is mapped to some parameter of an instrument inside a MUX module, this MUX module stops receiving this kind of messages through it's blue Event input. Right?

Indeed.

Is there a way to get them in blue Event input "in parallel" with MIDI-mapping table assignment?

Yes: The MIDI mapping is only applied on events received on the first input jack, not on events received on other input jacks and so you can take advantage of that, for example by creating an receiving point just before that MUX, then inside the MUX create an extra event input, and then outisde the MUX connect that receiving point to both event inputs of that MUX. Attached a draft example project that demonstrates it: The MIDI CC clip from the composer causes both MIDI mapping as well as option to further process it. Hope this helps.

[ortseam]

Yes: The MIDI mapping is only applied on events received on the first input jack, not on events received on other input jacks and so you can take advantage of that, for example by creating an receiving point just before that MUX, then inside the MUX create an extra event input, and then outisde the MUX connect that receiving point to both event inputs of that MUX. Attached a draft example project that demonstrates it: The MIDI CC clip from the composer causes both MIDI mapping as well as option to further process it. Hope this helps.

Yes! That's what I was looking for. Thanks a lot. Problem solved!