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 JaseFOS Sat Aug 22, 2026 2:12 am
Hi Folks,

As part of building a new live performance rig, I have a hardware setup consisting of a 2 x MPC One Gen 1 standalones running 3.9.1, a Mac Book Pro running Ableton Live 12.4.3. My aim with this set up is to facilitate seamless transitions between MPC One projects (while also sometimes mixing in DAW-produced projects from Ableton Live).

I have no problem getting the MPC Ones and Live 12.4.3 to syncronise - in fact, it's tight as you could hope for (thanks to wired ethernet connection of the MPC One Gen1s).

The issue I'm having is that if I Stop Playback on one of the MPC Ones (e.g. to load another Project), it causes the other MPC One to Stop. This is despite having the Ableton Link Start/Stop function disabled on both units (as well as having Link Start/Stop disabled on the laptop). The Laptop still plays fine - this problem only effects the MPCs Ones.

The only workaround I've found is to disable Ableton Link temporarily on the MPC I'm about to load the next project onto and then turn it back on again once the project is loaded which is cumbersome!

It appears that the Ableton Link Start/Stop function on the MPC One units has no effect.

Is this a bug that others are encountering?
By Elijah Sun Aug 23, 2026 1:45 am
There seems to be a bug with the MPC's Ableton Link Start/Stop Sync setting.

Checking and then unchecking Ableton Link Start/Stop Sync makes it work properly, but the problem comes back after loading a new project.
By JaseFOS Sat Sep 05, 2026 1:41 am
Thanks for your reply Elijah - yes, I can confirm that toggling the Ableton Link Start/Stop sync option prior to doing anything on an MPC that would effect the Transport (i.e. opening a new project) is a workaround that works (although, tedious, right!).

The good news is that InMusic support has kindly responded to my support enquiry on this issue and they have confirmed they can replicate it. Naturally there is no immediate fix and we can only hope the next Firmware can address this issue if they prioritise it.