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 NearTao Mon Jun 22, 2020 8:48 pm
What's up fam?!

Curious if anybody else can reproduce this on firmware 2.8 in standalone mode...

16 LEVEL any pad you want, set ORIGINAL PAD to 16. Pad 1-4 all play the same pitch.

16 LEVEL any pad you want, set ORIGINAL PAD to 1. Pad 13-16 all play the same pitch.

Maybe this is previous version of firmware behavior... but seems weird to me that some of the 16 LEVEL settings do not give you... 16 Levels.

EDIT: Upon recording the pads... and investigating the List Editor...
For an ORIGINAL PAD setting of 1... MOD TYPE of Tuning... but pads 13-16 produce tuning of all 120. So apparently it cannot go above 120 to tune

For an ORIGINAL PAD setting of 16... MOD TYPE of Tuning... but pads 1-4 product tuning of all -120. So apparently it cannot go below -120 to tune.

My question then is... why does it allow you to select ORIGINAL PAD below 4, or above 13? *shrug*
By wavejockey Tue Jun 23, 2020 7:07 am
isn't this tied to the original key the sample is in?
+ the tuning of the pad the sample is on

if the pad is already tuned +24 or -24 keys, then the 16LEVELS tune cannot go further (than 3 octaves ?)

there's a cap there
User avatar
By NearTao Tue Jun 23, 2020 11:13 am
This is even with no tuning applied to the sample.

I suspect it is just a signed byte limit, but kind of weird that you cannot use the entire note range offered by the pads. Oh well. Keygroups can do what I want.
By 40Beatz Tue Jun 23, 2020 12:39 pm
I think thats Normal Operation with the Newer MPCs. I can only guess that The Live/X can only 16 Level an Octave worth of Tuning. Which is 12 notes. Thats why the Last four pads(13-16) produce the same Tune.

You got two options... Set the Orignal pad in the Middle(Pad 8 ) so you can get a kinda full Octave Range....

Or......Open the Sample in a Keygroup Program. Boom! Then you'll have to Whole Key Range
By Eyalc Tue Jun 23, 2020 12:49 pm
I’ve never see this issue. Will try to recreate it. But agree - keygroups are generally more flexible anyway.

Has Akai responded publicly to any of these 2.8 issues? The list of issues is getting LONG. Have they just remained quiet?
User avatar
By NearTao Tue Jun 23, 2020 1:12 pm
I suspect that this has been in all of the firmware versions... and not introduced in 2.8, I just happened to notice it here because I was trying to squeeze a couple more notes out of 16 LEVEL than I normally do. To me it appears that it isn't directly a problem with 16 LEVEL TUNE, and actually a restriction on the MOD TYPE Tuning only has a range of -120 to 120 (Which fits in an 8-bit signed byte), but to do this as I would expect would require a MOD TYPE Tuning range of -150 to 150, which would require a 9-bit number... which would likely need a 16-bit data type.

My guess is that Akai is not going to fix this... so this thread can likely be closed... but it does make me scratch my head at the implementation.
User avatar
By mr_debauch Tue Jun 23, 2020 9:21 pm
yeah i always wondered why there was that limit... and not just on the live, even the 60 had that but the machine could go lower than 16 levels in pitch when you adjust it there so it is kind of a head scratcher.