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 kazakore Thu Feb 08, 2024 1:23 pm
This is a huge one! Can't believe it can have gone unmissed for long but it's in both 2.12.3 and the 2.13 just released.

In short; any Note Off of the same Note value, eg E3, with trigger Note Off on ALL E3 notes triggered from the same MIDI port, no matter the Channel number.

You need to be triggering the MPC externally to show this, easy from a DAW or sequencer.

Start the MPC, open an Empty Project.
Load a Program (either Plugin or Keygroup) which can hold a sustained note.
Set the Track to only listen to a single channel of your MIDI source.
Send a sustained note on that channel and start looping playback over it.
Go to another track set to a different MIDI channel and enter a short note somewhere in the middle.
The original sustained note will be cut off by the Note Off in the other channel no matter what channel it is set to as long as it's on the same port.

Only tested with USB, but I have two virtual MIDI ports from my sequencer and A does not interfere with B and vice versa.

Does anybody know if there's a firmware version where this very simple thing works correctly?
By mpc_fan_2022 Thu Feb 08, 2024 3:20 pm
Why are you ruining the mood here, when a brand new MPC Key 37 has just been release? AKAI is busy that's all, stop being negative be positive and go buy the brand new MPC Key 37, The internet is so horrible these days with all the people whining about little things! It's not like AKAI can do everything you want! Look at the beautiful influencer videos, and back then with the oldschool MPC 2000 we didn't complain like today!

--

Sarcasms aside, there are multiple threads about this freaking bug that prevents me to use my MPC the way I want to, and no I won't work my way around that bug, i want that fixed... I don't understand how this is not on the top of AKAI's list, this bug is absolutely an embarrassment. Of course, none of these influencers who got a free MPC key 37 are talking about it.
Last edited by mpc_fan_2022 on Thu Feb 08, 2024 3:25 pm, edited 2 times in total.
By mpc_fan_2022 Thu Feb 08, 2024 3:33 pm
It occurred when they fixed a MIDI OUT bug if I recall correctly. Somehow fixing the MIDI OUT bug introduced a regression bug for MIDI IN. Fixing a regression BUG is always an engineer's most urgent task to fulfill.
By Rcmusic35 Thu Feb 08, 2024 6:46 pm
They know about it since a great amount of updates. you can see this in all the last release notes:

Off topic:
Known issues:

The following issues have been confirmed by Akai Professional to be present in this and previous versions of MPC firmware. We are actively working on a resolution to these issues.

In some cases, MIDI note-off messages can be sent to the wrong MIDI channel when received from multiple sources simultaneously.
By Rcmusic35 Thu Feb 08, 2024 6:48 pm
oh, and it appeared on release notes from 2.11.9 so maybe 2.11.8 does not have it? I was under the impression it was way older than this.
User avatar
By Neurone Wed Feb 05, 2025 12:31 pm
Korzo wrote:They announce that they are aware of it, and they will solve it in the last release


Yeah, they told me that two years ago.
Keep buying those plugin$....
By Straker Wed Feb 05, 2025 2:38 pm
Korzo wrote:They announce that they are aware of it, and they will solve it in the last release

They just said "in a future update" which, in Akai terms, could be next week or next year or before 2030 anyway.
But you can buy NI forest expansion or fire some cut down Kontakt xylophone sound meanwhile.
By B-Wise Wed Feb 05, 2025 2:44 pm
Straker wrote:
Korzo wrote:They announce that they are aware of it, and they will solve it in the last release

They just said "in a future update" which, in Akai terms, could be next week or next year or before 2030 anyway.

Or they could do you dirty like the Force & forget about they device all together.
By Masi Wed Feb 05, 2025 8:44 pm
Neurone wrote:
Korzo wrote:They announce that they are aware of it, and they will solve it in the last release


Yeah, they told me that two years ago.
Keep buying those plugin$....

Happens with other companies too.

I reported a bug with Drumbrute Impact to Arturia. Got a response that they new and are working on it. No firmeware update has been releasead to fix the issue.
User avatar
By angel Fri Feb 07, 2025 9:37 am
Thanks for reaching out and I apologise for the delay in correspondence, we were closed over the holidays and weekends with a high number of tickets and I just want to assure you that your message is important to me. My name is Rich from the level 2 team.

Firstly, I highly appreciate you reaching out to me to report this, and I completely understand the frustration it has caused, because I also use 2 MIDI keyboards with my MPC.

This same bug has been raised to the developersmany times, and I have received multiple complaints from users online both on forums and through support tickets. Me and the Akai Pro team are very aware that this is an issue which needs to be resolved.

I know that it is taking a very long time and I sincerely apologise for that. I know that this is not what you want to hear, but from a technical support level, I cannot say when this will be fixed, as, based on my understanding, the coding required to fix this involves a deep deep dive into the OS as opposed to being a standard fix.

What I can tell you is that the developers are very aware, and they do intend to resolve the bug. I know that this is a vague update, but unfortunately it's the only information we have right now.

Please don't allow the time it takes to repair the bug deceive you into thinking it's being ignored; the developers are working on it and your voice is heard.

I kindly ask you to keep your inMusic/Akai Pro account active to receive updates in seperate emails when updates are released. Updates do not come directly through this support ticket and will come through the mailing list and our social media accounts.

As this issue cannot be resolved by technical support and instead can only be resolved through the developers in an update, I'm going to close this ticket. If you have any other questions, please feel free to submit another support ticket.

Kind Regards,
Rich
Technical Support Specialist - Level II
inMusic Europe Ltd