Hi Again,
there some functions avavibale via MIDI mapping like the autopilot.
The different stages seem to be devided into midi values.
I would like to map a button for the stages OFF and Forward (with working LED Feedback)
I already have a nice button wich i can format as a toggle, with values and colors for On and Off
I use Control Change (CC) with a range between 0 and 127.
I cant find a documentation for the midi values for the different stages and do not get behind it.
(Even when i try to get the best out of my math skills)
Anybody knows the correct ranges?
THX
Wanted: Autopilot Stages MIDI controller values
Re: Wanted: Autopilot Stages MIDI controller values
It's best to use Midi Notes for this.
If you use CCs, the 0...127 will be mapped along the four states of the Autopilot control.
So 0..31 will be backward, 32...63 will be off, 64...95 will be forward and 96..127 will be random.
If you use Midi Notes, you can assign separate shortcuts for each state.
If you use CCs, the 0...127 will be mapped along the four states of the Autopilot control.
So 0..31 will be backward, 32...63 will be off, 64...95 will be forward and 96..127 will be random.
If you use Midi Notes, you can assign separate shortcuts for each state.
Re: Wanted: Autopilot Stages MIDI controller values
THX for the info Joris.
Also thx for the hint with the midi notes. I already got that one cause you answered a similar questiion for sb who wanted to map the beat slicer. I try the range first cause it will save some buttons and i might need them for other nice stuff to map.
That is quite logic and i feel sorry i didn't catch it myselfSo 0..31 will be backward, 32...63 will be off, 64...95 will be forward and 96..127 will be random.

Also thx for the hint with the midi notes. I already got that one cause you answered a similar questiion for sb who wanted to map the beat slicer. I try the range first cause it will save some buttons and i might need them for other nice stuff to map.
Re: Wanted: Autopilot Stages MIDI controller values
Hi Joris,If you use Midi Notes, you can assign separate shortcuts for each state.
i stopped using a single button & assigned them to Notes as you mentioned.
Started with the layer focused mapping for the maschine mkI and it worked perfect using two buttons.
(Off & >>)
After checking in and outputs for every layer i started mapping the AP functions to the Deck focused mapping.
The Deck focused mapping is working fine. Im using 3 buttons per layer in here (<< | Off | >>)
But since i mapped it into the Deck focused mapping, the layer focused mapping does not recive
the outputs anymore. (while the inputs are working fine)
The corresponding buttons on the deck focused controller recive the correct output when triggering the buttons on the layer focused controller.
Can u help me again with this one?
THX HI5
Re: Wanted: Autopilot Stages MIDI controller values
I think you're already in contact with Bonne about this one, right?
Re: Wanted: Autopilot Stages MIDI controller values
Nope its not a Show stopper so i decided to post it to the Forums. Already stole a lot of Bonnes time.
Re: Wanted: Autopilot Stages MIDI controller values
Ran into the Same trouble with the transport section by the way.
The layer focused Outputs stop working after Mapping the Same functions deck focused.
The layer focused Outputs stop working after Mapping the Same functions deck focused.
Re: Wanted: Autopilot Stages MIDI controller values
I'm sorry. Since you've already spent so much time with Bonne on a related or at least a similar issue, I'm not sure what I can bring to the table.
If you want to have this issue addressed, I suggest to contact Bonne again. At this point she knows more about your situation than anyone.
If you want to have this issue addressed, I suggest to contact Bonne again. At this point she knows more about your situation than anyone.
Re: Wanted: Autopilot Stages MIDI controller values
Youre right its a related issue.
I contacted Bonne again.
I contacted Bonne again.