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 Smiley Mon Feb 03, 2025 9:08 pm
Immediately after updating from Mpc 2.* To 3.4.1 i noticed the pads were less responsive. They also retrigger the sample sometimes.
I have reset preferences and tried all velocity and pad curves but i can still feel the pads are way less responsive then before.
Sorry this is not a data driven bug report as such but it is so noticable that perhaps other users can confirm the same?
User avatar
By Logrinn Tue Feb 04, 2025 2:12 pm
Elijah wrote:... This issue does not occur when overwrite recording with a single pad, but it happens when performing finger drumming using multiple pads...
...This issue does not occur when using external USB-MIDI pads or in controller mode (MPC2).


MPC-Tutor wrote:Okay, got it. TC must be off. That's really not good at all.

A way to highlight it; record basic kick snare pattern at half level. Extend all the events then record at full level so you can see the short red events on top of the existing long yellow events.

Also SHIFT > SELECT ALL > DELETE doesn't seem to visually delete those ghost events. You have to leave grid and go back before they go.

I just officially reported this to the closed beta group.


I couldn't recreate this on my Key37.
I was interested to see if it was a pad or a key related issue, but both options work for me.
@Elijah @MPC-Tutor What hardware did you try this on?
Could someone with both a Live (or Live II or One or One+ or X) and a Key 37 (or 61) try this to see if the hardware makes a difference?
By Rezolve Tue Feb 04, 2025 10:26 pm
Sequence track mutes don't seem to carry over to song mode. I have 5 sequences in the project and I have set up track mutes in each sequence and they work fine when I switch sequence in the Main window. When I create a song with the same sequences, the track mutes seem to randomly change. Is this a bug or am I doing something wrong?
By Smiley Wed Feb 05, 2025 5:19 am
Expected: project continues playing while saving
Currently: project stops when clicking 'save project' (no sound, no play)
This is a flow killer! In 2.* It could temporary unresponsive while saving, which i understand. But stopping the project entirely?
By Primalmotion Wed Feb 05, 2025 2:19 pm
Rezolve wrote:Sequence track mutes don't seem to carry over to song mode. I have 5 sequences in the project and I have set up track mutes in each sequence and they work fine when I switch sequence in the Main window. When I create a song with the same sequences, the track mutes seem to randomly change. Is this a bug or am I doing something wrong?


I have noticed the same problem. I think I was able to work around by going into NEXT SEQ and tap the "-> to song" shortcut at the bottom of the screen to refresh the mutes in SONG mode. But yeah the mutes on sequences seem to randomly change otherwise.

(also: this is my first post here :) hello y'all!)
By MaschineRefugee Wed Feb 05, 2025 7:00 pm
Recorded an audio track, full length of a 150 bar sequence.
Set the loop to start at bar 10, end at bar 13.
Added a plugin track (synth), with the intention of recording a synth part over the audio.

What happens: When playing or recording the loop, the looped part of the audio track is only played once. Upon the second loop: silence.
What should happen: the looped part of the audio track should play in every loop.
By Broken Gadget Wed Feb 05, 2025 7:36 pm
Using MPC One. A long sequence (190 bars). Go to the track mute screen, switch the R to W, hit play and mute and unmute some tracks. Works in real time. Switch W back to R, but the mutes are not replayed.

Tested with a mix of midi tracks and audio tracks.

In list edit mutes have been recorded but to re-iterate they do not play back. This is true whether the event or audio mutes option has been chosen.
User avatar
By MPC-Tutor Wed Feb 05, 2025 10:13 pm
Thanks, although we've already listed this bug twice previously in this topic

MaschineRefugee wrote:Recorded an audio track, full length of a 150 bar sequence.
Set the loop to start at bar 10, end at bar 13.
Added a plugin track (synth), with the intention of recording a synth part over the audio.

What happens: When playing or recording the loop, the looped part of the audio track is only played once. Upon the second loop: silence.
What should happen: the looped part of the audio track should play in every loop.
By vorn1 Wed Feb 05, 2025 10:51 pm
Record MIDI on different tracks and different MIDI channels, but with the same MIDI note number.
Expected: Any MIDI note is recorded as long as it was sent to each track.
Actual: Note-off message on one track cuts off notes on other tracks.
By pitrak Wed Feb 05, 2025 11:33 pm
On the key61, you can assign the touch strip to a qlink - cool for controlling a bunch of project parameters.
However, when you touch another qlink, the touch strip links to that qlink. Seems like a bug not a feature, and makes combined usage of touch strip and qlink impossible..
By MaschineRefugee Thu Feb 06, 2025 7:51 am
MPC-Tutor wrote:Thanks, although we've already listed this bug twice previously in this topic

MaschineRefugee wrote:Recorded an audio track, full length of a 150 bar sequence.
Set the loop to start at bar 10, end at bar 13.
Added a plugin track (synth), with the intention of recording a synth part over the audio.

What happens: When playing or recording the loop, the looped part of the audio track is only played once. Upon the second loop: silence.
What should happen: the looped part of the audio track should play in every loop.

Sorry, will pay better attention…
By Broken Gadget Thu Feb 06, 2025 11:41 am
No drum tracks on Export

Dan F wrote
1. Create a song with a drum track
2. Menu>Song Mode
3. Export

Expected Result: Wav file with all tracks and no disruption to MIDI programs on .xpj file
Actual Result: No drums on wav file and MIDI drum program completely wiped


I reported the drum track failing to render to a wav in export mixdown to AKAI in the beta stage. I found that a workaround was to solo the drum track to create its own wav, then to open another project and mix that wav with what was rendered in the mixdown wav. I haven't witnessed the midi drum program being wiped though.