On the first, it might be looking at a MIDI mapping utility such as MidiFire, Bome (or on iOS Midiflow, but that's presumably no use for Max purposes). There may be something you can use in this thread; Artiphon's single-gesture presets look helpful, though I haven't dug into them.
Freshdesk forums are fussy about browsers. The penny only dropped that the reason the ROLI forums had been stripping out all my whitespace was that I was using the normally superpowered iCab. Safari respects whitespace and gives you all kinds of formatting options that aren't there at all in other browsers, but I haven't looked further. If you have a formatting bar in the message window it's an encouraging sign.
If you would like to preview the Max for Live Utility before we release it, you can download it here:
Artiphon Orba Max for Live Utility
Let's use the max for live utility to better illustrate the problem.
The mappable sources are:
If I'm in Drum Mode, those first five do nothing.
If I'm in Bass or Chord Mode, there's no Vibrato.
The full set of parameters is only available in Lead Mode.
Here's the thing. I don't know that the user is in Lead Mode.
Reasons the user might not be in Lead Mode:
Let's focus on that last one for a moment.
If they just turned on their Orba, it defaults to Drum Mode, where five degrees of expression are effectively broken in this patch.
Radiate, Tilt, Spin, Press, and Vibrato. All disabled.
What you want, when you open a patch, is the other thing.
(Y'know. Unfettered access to sensor data.)
(...for the patch to work.)
To some degree, this does give me my working orders. Just require that the user be in Lead Mode.
...and if I care about tracking which buttons are pressed, I need insist that they remain in C Major. Or provide a "press every note so I know which scale you're using" mechanism.
...until a new set of presets change these requirements.
Then, evaluate whether or not I need to rewrite everything.
Worth reiterating, I don't think you're going to be able to add "Slide" to that max for live device, through this approach. You're basically dancing on the edge of a level of complexity which requires bidirectional communication to let apps manually enable or disable these features as needed.
We are planning to keep the gestures and their mapping as consistent as possible while adding new features as they come in.
The Slide gesture will be added as a separate gesture with its own default midi cc. We did not get to do that yet. The cc's are planned as midi cc114 (slide distance) and midi cc115 (slide velocity)- but since we have not released that yet it may have to change for unexpected reasons.
Your device is producing error messages in the max console. The cause is in your [press] subpatch. Bottom-right corner.
(that inlet is for limiting which ports and channels [notein] listens to. which is a thing in the max runtime, but your MIDI stream is already filtered down by Live itself, so whatever. honestly, I'm a little surprised that max for live even reads that inlet. anyway, you're feeding in raw MIDI bytes. it's not expecting those.)
Aaron, try this new version for the Orba Max for Live device, if you like: