MPC MAJOR MIDI ISSUE : "multichannel Note off" midi bug

(sigh!)

Hi Alan,

We really appreciate your patience while you awaited for the arrival of this email, thank you.

I have personally been in contact with our developers to raise this issue both in writing and verbally. This is something we are aiming to fix in future software updates of the MPC Software. I understand that this is not the answer you were hoping for, as an instant solution would be more ideal, but I want to assure you that your email along with the MPC forum thread comments are truly valuable to us, and everything you have reported to us has been acknoledged and is now with our developers who are working hard to fix the issue.

As for refunding the MPC, this is something which will need to be discussed directly with the seller of your product. I kindly ask you to contact the seller to explain this situation and ask to receive the money which was paid to them for the goods.

I deeply apologise on behalf of the entire Akai Pro team for your experience, we truly value you and the patience you have had towards this situation. If you have any further questions, please feel free to ask.  

Hello,

I raised a ticket for the "multichannel Note off midi bug", too.

Here is the reply of Akai Pro Support.

Akai Pro wrote:Hi,
Thanks for your feedback and I apologize that your experience with me has not been adequite. I am really sorry about how long it took to receive a reply from our support team,
[...]
Regarding the note OFF events are not recorded correctly into the MPC tracks, as mentioned, I have logged this as a bug report so that our dev team are aware and we hope to provide you with a solution in a future update.
[...]
I apologize again for your experience and if you ever need to reach out to us again, please feel free to do so.

So, Akai Pro says the same thing to everyone, seems to discover the problem thanks to my ticket , but does nothing to fix it.

And the bug still exists in 2.15

Have Akai fixed this bug in MPC 3 ?

Thank you.

Crazy how none of them big youtubers even checked that bug out. This would have been the very first thing I would have checked.

mpc_fan_2022 wrote:Crazy how none of them big youtubers even checked that bug out. This would have been the very first thing I would have checked.

They're probably paid to stick to the internal software (or they just dont use MIDI gear) so they can show off all the new add-ons and rope people into buying the plugins.

mpc_fan_2022 wrote:Crazy how none of them big youtubers even checked that bug out. This would have been the very first thing I would have checked.

loopop said "Not yet" when i asked the q on his IG. lololololol

chrisroland wrote:loopop said "Not yet" when i asked the q on his IG. lololololol

Hahahahsha..... If they can't get this working for the next major release of their OS, I'm gonna probably piss myself laughing.

Can anyone confirm what the latest version is that doesn't have this bug? The device is unusable while it is present, so no point in having any new features (which I've/we've) paid for if the platform fundamentally doesn't work. From reading this thread it seems like 2.9.0 or 2.8.1? (https://www.akaipro.com/mpc-software-fi ... loads.html)

The software and the force have the same bug. It’s a fundamental issue, which I think the clowns have created intentially as a workaround for a hanging note problem that they couldn’t fix from years ago. What they’ve done to eliminate this is to send a note off command on all channels when a matching note on hasn’t received its note off.
They will never fix it until they change the clowns they call devs.
Actually. Got that wrong, incompetent clowns.

I can confirm it's still there in V3

Really? Still?...

That's just sad at this point. Akai WTF?... Akai needs to get there priorities straight.
I never bought any of there plug-ins or anything because of there practice on things like this. Also the fact they do that whole activation thing. Hell.... I didn't update once for 2 years... They just kept giving trash updates. I lost hope a long time ago, but see that the midi bug is still there in V3? Just plain ol sad...

I don't think this will ever be fixed, as much as I'd love it to. The MPC wasn't designed to be an instrument for another sequencer to control, the MPC was designed to be the control.
Have you also noticed that when connecting to the midi din in, the MPC ignores which ever midi channel you assign to a track, it will play the notes from every midi channel.

I've accepted that it will never be fixed and changed the way I work to have the more constant things (like long synth/strings chords) on the MPC and have the more intricate parts controlled by the Keystep pro on microfreak and iPad insturments. I can get away with controlling 1 instrument on the MPC by routing midi through AUM on the iPad and setting AUM to only send a specific midi channel to the MPC (bluetooth midi).

AndPerry wrote:The MPC wasn't designed to be an instrument for another sequencer to control, the MPC was designed to be the control.

I kinda have to disagree with that. The MPC should be able to multi-track Midi record, using different Midi channels simultaneously without it corrupting the Midi data. My MPC2000XL used to be able to multi track midi record just fine. The 2K manual even mentions plugging in external sequencers to record from. Simultaneous multi track/Midi channel recording for me has always been a part of what the MPC does, and should do.

This really shouldn't be an issue with today's hardware.

It will get fixed when it costs Inmusic too much to keep it unfixed.