In my conversation with Arturia support it looks like they have now scheduled our issue to be investigated:
This issue is now referenced in our database.
• Our Q.A department will now review this issue in order to work on it along with our Dev Team and hopefully fix this in a forthcoming update / hot-fix.
I also recently received a meaningful reply from them where they acknowledged the issue, noted that it was present in an earlier firmware and that 1.1.1 was meant to address it but did not, and that they are actively working on it.
1 Like
I also sent them a video - it describes the sustain pedal delay issue. I also give an example with another keyboard - how it should work. The video is here - https://youtu.be/dW-okn_9nDw
Waiting for their reply
1 Like
So after relentless hounding Arturia tech support and sales, whom I directly purchased it from, I got a response today that may be promising. I’m not at my KeyLab mk3 at the moment, but if anyone is and can try this temporary workaround, pls post.
Thank you for your detailed follow-up and for sending the videos. I completely understand your frustration—especially with an important performance coming up—and I want to clarify that this is not an isolated case or an issue on your end.
We have been able to reproduce similar sustain pedal behavior on the KeyLab mk3 with certain pedal models, including the Yamaha FC4A and Roland DP-10. This has already been logged with our development team and is under active investigation for a firmware fix. The problem occurs when the unit processes the HOLD function in parallel with MIDI note events, which can cause dropped or delayed sustain messages during fast playing.
Temporary workaround:
In the MIDI Control Center, set the sustain pedal’s Max Value to around 120–126instead of 127. This prevents the HOLD LED from triggering and avoids the timing issues. The downside is reduced half-pedaling range, but it will restore stable sustain behavior until the firmware update is released.
I have linked your ticket directly to the ongoing bug report so your case is included in the priority review. Once the firmware update containing the fix is available, I will reach out to you immediately.
I understand the timing here is critical for your upcoming show, so please let me know if you’d like me to guide you through applying the workaround right away.
Best regards,
Andrés - Arturia Support


Has anybody implemented this “official” workaround yet? I use Gig Performer and so far I’ve experienced no issues using the sustain pedal input. I’ve run a few MIDI Monitor tests and I’m getting 0-125, which is where I’ve set the highest value. I’ll probably bump up the higher value a digit or more later on, but for now, I’m feeling confident I can use my mk3 for this Saturday’s gig with complete confidence.
???
???
Anybody own a mk3 anymore?
I also got this reply. But that doesn’t work for me as I want to use the pedal in switched control mode. In the control mode there’s too much unnecessary info on cc64 which is hard to edit - it takes a lot more time. I also asked when to expect the fix. But the answer was - they can’t give the answer). I really think that the problem can be in the hardware design as thd software fix can’t take that much time. So my keyboard is back to the store, they we kind enough to give me a refund. Good bye, Arturia. That was not the best experience.