Support and discussion for all of Akai’s modern standalone MPCs including the MPC X / X SE, MPC Live 1, 2 & 3, MPC One / One+, MPC Key 37/61.
By djst Sat Nov 06, 2021 9:39 am
Akai should work on small quality of life improvements around the workflow in the next release. One such example is a way to re-map existing bbutton.

1. On the MPC One, the +/- buttons below the wheel would be ideal candidates for octave or active track shift. Currently, I don’t see why anyone would use them when there’s a big knob right above them that changes the same parameter with both greater precision and speed.

2. I rarely jump onto the Step Sequencer or toggle TC, so those two buttons would be great to map to e.g. Solo and Mute.

3. Those four pad bank buttons - I rarely use more than 16 samples and would be perfectly happy with just one or two bank cycle +/- button and then freeing up the other 2-3 buttons for other stuff. I’d add a Last Screen feature to get back to the previous pages you were on more quickly, and then I’d add Track +/- buttons to jump between the active track more quickly across all screens.

4. The Erase button - I don’t think I’ve used it more than once. Perfect candidate for reconfiguration.

Quality of life things like button mapping should be fairly easy to implement by Akai, along with the ability to reorder and delete tracks/sequences/programs more easily using drag and drop, a Select All function in the grid sequencer, etc.

Hopefully they’re listening to feedback like this.
User avatar
By zangetsu01 Sat Nov 06, 2021 11:27 am
djst wrote:Akai should work on small quality of life improvements around the workflow in the next release. One such example is a way to re-map existing bbutton.

1. On the MPC One, the +/- buttons below the wheel would be ideal candidates for octave or active track shift. Currently, I don’t see why anyone would use them when there’s a big knob right above them that changes the same parameter with both greater precision and speed.

2. I rarely jump onto the Step Sequencer or toggle TC, so those two buttons would be great to map to e.g. Solo and Mute.

3. Those four pad bank buttons - I rarely use more than 16 samples and would be perfectly happy with just one or two bank cycle +/- button and then freeing up the other 2-3 buttons for other stuff. I’d add a Last Screen feature to get back to the previous pages you were on more quickly, and then I’d add Track +/- buttons to jump between the active track more quickly across all screens.

4. The Erase button - I don’t think I’ve used it more than once. Perfect candidate for reconfiguration.

Quality of life things like button mapping should be fairly easy to implement by Akai, along with the ability to reorder and delete tracks/sequences/programs more easily using drag and drop, a Select All function in the grid sequencer, etc.

Hopefully they’re listening to feedback like this.


Be carefull with bringing good ideas to the table. They might just pick it up and decide to implement it in the Force. :smoker:
By djst Sat Nov 06, 2021 9:45 pm
64hz wrote:As long it's all optional I don't see why this can't happen.


Yeah, the idea here is that it would all be configurable so you could reconfigure buttons you rarely need to something you use more often.
User avatar
By jabberwalky Sat Nov 06, 2021 10:37 pm
I agree. Those +/- buttons are super useless and in a prime place for something way more usable. My buttons would do entirely different things if the option were available.
User avatar
By Monotremata Mon Nov 08, 2021 11:16 pm
NewAkaiUser wrote:Good idea! Also switch step sequencer to grid mode or better the ability to freely change each button. I think @Ultros will do it faster :nod:


That would require access to the source code, which nobody here has.
User avatar
By Ultros Mon Nov 08, 2021 11:59 pm
TheKikGen released a library last year that lets you intercept alsa midi events by hijacking libc and alsa's read / write functions so its completely doable. We may not have akai's source code but there's more than one way to skin a cat.

You dont need access to the source code to hack something, merely a debugger and some assembly / programming knowledge.