2.11-2.13 Bug reports

MPC-Tutor wrote:
Pad perform is initially defaulting to bank C. Set to bank A and you shouldn't need to use the octave+ button hack.

And make sure you watch the 'Start bank at root note' settings cause that will screw up the note mappings too even in Chromatic mode since it starts it based on the root of whatever scale is selected. Pad Perform is totally **** on my MPC Live and is on all the time regardless of what I've tried to shut it off. I went back to 2.10 so I can turn it off again. Akai really blew this one apparently just so they could rush out those promo videos of Scott Storch looking like a Jersey Shore douche with his MPC Key.

Finally found and updated to 2.11.2... Clipping issue is NOT fixed...

Alright, reverted to 2.10, opened the same project, clipping gone.

Really hope this gets fixed soon as I was really looking forward to the update and new features. Might have to see if they will allow me a second trial period of OPX4 as I'd really like to explore that a bit.

MPC-Tutor wrote:

BostonGreen wrote:2.11 pad perform with baseline plugin bug.
Load baseline
Select pad perform
Pad 1 is automatically set to C2, to get it to go to lower than C0 you need to stab the octave+ button all the way up to C8, then back down again to get to C-2 (if you just try to go down without going up, it only goes down to C0, not C-1 or C-2)

Pad perform is initially defaulting to bank C. Set to bank A and you shouldn't need to use the octave+ button hack.

Hmmmmm, today it's working as it should do, it is defaulting to bank c, but as you say, pressing bank a fixed it. Controller mode defaults straight away to bank a.

Yesterday though I definitely double checked the bank.

Wonder whether 2.11.1 to 2.11.2 fixed it? Can't find any release notes for .2

In the old browser, when you exit a folder, the curser now jumps back to the top of the list of files in the previous branch.
Now when I first installed 2.10 it was the same, I then had reason to reinstall 2.10 it then worked as you would expect. I.e. the curser staying on the folder you’d just entered.
Now on 2.11 it’s gone back to as it was before. But intermittent, depending on what’s selected on the filter.

chrisroland wrote:would have to reinstall 2.10 to determine if this is actually a bug in 2.11 but since upgrading, MPC appears to no longer receive MIDI note info on the first step of my Pyramid sequence. mapped a chopped loop to pads 1-8 and Pyramid is apparently receiving/transmitting with MPC correctly on the selected MIDI channel. but when I program a note on Pyramid to trigger pad A01's slice on the first step of a sequence, the slice doesn't play. but only the first step. if i program the note on the next available step, the slice will play. this was working fine last night with 2.10.

insalled 2.11.2, and then reinstalled 2.10.1 to confirm that indeed this is apparently a bug (reported now). MPC One apparently will not play any triggered notes on the first step of an external sequence. -- which is not great if you have any MIDI events on the first beat, i.e., every sequence ever

Reverting back to 2.10, plug in synth sounds are messed up. Fixed by choosing different plugin and then re selecting right one. Drum pattern also spoiled but I can’t tell how. I just know it’s wrong

Bradley Smith wrote:Reverting back to 2.10, plug in synth sounds are messed up. Fixed by choosing different plugin and then re selecting right one. Drum pattern also spoiled but I can’t tell how. I just know it’s wrong

With the drum patterns.. You have to be careful because of the new default mapping. Now when you create a drum program its chromatically mapped instead of the old MPC layout. If you make a brand new drum program in 2.11 and put it on a track you created with 2.10, the notes won't match the pads and it screws everything up. You cant even copy events from one track to another and have it lay them out in the right spot. It shifts the notes around to match the new pad mappings and even with the same drum loop chopped in the exact same spots, it doesnt match up. Change the note mapping back to the 'Classic MPC' layout and they'll drop in just fine.

Im happily back at 2.10 because of the pad perform issue, so far it seems Im like the only one thats run into that. No matter what Pad Perform is always on here when I use a keygroup. Even opening old projects, as soon as I go to a track with a keygroup or midi instrument, Pad Perform turns on and there's no way to turn it off. Tested it out by setting it to chords and yep, no matter what it triggers whatever Pad Perform is set to.

Here's a brand new empty project, created a blank empty keygroup and not only are the banks all **** like everyone else sees, it goes right to whatever scale/chord Pad Perform is set to and stays on..

Monotremata wrote:

