Lokua

Just test driving Max 8's new midi mapping feature, and am running into a strange issue. I have two MIDI Fighter Twister controllers, and when I map controls with one of them, everythings works fine. However, when I map any control with the other controller, which is identical besides the channel it transmits on, the 

 view, and the UI object (tried a bunch) only jump from 0 to 127 when the physical controller crosses 63 (even though ctlin indeed shows a normal stream of controller values).

midimap.gif

Just test driving Max 8's new midi mapping feature, and am running into a strange issue. I have two MIDI Fighter Twister controllers, and when I map controls with one of them, everythings works fine. However, when I map any control with the other controller, which is identical besides the channel it transmits on, the Exponent and Steps column are both grayed out in the Mappings view, and the UI object (tried a bunch) only jump from 0 to 127 when the physical controller crosses 63 (even though ctlin indeed shows a normal stream of controller values).

Just test driving Max 8's new midi mapping feature, and am running into a strange issue. I have two MIDI Fighter Twister controllers, and wh

max-8-midi-mapping

Probably should have made description simpler.

Why is my control knob being perceived as a toggle when mapped?

Am I the only one experiencing this?

Probably should have made description simpler. 

What causes the Exponent and Steps columns to be enabled/disabled in the Mappings sidebar?

I'm also not able to find how to enable the step parameter.

I tryed to change the step and exponent in the inspector but without success

Is the key mapping feature only experimental for now ?

Is there any answer to this since 2018 ?
I'm also not able to find how to enable the step parameter.
I tryed to change the step and exponent in the inspector but without success
Is the key mapping feature only experimental for now ?


Max 8 MIDI Mapping