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 MPC-Tutor Thu Sep 05, 2024 6:49 pm
Use this thread to report any bugs you find in the new mpc 3.4 beta. However don’t forget to report direct to akai as well as we've no idea if they are reading this.

Please remember to state your MPC model when reporting and generally give lots of detail with step-by-step recreation. also state your version number, as I assume Akai will be rolling out constant updates. Current release is 3.4.80 (preferences > info)

MPC3 Bug Reports

MPC 3 Feedback & Suggestions
By dustyslices Thu Sep 05, 2024 7:11 pm
1. Assigning "looper" sample directly to an audio track crashes MPC
2. Audio Clip Container doesn't resize according to "parent" sample pitch
3. in order to change parameters in sample editor, you must touch the sample waveform first in order to make it "active".

By sduck Thu Sep 05, 2024 8:46 pm
No time signatures besides 4/4. You can't use the old workaround by adding new bars to a sequence with the time signature you want and then deleting the 4/4 bars - there's no option to input what time signature you want. Seems like a pretty major omission to me, and I know it is to a few people on facebook.

Bug report filed.

And if you have projects with non 4/4 time signatures, back them up before opening them in this new version! they will get converted to everything being in 4/4, sometimes with "interesting" results.
By mas_akala Fri Sep 06, 2024 1:24 am
MPC Live 2 gets "incorrect wifi password" response when attempting to connect. Password is definitely correct. Tried on multiple wifi networks. Downgraded back to 2.15, wifi works as expected. Upgraded to beta 3.4.0.80 both with USB drive and PC method, can no longer connect to wifi. Tried reseting preferences, did not resolve. Ethernet cable works as expected.
By Tony Byrne Fri Sep 06, 2024 9:12 am
There are display glitches in the Grid view at certain zoom levels, where white vertical beat grid lines get overwritten by the passing playhead. The same lines also don't quit line up with the divisions in the loop header.
User avatar
By MPC-Tutor Fri Sep 06, 2024 9:48 am
This is not strictly a bug, it's just a feature they've chosen to not implement (for whatever reason, but it's the same on the Force which doesn't bode well).

sduck wrote:No time signatures besides 4/4. You can't use the old workaround by adding new bars to a sequence with the time signature you want and then deleting the 4/4 bars - there's no option to input what time signature you want. Seems like a pretty major omission to me, and I know it is to a few people on facebook.

Bug report filed.

And if you have projects with non 4/4 time signatures, back them up before opening them in this new version! they will get converted to everything being in 4/4, sometimes with "interesting" results.
By Aisomon Fri Sep 06, 2024 12:06 pm
My report
When I boot up the MPC X SE in standalone It boots up slow and I get the following message 1 of your plugin content folder(s) could not be found. Please, check that your storage media is attached. Do you wish to keep scanning this location for content?
By constantG Fri Sep 06, 2024 12:16 pm
My MPC One is connected to the internet but will not let me activate the beta. When I go to the activations page, I can see the beta at the bottom of the list but it won't let me do anything. Also when it starts, there is a message saying that it cannot find a plugin folder(s).
By dustyslices Fri Sep 06, 2024 1:33 pm
constantG wrote:My MPC One is connected to the internet but will not let me activate the beta. When I go to the activations page, I can see the beta at the bottom of the list but it won't let me do anything. Also when it starts, there is a message saying that it cannot find a plugin folder(s).


check if your date and time are correct, if not then adjust them manually. "Ones" don't have constant access to the time server and the RTC in the device likes to drift apart. Your device won't show you "activate" buttons if the time on the device is different than on the activations servers.
EDIT:
don't forget to reboot it afterwards
User avatar
By Jean-Marc Liotier Fri Sep 06, 2024 2:05 pm
dustyslices wrote:"Ones" don't have constant access to the time server and the RTC in the device likes to drift apart
You mean those that are not permanently connected with RJ-45 or all of them ?
User avatar
By Logrinn Fri Sep 06, 2024 4:58 pm
MPC KEY 37

Locators jump to the start of the bar specified.
Ie if I set three locators at bars 4:1:0, 5:3:0 and 6:1:0, the first and third of these locators jump to their right place; start of bar 4 and start of bar 6. But the second locator doesn't jump to 5:3:0, but instead to the start of bar 5.
No matter what value I specify, a locator always jumps to the start of the bar in question. The beat and tick values specified doesn't matter.
By MoodyB Fri Sep 06, 2024 10:01 pm
mas_akala wrote:MPC Live 2 gets "incorrect wifi password" response when attempting to connect. Password is definitely correct. Tried on multiple wifi networks. Downgraded back to 2.15, wifi works as expected. Upgraded to beta 3.4.0.80 both with USB drive and PC method, can no longer connect to wifi. Tried reseting preferences, did not resolve. Ethernet cable works as expected.


My Live 2 connected & activated fine over wifi here.

Upgrade to v3.4 was done via usb drive.
By Lex Luthor71 Sat Sep 07, 2024 12:01 am
After rearranging the Menu icons to my preference, every time I boot the MPC LIVE, the Control icon ends up at the bottom next to the Project/Save/Preferences Tab and the New Project Tab ends up above it where it used to be. Also every time I boot up the MPC LIVE after a few minutes of it being off when I go to Preferences> Activations, my Flex Beat plugin, MPC STEMS feature, and the MPC Beta are listed with the Activate button and I have to keep Activating even though they're all paid got and registered under my account and had been previously Activated. Refreshing and Logging out my account on my MPC LIVE doesn't address this. I’ve reported this to Akai so hopefully this gets addressed in a future update.