Bradley Smith wrote:Reverting back to 2.10, plug in synth sounds are messed up. Fixed by choosing different plugin and then re selecting right one. Drum pattern also spoiled but I can’t tell how. I just know it’s wrong

With the drum patterns.. You have to be careful because of the new default mapping. Now when you create a drum program its chromatically mapped instead of the old MPC layout. If you make a brand new drum program in 2.11 and put it on a track you created with 2.10, the notes won't match the pads and it screws everything up. You cant even copy events from one track to another and have it lay them out in the right spot. It shifts the notes around to match the new pad mappings and even with the same drum loop chopped in the exact same spots, it doesnt match up. Change the note mapping back to the 'Classic MPC' layout and they'll drop in just fine.

Im happily back at 2.10 because of the pad perform issue, so far it seems Im like the only one thats run into that. No matter what Pad Perform is always on here when I use a keygroup. Even opening old projects, as soon as I go to a track with a keygroup or midi instrument, Pad Perform turns on and there's no way to turn it off. Tested it out by setting it to chords and yep, no matter what it triggers whatever Pad Perform is set to.

Here's a brand new empty project, created a blank empty keygroup and not only are the banks all **** like everyone else sees, it goes right to whatever scale/chord Pad Perform is set to and stays on..

I just updated to 2.11 and my pad perform works fine as always.
I never use it but I read your problems and tried but I really have no problem.
I don't have any issue until now.
That's quite weird.
I never use external midi though.

Straker wrote:I just updated to 2.11 and my pad perform works fine as always.
I never use it but I read your problems and tried but I really have no problem.
I don't have any issue until now.
That's quite weird.
I never use external midi though.

Yeah I dont get it. When I go back to 2.10 and make a new keygroup program, Pad Perform comes on right away there too (I dont remember if it did that a few days ago before the update or not) but in 2.10 it has an OFF setting to just turn it off. In 2.11 here, it stays on and does not ever turn off. I've dug through the prefs I dont know how many times, played with Pad Color and Pad Mapping, its just stuck on. I haven't seen anybody else with this issue so I wonder if its just my MPC or what? When I reset the preferences somehow it remembers my WiFi stuff so that struck me as kind of odd. I might bust out the factory restore file and wipe it back to 2. whatever and try upgrading again. Maybe it needs a good cleaning out or something.

Monotremata wrote:

Straker wrote:I just updated to 2.11 and my pad perform works fine as always.
I never use it but I read your problems and tried but I really have no problem.
I don't have any issue until now.
That's quite weird.
I never use external midi though.

Yeah I dont get it. When I go back to 2.10 and make a new keygroup program, Pad Perform comes on right away there too (I dont remember if it did that a few days ago before the update or not) but in 2.10 it has an OFF setting to just turn it off. In 2.11 here, it stays on and does not ever turn off. I've dug through the prefs I dont know how many times, played with Pad Color and Pad Mapping, its just stuck on. I haven't seen anybody else with this issue so I wonder if its just my MPC or what? When I reset the preferences somehow it remembers my WiFi stuff so that struck me as kind of odd. I might bust out the factory restore file and wipe it back to 2. whatever and try upgrading again. Maybe it needs a good cleaning out or something.

Yeah I don't get it.
I would try to reinstall 2.10 and then 2.11 again, hoping that this solves the issue.
The strange thing is that it cannot be a hw problem.
So yeah, maybe a good cleaning of datas could help.
I updated via usb drive and with the file .img so I can say that this one works.
Strangely enough I just updated 2.11 and all seems to work fine so I still don't understand why they also made 2.11.1 and 2.11.2.
Quite confusing.

Monotremata wrote:

Bradley Smith wrote:Reverting back to 2.10, plug in synth sounds are messed up. Fixed by choosing different plugin and then re selecting right one. Drum pattern also spoiled but I can’t tell how. I just know it’s wrong

With the drum patterns.. You have to be careful because of the new default mapping. Now when you create a drum program its chromatically mapped instead of the old MPC layout. If you make a brand new drum program in 2.11 and put it on a track you created with 2.10, the notes won't match the pads and it screws everything up. You cant even copy events from one track to another and have it lay them out in the right spot. It shifts the notes around to match the new pad mappings and even with the same drum loop chopped in the exact same spots, it doesnt match up. Change the note mapping back to the 'Classic MPC' layout and they'll drop in just fine.

