BUG! MIDI mapping FX filter with external MIDI controller

Hello. Help!

I'm having serious problems with mapping fx to external controllers. Every time I open a second project in my MPC and I move the parameter that I have mapped (for example the frequency of a filter), it starts to glitch, giving random values, and when I open the screen of that effect, it directly freezes the MPC, forcing me to reset the machine. If I map other things, like volume of a track, everything works fine. It only happens with the fx . I have done all kinds of tests, but I can not solve it.

...and for more surprises, i even get the same bug on MPC2 software!


This video explain all the process: https://www.dropbox.com/s/4rfukawozb0q028/Error%20mapping%20FX%20on%20external%20midi%20controller%207abr23%20v1.mp4?dl=0

Please, help me. This is an important feature to my live gigs. Thanks!

Did you ever find a fix for this? I’m trying to map a knob to delay feedback on a track and seeing the same issue.

I have the same issue with mapping a Launchcontrol XL to the filter cutoff on a submix. Exactly the same behavior. Can anyone fix this please?!

Have you turned off 'Learn' in midi control?

Also, is Automation Write enabled?

Neodymium wrote:Have you turned off 'Learn' in midi control?

Yes, i turned it off, but still the same problem. It´s ok if is the first project you are editing after turning on the MPC, but after you save it with the mapping changes and open it again, the mapped knob start to move randomly and glitch, and if you try to use it anyways ,it freezes the machine

I'm having the same problem! As soon as I turn a knob from my midi controller that controls a filter on a sub mix it starts to bug out. It continues to randomly move the filter and eventually the entire MPC freezes up. It worked fine on my first sequence, but on the second sequence I start having this issue.

Does anybody have a fix for this??

Finally AKAI spoke: They have done some test after i put a ticket with the issue and they admit this is a BUG on the firmware. They say they are gonna fix it on future releases of the firmware, and meantime they recomend downgrading the firmware to previous releases when this bug didn´t existed.

Back to the future

I see the exact same behavior here on OS 2.15. I got to say this is a huge omission, in 2024 external control is everywhere. Basic compatibility is not a luxury, it is a requirement.

same problem here... this also happens in MPC standalone... It's absurd that such a basic bug takes so long to be fixed

Has anyone resolved this issue on 2.15? Also for those that have moved to 3, does this issue exist?

So, We are on 2.15.1 and have the identicle bug. Perfectly explained. Thanks.

Any updates? Any fixes?