DBM implementation question: user controls and events

[minortom]

Moss, off the wall code question: when mapping user controls on Maschine Jam, how are you preventing slider touch from registering before slider position? I have a HarwdareButton matched to slider touch MIDI data that registers first (this part makes sense). I've tried temporarily setting its pressed/released action matchers to a nonsensical matcher, but then Bitwig simply maps the touch event as raw MIDI CC, as if it's getting passed straight through to Bitwig.

Couldn't tell easily from the code, thought I'd ask.

[moss]

Moss, off the wall code question: when mapping user controls on Maschine Jam, how are you preventing slider touch from registering before slider position? I have a HarwdareButton matched to slider touch MIDI data that registers first (this part makes sense). I've tried temporarily setting its pressed/released action matchers to a nonsensical matcher, but then Bitwig simply maps the touch event as raw MIDI CC, as if it's getting passed straight through to Bitwig.

Couldn't tell easily from the code, thought I'd ask.

For user parameters there is no way to fix this. Bitwig maps whatever it receives first.
I already requested an option to forbid certain CC from mapping but that is still not available.

[minortom]

Thanks.

Ah, I think I see what you're doing: you are using a HardwareSlider with matchers set on its beginTouch/endTouch actions, and that's why your user control mapping works correctly. I was using a separate HardwareButton to represent the touch control, and mistakenly concluded you were too.

[minortom]

Also, have you noticed that UserControlBank parameters behave unlike the others? Namely, .value().get() does not return the actual value and value observer never gets called, even when the control is properly mapped and the value is clearly changing. Wonder if that's just how UserControlBank is or I'm doing something wrong.

[moss]

Also, have you noticed that UserControlBank parameters behave unlike the others? Namely, .value().get() does not return the actual value and value observer never gets called, even when the control is properly mapped and the value is clearly changing. Wonder if that's just how UserControlBank is or I'm doing something wrong.

Yes, user parameters have some issues, e.g. you cannot reset them to default values. Thing is that they are a bit outdated and they might be replaced with something completely different in the future.