Im happily back at 2.10 because of the pad perform issue, so far it seems Im like the only one thats run into that. No matter what Pad Perform is always on here when I use a keygroup. Even opening old projects, as soon as I go to a track with a keygroup or midi instrument, Pad Perform turns on and there's no way to turn it off. Tested it out by setting it to chords and yep, no matter what it triggers whatever Pad Perform is set to.

Here's a brand new empty project, created a blank empty keygroup and not only are the banks all **** like everyone else sees, it goes right to whatever scale/chord Pad Perform is set to and stays on..

Yes, it now defaults to chromatic, which they've also changed to include the sharps # on every other pad.

This is the reason for every other pad being light dimmed, the dimmed are the sharps.

This is also the reason people thinking 16 levels stays activate when you leave it and also why old projects don't play correctly as every other pad has a sharp assigned to it. I think if you switch to notes, old projects should play correctly? Anyone confirm?

I'll have a play later hopefully, try and set Notes instead of Chromatic in my default empty project, hopefully it'll save those parameters

hey, weird, i can't seem to reproduce the keygroup pops and clicks bug you are all talking about! neither with my own keygroups nor factory\expansion ones, nor extracting sounds from drum programs.
i turn the keygroup to mono, record a sequence, play it back and it sounds perfectly fine.
my firmware is 2.11.2, do you think they fixed it in this minor update? don't get me wrong, i'm more than happy to not have it ehehehe but it seems strange that you have it and i dont.
mpc live og mk1.

BostonGreen wrote:Yes, it now defaults to chromatic, which they've also changed to include the sharps # on every other pad.

This is the reason for every other pad being light dimmed, the dimmed are the sharps.

This is also the reason people thinking 16 levels stays activate when you leave it and also why old projects don't play correctly as every other pad has a sharp assigned to it. I think if you switch to notes, old projects should play correctly? Anyone confirm?

I'll have a play later hopefully, try and set Notes instead of Chromatic in my default empty project, hopefully it'll save those parameters

Yeah you can tweak it and get it to the regular C-2 mapping, but the problem is that Pad Perform itself is always on. If this is the way its supposed to be now, they forgot to tell us. In 2.10 you can turn Pad Perform on when you want to play/record but then turn it off. In 2.11 its always on, which highlights whatever scale you have it set to. If you're trying to watch something play on the pads its impossible because now it ignores the pad color settings and when it plays it lights up every octave for that note. There's workarounds sort of but its annoying as hell. Setting it to Custom Mode (Im guessing they replaced the OFF option to fit this one in the space) and picking the C-2 mapping sets the pads to normal but then they're always lit and it still does the thing with lighting up every octave.

@Straker - trust me I've gone back and forth from 2.10 to 2.11 multiple times with every method of update possible at this point. Its just weird. Did the factory content restore and went to 2.11 again just now, still same shit though.

Monotremata wrote:

BostonGreen wrote:Yes, it now defaults to chromatic, which they've also changed to include the sharps # on every other pad.

This is the reason for every other pad being light dimmed, the dimmed are the sharps.

This is also the reason people thinking 16 levels stays activate when you leave it and also why old projects don't play correctly as every other pad has a sharp assigned to it. I think if you switch to notes, old projects should play correctly? Anyone confirm?

I'll have a play later hopefully, try and set Notes instead of Chromatic in my default empty project, hopefully it'll save those parameters

Yeah you can tweak it and get it to the regular C-2 mapping, but the problem is that Pad Perform itself is always on. If this is the way its supposed to be now, they forgot to tell us. In 2.10 you can turn Pad Perform on when you want to play/record but then turn it off. In 2.11 its always on, which highlights whatever scale you have it set to. If you're trying to watch something play on the pads its impossible because now it ignores the pad color settings and when it plays it lights up every octave for that note. There's workarounds sort of but its annoying as hell. Setting it to Custom Mode (Im guessing they replaced the OFF option to fit this one in the space) and picking the C-2 mapping sets the pads to normal but then they're always lit and it still does the thing with lighting up every octave.

@Straker - trust me I've gone back and forth from 2.10 to 2.11 multiple times with every method of update possible at this point. Its just weird. Did the factory content restore and went to 2.11 again just now, still same shit though.

I did read or watch something a couple of weeks back, saying OFF had been replaced with CUSTOM

Set it to custom, save as your default template and see if it reverts back to defaulting to off when you start a new project