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 virtualan Tue Feb 25, 2025 8:01 pm
MPC 3.4.2 Release Notes
MPC 3 Firmware Update
Compatibility

This release is for MPC Key 37, MPC One+, MPC X Special Edition, MPC Key 61, MPC One, MPC Live II, MPC X and MPC Live hardware.

Desktop Software

In controller mode MPC remains compatible with the MPC 2.15 desktop software. However, please note that projects created in Standalone Mode on version 3.4 are not backward compatible with the MPC 2.15 desktop software.

Downloading the Firmware Update

To download the 3.4 Firmware Update, use the online updater or navigate to MPC Software & Firmware Downloads and select the appropriate download.

For instructions on installing these updates, please visit our support page here.


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.


WHEN???? 2040??????
By chrisroland Tue Feb 25, 2025 9:12 pm
virtualan wrote: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.


WHEN???? 2040??????


as others noted from the full release notes, it sounds like Akai is in the process of a larger overhaul of the MIDI system generally for this "Spring":

MPC3 OS for Standalone will receive highly requested updates in Spring, including Flexible Time Signatures, Wireless Expansion Transfer, and Enhanced MIDI Recording & Playback - addressing user-reported challenges with external gear and additional new features that will further elevate the MPC3 OS experience."
By [email protected] Fri May 30, 2025 9:43 pm
I CAN NOT BELIEVE THIS HAS NOT BEEN FIXED YET. Now is spring. Almost summer. Release 3.5. Bug is there. Live 2. Workaround: Adressing tracks via 2 Midi Din and USB. Thank god the Hapax has different outputs. So I can manage approx. 10 average note-filled tracks if I evenly distribute them. It's a pitty... but hope dies last.
User avatar
By Ultros Fri May 30, 2025 11:52 pm
Forget about it, the days of using midi are over! Now we all just break out our wallets for novelty dlc packs like punks. "Abuse me akai, abuse me for buying your product! No really they love us they only beat us on wednesday!" I ended up selling off most of my synths while waiting for this to be fixed.
By BackOnDaMPC Sat May 31, 2025 6:58 pm
virtualan wrote:MPC 3.4.2 Release Notes
MPC 3 Firmware Update
Compatibility

This release is for MPC Key 37, MPC One+, MPC X Special Edition, MPC Key 61, MPC One, MPC Live II, MPC X and MPC Live hardware.

Desktop Software

In controller mode MPC remains compatible with the MPC 2.15 desktop software. However, please note that projects created in Standalone Mode on version 3.4 are not backward compatible with the MPC 2.15 desktop software.

Downloading the Firmware Update

To download the 3.4 Firmware Update, use the online updater or navigate to MPC Software & Firmware Downloads and select the appropriate download.

For instructions on installing these updates, please visit our support page here.


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.


WHEN???? 2040??????
2040 seems very likely :lol:
By [email protected] Sun Jun 01, 2025 8:37 am
MPC & HAPAX – A love story with missing notes
After several years of exploring virtually every type of synthesizer, sampler, drum machine, groovebox, tablet, and VST, I have now reached what I would call a milestone. I wanted to create two perfect worlds for myself, where music production is truly enjoyable and I am not held back by technical obstacles and complicated workflows.

World 1 (PC): Mac Mini M4, Hookpad for songwriting (100% web-based), Ableton as DAW, Ableton Push 3, Launchkey Midi keyboard, TEControl Breath Controller, Stream Deck, ACE for AI vocals.
In this world, anything is possible. But you get distracted and end up sitting in front of a screen all day again. And you spend a lot of time maintaining software agents from Arturia, NI, Roland, etc., have to update your system all the time, and then you don't make any music during that time.

World 2 (No PC): Hookpad again for songwriting, AKAI MPC Live II controlled by Squarp HAPAX.
In my opinion, the combination of HAPAX and MPC Live II is almost perfect. Important to note: MPC must be Clockmaster (otherwise plugins and effects won't sync properly) and three physical MIDI connections should be set up from the HAPAX to the MPC so that 8 plugin and multiple drum tracks can be sequenced flawlessly. Because the only thing that really annoys me about this otherwise brilliant combo is the note-off or MIDI channel overload bug in the MPC. With an MPC One, this is a total showstopper. With a Live or X, there is a workaround to switch to other MIDI interfaces as soon as the bug occurs. The channel number can be left as it is (which is cool because then learned MIDI CCs for automation don't have to be relearned).
As an example, I control 3 drum tracks via MIDI DIN A, 4 synth tracks via MIDI DIN B, and 3 more via USB MIDI in a template. With a little luck, the bug doesn't show up anywhere and working with the entire system is really fun.
Speaking of automation: it works absolutely brilliantly with HAPAX and MPC.
Have a nice Sunday
John

PS: And if you don't own already one get a HAPAX NOW! The HAPAX is THE most important machine on my journey. It’s just the perfect sketchbook and it can do so much in such an easy way.

