I have a layout with many knobs, some visible, and some invisible, and used as supercontrols for sets of 'radio' buttons. I use them to set values in my custom device, and to receive values from it when I change patches. These have been working fine until recently, when some of them (not all) have stopped responding to MIDI messages.
I have only noticed this problem since updating to 1.6.2, and I don't think it's a problem with my layout because I also see it with a new one with only one knob.
My test layout has a single knob, with the following settings:
Subtype: normal
Display min->max: 0-127
#ticks: 128
MIDI ch-CC: 1-3
Msg type: Control Change
MIDI min-max: 0-127
Default value: 64
This is a default knob with only the MIDI channel and CC changed to match the message my device is sending.
When I send B0 03 03 (CC, ch 1, CC 3, value 3) to MD from my device, the knob responds as expected, and is set to 3.
When I change it to limit the range of MIDI values and #ticks etc. it stops working. These are the new settings:
Subtype: normal
Display min->max: 1-8
#ticks: 8
MIDI ch-CC: 1-3
Msg type: Control Change
MIDI min-max: 1-8
Default value: 1
Now when I send B0 03 03 (which I confirm in the log, BTW), the knob always goes to 1, not 3.
Going back to my original large layout and testing several of these kinds of controls, I find that some work and some don't.
I'm running 1.6.2 on an original iPad, which sometimes struggles for memory when running MD.
Have I misunderstood something basic or is this a new problem?
Sorry that was long-winded...