Assigning a CC to a control disables messages from onController

[ulrik]

@Christoph-Hart said in Assigning a CC to a control disables messages from onController:

Also why would you want the CC7 to still update the volume when the user chose to control something else with it?

I have a setup where the user can chose to control several functions with whatever cc he chose
for instance, control modulation and filter with the modWheel.
I made it so the user can set the amount of influence for each parameter, I think it can be handy in some circumstances

[d.healey]

@ulrik

I have a setup where the user can chose to control several functions with whatever cc he chose

You can do that through MIDI learn (assuming you have on screen controls for those parameters).

[ulrik]

@d-healey 🤭 Oh, of course you're right, I'm blushing

[Casey Kolb]

@Christoph-Hart said in Assigning a CC to a control disables messages from onController:

Yes, but please imagine the alternative option where people have to remap all MIDI CCs when they load a DAW project

I hear you, but wouldn't it make sense to store a handful of global CCs in an external file which act as the default for every instance of the plugin? And then you can also have MIDI CC saved per preset, but they wouldn't disable the global controls. A great number of my test users are getting annoyed with the CCs saved per preset because they have to remap literally every preset to match their setup

I can make the external CC settings file work, but I just don't want the MIDI Learn to disable the onController callback for that CC.

Also why would you want the CC7 to still update the volume when the user chose to control something else with it?

Let me provide another example: I have CC1 automatically assigned to the dynamics knob of my plugin, but there are plenty of cases where a user would want to keep that setting globally, but also add more controls to CC1 in a preset for the convenience of a one-knob mod wheel tweak (I do this all the time, and so do lots of other producers). The instant a user MIDI Learns CC1 for any other control, it will disable the global CC1 control for the dynamics knob, even if they wanted to keep that assignment. They might not even realize the dynamics knob CC assignment was disabled, which is why from a design perspective it seems hairy.

Is there a way to keep the MIDI Learn per preset, but prevent it from disabling global CCs saved in an external file? That's really all I'm looking for.

[ustk]

@Lunacy-Audio so why don't you make your own system, global CC + custom midi learn. You lose the simplicity of using the native midi learn but you can make exactly what you want. This implies you use only panels for sliders to make the midi learn from a right-click (or any mouse/modifier), or a unique panel that lists all parameters where you set the global and the custom CC in one place.

[Casey Kolb]

@ustk Because reformatting 1000 knobs and sliders as panels would take weeks

Tweaking this in the C++ would probably take 30 minutes, but I just can't figure out where it is.

[Casey Kolb]

@ustk As suspected, it was a single if statement preventing this

Works great if you just remove the if (!consumed) from line 726 https://github.com/christophhart/HISE/blob/master/hi_core/hi_core/MainControllerHelpers.cpp#L726

[d.healey]

@Lunacy-Audio What does editing that line do?

[ustk]

@Lunacy-Audio Same question as Dave, seems strange...

[Casey Kolb]

@ustk @d-healey As mentioned previously in the thread, it makes it so that MIDI Learning a new control does not disable that CC from the onController callback, so you can set global CC controls and save them in a file, while keeping the MIDI Learn functionality without any conflicts between the two.

[d.healey]

@Lunacy-Audio Oh that's interesting, will one have priority over the other or will both be active at the same time? Have you made a pull request?

[Casey Kolb]

@d-healey Both will be active at the same time. I've run a few tests in the exported plugin and it seems to work without any issues. It's great for assigning say CC1 by default to a knob on your interface, but also allowing the user to assign CC1 to other knobs without overwriting the default.

I haven't made a pull request because it seems that some people don't want this behavior. Easy enough to tweak if you want it though!