Firmware 2.8 - 'Assign Slice to Pad': 2 major bugs

Bug 1:

SAMPLE EDIT > CHOP > THRESHOLD
Select a slice (e.g. slice 1)
CONVERT > Assign slice to pad > Non destructive slice

This should assign the selected slice to the chosen pad in the chosen program, but it's instead just assigning the whole sample (i.e. with the pad set to slice:ALL (instead of Slice:1).

Creating a new program with slice or pad parameters is fine, it's just 'assign slice to pad' that doesn't work

Bug 2:

Chop as above, but this time choose:

CONVERT > Assign slice to pad > Pad Parameters

This initially appears to work, however the MPC has actually now permanently changed the start/edit points of the original sample rather than just changing the pad params in the program. Go to TRIM and make sure 'slice' is set to ALL and the entire sample is now changed to match that pad param slice you did.

So this bug is actually changing the core start/end points of a sample and hence all instances of it on any pad where it is currently used.

MPC-Tutor wrote:Looks like a bug in CHOP mode unless I'm missing some new preference, but this was working previously.

SAMPLE EDIT > CHOP > THRESHOLD
Select a slice (e.g. slice 2)
CONVERT > Assign slice to pad > Non destructive slice

This should assign the selected slice to the chosen pad, but it's instead just assigning the whole sample with the pad set to slice:ALL (instead of Slice:2). Doesn't work if you set pad parameters either.

Creating a new program with slice or pad parameters is fine, it's just 'assign slice to pad' that doesn't work.

Uhm. Not nice.
I also have the feeling instant track mute is messed up.
My projects that were working fine until 2.6 (I didn't update to 2.7) now have problems on 2.8 with long samples on drum tracks that don't get muted when I change sequence where those tracks are muted. The samples keep playing, they are same length of the sequence so it's not an overlap. They just get retriggered even if the track is muted.
Also they don't play on first sequence if I switch them on at the middle of the sequence, they start playing only at the beginning of the next cycle.
It was not definitely like that until 2.6, the projects are the same and so something changed.

Updated my original report as there are actually two bugs here, second one is fairly major IMO as it's changing the core start/end points of a sample rather than just the pad params in the pad.

MPC-Tutor wrote:Updated my original report as there are actually two bugs here, second one is fairly major IMO as it's changing the core start/end points of a sample rather than just the pad params in the pad.

Problems coming out as you use 2.8 daily.
I think 2.8 was not checked completely as it should before releasing.
Also qlink overlay has some conflict with data dial on track mute and main page. Sometimes it doesn't work after you use qlink overlay.
But sometimes it works.
Unpredictable.

chapter 19 in the MPC Bible uses 'Assign Slice' to build a drum kit with select slices to a specific layout using non-destructive slices, so that's going present a challenge to get that 2.8 compatible

workaround for the moment is to use it anyway then go to PROGRAM EDIT > SAMPLES and manually change SLICE: ALL to SLICE:2 etc on each pad. Meh.

Other option is to 'convert > new program using slices' (which works fine) and then use the new COPY PADS option to copy the desired slices to a separate blank program, that way you can build the sliced kit with the pad layout you prefer.

Workaround for the pad parameter bug is to not use it at all

Eeeeek yep, 'assign slice to pad' in general is broken. I had to go check right now because I use the convert->pad parameters all the time..

Luckily its NOT broken if you convert the whole thing using 'New Drum Program Using Slices' with Pad Parameters. Thats the function I use all the time so thank god I can still work for now. You just can't assign it one slice at a time for now, have to do the whole thing at once. The work around of going in and manually changing the slices works fine too so theres that at least.. Thats gonna be a pain in the ass when you're in a hurry and forget you have to go into the program and change the slice assignments haha.

Another workaround, work in SAMPLE EDIT > PROGRAM mode.

Slice your break as usual but don't convert.
Blank program, assign your break to say, pads A1 - A4
SAMPLE EDIT > CHOP > PROGRAM
Hit pad A01 and set SLICE param accordingly (e.g. set a. kick)
Hit A02 and assign the snare slice and so on.

Of course, this would have been picked up before release if Akai had actually released this as a beta to the public beta forum that we all signed up for (but now appears abandoned).

Just noticed another quirk as well.. So when you do the Convert->Assign Slice to Pad method.. You go in and change each slice in Program Edit back to Slice 1, Slice 2, etc...

In the Program Editor, the program I created using 'New Drum Program from Slices' the Slices are set to 'PAD' not the actual slice number.. If you go into the 'problem' program and set the slices to 'Pad' it **** them up again. In this program I have open, slice 1 set to 'Pad' is now the entire loop (I'm messing with Aerosmith's Walk This Way hehe), slice 2 gets set to the parameters for the first slice, slice 3 is actually the second region, etc.. Works perfect if you set them to the actual slice# but something is definitely up with the pad settings.

I must have signed up for the beta program about 20 times, both when I had my MPC Studio Black and another 10 times or so after I got my actual Live last year. Never got a single response from them, and I would've been their darling tester last year when I wasn't working and was playing with this thing for 12+ hours a day hah.

Monotremata wrote:J
In the Program Editor, the program I created using 'New Drum Program from Slices' the Slices are set to 'PAD' not the actual slice number.. If you go into the 'problem' program and set the slices to 'Pad' it **** them up again. In this program I have open, slice 1 set to 'Pad' is now the entire loop (I'm messing with Aerosmith's Walk This Way hehe), slice 2 gets set to the parameters for the first slice, slice 3 is actually the second region, etc.. Works perfect if you set them to the actual slice# but something is definitely up with the pad settings.

I'm not seeing that, I'll have to check this properly when I've not got my wife shouting at me for working on the weekend!

When you get a chance go back in Sample Edit too with the 'problem' loop and see if it starts messing with anything.. I went back into sample edit, and was just scrolling through the slices and somehow it changed slice 1 to start at like -1 and end at 0, slice 2 was the actual first slice of the loop. Further scrolling through the slices and trying to 'fix' them did some weird stuff. At one point, I had it chopped to 8 regions. All 8 slices were crammed into the area that used to be Slice 8. That last eighth note region, now had 8 tiny micro slices all crammed in there. I got it to reset by going back to Trim and redoing the Chop by Regions but I bet once you mess with the program it'll start screwing up again. This ones weird heh.

Did you already report this directly to Akai? Either beta forum or via other ways?

nicolasbulb wrote:Did you already report this directly to Akai? Either beta forum or via other ways?

Yes, through the software, on the public getsatisfaction forum and the beta forum although that now seems abandoned by Akai so you start to feel like an idiot spending your time on there.

I’ve posted as well on their Instagram account. The more idiots we are reporting, the wiser we will become.