For the MIDI implementation I think it need be no more complicated than this:
| CC:113 Transition | description | CC Value | detail | |
|---|---|---|---|---|
| Change Part (Aeros Only) | 101-106 | Value 101-106: Begin the transition to part (part # = value # minus 100 , so value 102 is part 2) according to the Change Part setting (Immediately/End of Measure/End of Loop). If the part doesn’t exist in the song, the Aeros will ignore the command. This allows you to send a single on-press command for changing parts. This also allows you to switch the part on the Aeros without switching parts on the BeatBuddy (which ignores values 101-106) when they are on the same channel and being controlled by a MIDI controller. This command can start the Aeros from a stopped state. | 4.1.2 | |
| — | — | — | — | — |
| Oneshot Part (Aeros Only) | 111-116 | Value 111-116: Transition to part (part # = value # minus 110 , so value 112 is part 2) IMMEDIATLY and START if not in a running state, with STOP at end of part already triggered. If the part doesn’t exist in the song, the Aeros will ignore the command. This allows you to send a single on-press command to one shot a part. This command will start the Aeros from a stopped state and stop the Aeros from a running state (at the end of the selected part). | 5.x…. | |
| — | — | — | — | — |
The implementation of “one-shot” only really makes sense with regard to MIDI.
With the limited number of buttons on the Aeros, there would be no alternative to “tap-dancing” to achieve a one-shot no matter how you implement it with the Aeros buttons.
Unless you dedicate one physical button to being either a ‘one-shot button’ or ‘make this part a one-shot button’ a user would have to tap-dance or bend down to touch the unit to get a ‘one-shot’ capability.