[BUG] Sample auto-triggering in trim/program

Alright, this is a not hard to work around, but quite irritating bug.
(2xl, 1K)

At certain times, the mpc will enter an "auto-playback mode", where when parameters are edited, it will play back samples on its own. (better explained through examples below)

It seems to start sometimes when editing a NDC sample in trim mode, though I haven't completely worked out the pattern to this bug, it might start in other places. Once this "auto-playback mode" is enabled, these things happen:
In trim mode, whenever a new sample is selected from the list, or a new chop is selected, or the start or end points are changed, it will play the sample on its own.
This gets really irritating, like if you scroll through the list, it will play every single sample you scroll over, and trimming works really slowly because it is trying to replay the sample every click of the data wheel.
It also happens in program mode, when scrolling through the list to assign a sample to a pad, it will play EVERY sample on the way. Absolutely terrible if the pad is set to POLY.

The workaround I've found for it is you go to the LOAD screen, and the next sample you scroll to, it will do the same auto-playback, but won't do it again after that. (until the "auto-playback mode" is again entered in the trim screen)


Really annoying.

No its a great feature, you just aint cottoned on to that yet maybe. You wanna try using your ears (close your eye) to select sample. Do it, and see if you get what I mean. Don't look now

No, I don't see myself getting used to it, especially since it's clearly a bug, not an intended feature, since there is no direct way to enable/disable it, nor does it always happen.

Yes, I fine-trim samples by ear. But say the relevant sample doesn't start until a few second in, that part I would scroll to visually, then fine-tune it after. But it takes a while to get to that point when this glitch is happening, especially with a long sample. In trim, there's a slight delay between hitting the pad and hearing the sound, unlike the tight timing when it's assigned to a pad. This delay is longer the longer the sample is, and when the bug is happening, it has to do the delay for every single click of the data wheel.

And there's no reason at all that I'd need to hear every sample along the way when I'm scrolling to a particular sample.

Also, forgot to mention, this also happens when adjusting the tuning or chop number of a sample on a pad in program mode. So changing the tuning, it's like impossible when the glitch is happening on a POLY pad with a longer sample, because it just layers into a mess.

OK in trim , its just lag from CPU usually.
It is not a bug that they play as you change in program. Really you are having

sciguy wrote:And there's no reason at all that I'd need to hear every sample along the way when I'm scrolling to a particular sample.

yeah there is. To audition samples, but if you know what one you want, then just use shift + scroll to go quicker. Its a feature, not a bug.

sciguy wrote:This delay is longer the longer the sample is, and when the bug is happening, it has to do the delay for every single click of the data wheel.

So cut down samples to avoid this I think, or do you need silent lead into sample??

I can't believe that what I'm talking about is an intended feature.
How could a behavior with no clear method to enable/disable it be considered an intended feature? (And it does seem to turn itself on/off. The steps I mentioned are not the only times I've experienced this bug, just the ones that I was able to repeatedly cause the bug)

bliprock wrote:So cut down samples to avoid this I think, or do you need silent lead into sample??

Alright, I wasn't totally clear with my description of what was happening. By the "delay" I meant the CPU lag as you said. But when this bug is happening, it lags at every single data wheel click when changing the start/end points. Which makes scrolling through a sample really slow, since it constantly lags. When the glitch is not happening, I can trim as I normally would, scrolling the start/end points and auditioning by hitting a pad.

bliprock wrote:yeah there is. To audition samples, but if you know what one you want, then just use shift + scroll to go quicker. Its a feature, not a bug.

No, I would just hit the pad if I needed to audition it. Say I had 15 different long samples of single piano notes, and a drum sample I wanted was alphabetically after them. I don't need it to play each and every piano sample as I scroll to the drum sample, which is what would happen when the bug was happening.

this sounds like a either a hardware fault or a bug possibly related to NDC to me.

i've never experienced this bug, but i also never use NDC, so...


if you can reproduce this, send a step-by-step description to JJ. if you could make a video to demonstrate the bug to him, even better.

I definitely think it's caused by something with NDC. I'll play around with it sometime to figure out exactly what's happening.

It might have to do with playing back different chops in NDC too fast; since it's set up to play chops in trim mode as one-shot (rather than the note-on behavior for regular samples in trim), maybe it fills and glitches out some buffer or something, so when exiting trim mode, it still thinks it's supposed to play something.

I had that kind of bug in the sample list and in LOAD mode before but couldn't clearly identify why and do a step by step

Out of curiosity do you use Loop&hold samples?

nope, never used loop&hold. I don't even really know what it does.

It is not Hardware,NDC, or Loop&hold.As far as I can tell it is a random bug hard to reproduce.

sounds almost like a pad is stuck, with a constant NOTE ON
go into your sensitivity levels and see if anything is stuck there...otherwise i've never encountered this bug