PS2: I will open InMusic-Ticket 27453276 concerning the midi bug. Some are guessing Akai has planed to fix it by 2040 ;)
User avatar
By Oscar South Mon Jun 30, 2025 5:51 pm
virtualan wrote:MPC 3.4.2 Release Notes
MPC 3 Firmware Update
Compatibility

This release is for MPC Key 37, MPC One+, MPC X Special Edition, MPC Key 61, MPC One, MPC Live II, MPC X and MPC Live hardware.

Desktop Software

In controller mode MPC remains compatible with the MPC 2.15 desktop software. However, please note that projects created in Standalone Mode on version 3.4 are not backward compatible with the MPC 2.15 desktop software.

Downloading the Firmware Update

To download the 3.4 Firmware Update, use the online updater or navigate to MPC Software & Firmware Downloads and select the appropriate download.

For instructions on installing these updates, please visit our support page here.


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.


WHEN???? 2040??????


Checking in -- we get there yet?
By jamos Tue Jul 01, 2025 2:55 am
Oscar South wrote:
virtualan wrote:MPC 3.4.2 Release Notes
MPC 3 Firmware Update
Compatibility

This release is for MPC Key 37, MPC One+, MPC X Special Edition, MPC Key 61, MPC One, MPC Live II, MPC X and MPC Live hardware.

Desktop Software

In controller mode MPC remains compatible with the MPC 2.15 desktop software. However, please note that projects created in Standalone Mode on version 3.4 are not backward compatible with the MPC 2.15 desktop software.

Downloading the Firmware Update

To download the 3.4 Firmware Update, use the online updater or navigate to MPC Software & Firmware Downloads and select the appropriate download.

For instructions on installing these updates, please visit our support page here.


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.


WHEN???? 2040??????


Checking in -- we get there yet?


Spaghetti code.
Spaghetti design.
Throw it all against the wall and see what sticks.

3.x will never be stable.
By 40Beatz Tue Jul 01, 2025 1:29 pm
2.xx was Never Fully Stable lol.

We gotta learn to put that Spaghetti in a Bowl and add somethin to it, to make Delicious Beats.
I don't know of ANY Software that is 100% Bug Free. At some point we have to learn to Navigate thru the Wilderness. Figure out Workarounds. I remember when AKAI put out ONE, maybe TWO Updates Per Machine lol. Now we're spoiled lol
User avatar
By Neurone Wed Jul 02, 2025 7:45 pm
Let’s just remember this bug has been around for four years and Akai knew.
That’s gross incompetence.
In that time they’ve ignored it all whilst using considerable dev resources to sell us new plugins.
Akai will have to suck it up and fix it.
By 40Beatz Wed Jul 02, 2025 8:11 pm
Quick Question...

Could you guys get into list Edit and removed the "Note Off" messages after its been recorded? Or is that Overkill? I'm just tryin to imagine a Workaround for that Bug
By B-Wise Thu Jul 03, 2025 7:29 am
40Beatz wrote:Quick Question...

Could you guys get into list Edit and removed the "Note Off" messages after its been recorded? Or is that Overkill? I'm just tryin to imagine a Workaround for that Bug

That wouldn't work because the notes are already cut short & I don’t even think the note off messages are displayed in the list editor.

The simple workaround is to record each track while using a fast BPM. The more advanced method is using a MIDI patchbay & setting each MIDI channel as is own port or something like that. There thread for this somewhere on this site.
User avatar
By Neodymium Thu Jul 03, 2025 4:48 pm
From my understanding, I hope I have this right. Is that when 2 synths need to used the same note say C4, The first midi CC to cut off C4 will effect both synths. So they both get a duration to that point in time. So it's not editing not offs, but editing note length. Taking the note that cut off prematurely and extending it to it's intended length. Depending on how this bug effects you're workflow, it could be a fix, rather than a workaround.

I think a general work around would be stopping synths playing in a the same range. Compositionally (is that the right word) unless you are looking for unison notes this is probably not bad practice. But if you have two musicians playing away, that's easier said than done. If a bass synth player is say triggering the MiniD, telling a keyboard player to stay in his lane and watch out for left hand work is probably not a bad idea, unless you are that keyboard player. Alternatively, transposing the midi out from the bass synths trigger keyboard down an octave, whist shifting the bass synths oscillators up and octave, results in the same frequency output. reducing the chance both playing the same note. At the same to shifting the keyboard player midi trigger keyboard up an octave, whilst transposing the their synth oscillators down an octave creates even more space between both synths and their midi Notes.
By chrisroland Thu Jul 03, 2025 8:06 pm
Neodymium wrote:I think a general work around would be stopping synths playing in a the same range. Compositionally (is that the right word) unless you are looking for unison notes this is probably not bad practice. But if you have two musicians playing away, that's easier said than done.


Yes this is the real problem when trying to integrate an MPC into a multi-hardware setup. I can map the MPC midi note values and ranges to generally workaround what my other synths/drum machines are being sequenced but eventually, the more plugins i want to use on MPC the more clashes there are going to be with overlapping note ranges in the other gear. it's just a giant pain in the ass when it doesn't need to be (and shouldn't be, given that discrete multichannel sequencing was the whole purpose of midi in the first place)