I’ll preface by saying that I don’t know whether this is on the Ableton side or Sensel side that’s causing the interaction, but I’m hoping someone has insight or a solution for this. I’m trying to set up finer control in Ableton using the 14-bit precision setting in the XYZ MIDI Pad. I substituted a slider from the Music Production preset with the pad to do this. As you can see, only the X dimension is enabled, at CC20.
When routed into Ableton, I see that it’s putting signal through Channel 1 at CC20 and CC52, as expected, but when I try to map the incoming data in Ableton, it registers an input at CC32.
Ableton then automatically uses Absolute mode, which seems to follow CC52, the final 7 bits of the control signal, and when forced to Absolute 14bit, the signal controls nothing.
Is there a known method avoid this error and supply 14-bit midi data? I’m willing to test Max4Live, if that’s necessary.