MPC 3.5 Standalone Bug Reports

There are some noticeable stuttering, clicks and pops when I change from one sequence to another in the main mode. Although it’s gone after a second. It looks like the cpu or ram is struggling for a short period of time while loading the waveforms of the new sequence.

This is really crucial thing for live performances and I think a lot of people will appreciate if you could look into it.

ontherun wrote:On 3.5 i have a lot of midi Programs wirh. CC mapping and names.
When I load the midi program it doesnt schon my names for the CCs.

Same here.

I tried to map my Nymphes and PRO-800. At least the mappings seem to be kept in the project file. So I could make a template project with CC mappings.

What is stored in a MIDI program if not the CC names?

Masi wrote:

ontherun wrote:On 3.5 i have a lot of midi Programs wirh. CC mapping and names.
When I load the midi program it doesnt schon my names for the CCs.

Same here.

I tried to map my Nymphes and PRO-800. At least the mappings seem to be kept in the project file. So I could make a template project with CC mappings.

What is stored in a MIDI program if not the CC names?

Interesting, now I have to finx the project where I first assigned rhe names? That was months ago

See viewtopic.php?f=48&t=219402&p=1894343 - Unfortunately, I can't find the mentioned "Known Issue" in the release notes anymore… Not sure if they quietly removed it or if I’m just missing it. I've been checking for a new release every day, hoping they’ll finally fix it.

Ales Shi wrote:There are some noticeable stuttering, clicks and pops when I change from one sequence to another in the main mode. Although it’s gone after a second. It looks like the cpu or ram is struggling for a short period of time while loading the waveforms of the new sequence.

This is really crucial thing for live performances and I think a lot of people will appreciate if you could look into it.

*Program Changes with LSB & MSB cause note conflicts*
*PC MSB LSB wrong value when input by the number pad*

Is it still a known issue, or just buried? Still not comfy with 3.xx yet. Need stuff to work together like before lol.

I have an MPC live 2. I have noticed since the update to 3.5, every time I chop a sample, I get an unwanted distortion at the end of the sample after I time stretch.
I make sure that the sample is trimmed correctly at the start and end of the sample, to avoid pops and clicks. Also the distortion isn’t there when I test the playback of the sample before I time stretch.
I’m hoping someone out there has an answer for this as it’s made using my mpc pointless if I can’t get a clean sound. It never used to happen before on 2.0 etc.

MPC 3.5.0
Muted tracks in arrange view reset at beginning of each location and or original sequence length. Behaviour is noticeable after exploding drum track, where original drum track 'refuses' to stay muted.

Anyone else seen this?

Max

With my MPC One (2021 black version) more than 32 tracks (33 and more) lead to crashing the machine when any of the tracks above 32 is muted from the mute mode (bank C and above). It crashed 100% times when I tried. Is anyone else experiencing this behavior?

DavidOakL wrote:With my MPC One (2021 black version) more than 32 tracks (33 and more) lead to crashing the machine when any of the tracks above 32 is muted from the mute mode (bank C and above). It crashed 100% times when I tried. Is anyone else experiencing this behavior?

Yes i can definetly reproduce that.
-> Create new blank project, create 33 additonal tracks. Mute track 33 -> immediately crash.
Firmware 3.5.0 on MPC Live II

Ive got a similar Issue with pad mutes, see the following post.

Issue: Pad mute crashes.
Can anybody reproduce this:

Any Pad Mute on all banks above bank A and B leads to immediatly crash.
That means: pad banks C, D, E, F, G, H are not mutable at all.
Happens in any project on any track, regardless if the pads are empty or not.
How to reproduce:
- Open "New project"
- choose any track
- go to pad mute. (not track mute!)
- mute any pad on bank A or B -> works
- mute any pad on banks C - H -> immediatly crash

tested on several projects, tracks and the default project.

MPC Live II - Firmware 3.5.0

Tried this on my Key37 and don’t experience a crash. In other words - it works for me.
Firmware 3.5.0

In the MPC Live 2 OS 3.x, when layering samples on one pad (up to four layers per pad), it appears that filter and envelope settings are applied globally to all layers on that pad rather than independently per layer. This means changes to the filter, attack, release, or envelopes affect all layers simultaneously, even if "edit all layers" is turned off.

Admin: Not a bug, this is just how it has and always has been, long before MPC3.

Any updates on time signatures or clips? Or is it still in beta phase?

Admin: Bug reports only please.

Using external older MIDI synths w my MPC One as my main sequencer. Some of these older synths dont have the ability to turn 'local' MIDI off.

Per the manual, the solution is to change the Monitor of the midi track to off, so the notes you play don't route back through the MIDI output and cause a MIDI loop which usually results in notes freezing.

But as of 3.5 and even older, it doesn't work. It still lets MIDI OFF notes through the MIDI OUT port and the MIDI track itself doesn't record the notes I play into the MPC.

Seems like an easy enough bug fix but it hasn't happened yet.

Is there an official site to report 3.5 Bug issues or is this the place?

Alwaysuptil1 wrote:Is there an official site to report 3.5 Bug issues or is this the place?

Akai ain't got shit to do with this site & they don't even give Tutor his props, even tho he wrote the MPC Bible, which have been a major help to many.

https://support.akaipro.com/en/support/ ... al_support