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.
User avatar
By jaymack Thu Feb 20, 2025 4:05 pm
Ongoing Improvements

We deeply appreciate the feedback from our MPC 3 beta users. Two key areas—Time Signature Support and the MIDI Note Off issue—have been at the forefront of your input. Please rest assured that we are actively working to address these concerns in a future update.

Bug Fixes

In Keygroups, Aftertouch / Pressure to Filter parameters are no longer broken after duplicating the track
Activations and Splice pages in the preferences no longer display “attempting to connect to network” when already connected and online
“License Error, Reactivate” issue that causes licenses to deactivate no longer occurs on startup
“Unable to save samples” error no longer occurs when saving the project after using a bounce function. The sample saves correctly with the project.
Auto Sampler now records audio correctly after adjusting the inputs
AKP files now load correctly
Resolved an issue with the Pad mode not updating correctly when moving between Sample Edit, Track Mute and Main Mode
Slices converted using “New Drum Track Using Slices” now retain source BPM
Copy Bars and Delete Bars now default to the current sequence
Internal file paths no longer appear in popup messages
Audio tracks are now audible after looping when loop start is not set to bar 1
Character limit popup shows when saving a track which exceeds the limit
Tapping a pad selects it in the “Assign to Pad” field when creating stems
Shutdown time is no longer increased when Wi-Fi is off
Pad Mute pads light up to reflect the current tracks playback only
Audio and Event track mutes now have different names in the automation lanes
“Remove sample” TUI icon no longer appears in Track Edit for Drum/Keygroup layers without samples assigned
“Bounce to Audio Track” no longer saves a copy of the bounced audio to MPC Documents > Exports
After using “Drum pads to stems”, Save > Audio Mixdown with “Separate tracks” toggled on, saves audio for each track correctly
Event Mute automation is retained after using song mode, “Convert to sequence” and then using Copy Bars
Keys are retained for samples after using Convert functions on slices to create new samples
Resolved an issue where using Undo after Processing a sample that has just been created with Create Stems would also undo the creation of stems
Adjusting Program Change for a MIDI Track no longer affects the Program change value for other MIDI tracks in the project
In track mute mode, assigning track groups via the TUI now displays the group number correctly
Ableton Live Set export now works correctly and exported files load without issue
Copy Track function on Arrange and Track View's callout menus have been renamed to Duplicate Track as this is the function that occurs when this is used
Resolved an issue where certain MIDI data would not be deleted when recording over existing data in the arrangement
Error no longer occurs when reselecting a user plugin for Mellotron
End Markers now appear correctly after using manual chop in Sample Edit
Changing the loop status for a sample in a loaded project now saves the new status correctly with the project

Known Issues

If event automation exists, inserting bars before bar 1 causes tracks to be event-muted in that region
Event Mute cannot be assigned in Q-Link Edit / MIDI Learn
Toggling effects on/off on 2 or more simultaneously causes UI to become out of sync
Activations list not accurate on first startup after updating
Metronome doesn't sound when set to Mono Output
Multiple uses of Double Length with Events on Arrangement causes UI to freeze
Load to Pool not working for Splice files on external drives
Program Changes with LSB & MSB cause note conflicts
Track Length setting is fixed in copied sequence after using Copy Sequence
PC MSB LSB wrong value when input by the number pad.
By Unclegarygoo Thu Feb 20, 2025 5:48 pm
Very excited about some of the major bug fixes here! It seems that the export process has been almost fixed.

When I was on MPC 2, I used to have to export my tracks (audio mixdown), twice. On the second export my automation would correctly export.

On MPC 3.4.1, I could never get my automation to export correctly, it was usually a few milliseconds off no matter how many times I exported the audio.

On MPC 3.4.2, the automation is incorrectly exported when I export it once, on the second export, it correctly is written on my tracks.

Not overly excited about this but at least I can move forward with some projects.
By Masi Thu Feb 20, 2025 8:57 pm
jaymack wrote:Known Issues

Anyone knows and is allowed to tell us why these issues are listed?

The list of reported issues must be much longer.
By jamos Fri Feb 21, 2025 12:14 pm
Masi wrote:
jaymack wrote:Known Issues

Anyone knows and is allowed to tell us why these issues are listed?

The list of reported issues must be much longer.


Typically this means that the issue has been confirmed and is being investigated.

Many bug reports are not reproducible and therefore can't be confirmed or investigated. This is why it is important for beta testers to take the time to create a good, minimal, repeatable test case when reporting a bug, if at all possible.
User avatar
By MPC-Tutor Fri Feb 21, 2025 1:25 pm
Masi wrote:
jaymack wrote:Known Issues

Anyone knows and is allowed to tell us why these issues are listed?

The list of reported issues must be much longer.


These are just issues they are actively looking at with some degree of priority. Other issues are logged, a priority is set, and these issues may or may not be investigated immediately.
By Straker Fri Feb 21, 2025 1:35 pm
How is the compatibility with MPC2 projects?
Are all tracks loaded correctly?
Are track mutes loaded correctly?
Are qlink assignments in project mode loaded correctly?