Does anyone else's 1000 occasionally not trigger samples

Why is everyone treating this like a non-issue?

I have noticed this, and then some.

While I have only had a sample fail to play ONCE, I have also had to scrap a sample that developed nasty artifacts all on its own... I literally played a seuquence, hit stop, and played it a few moments later after making no changes, and the second time, my sample had a strange clipping sound in the middle of it.

I have also had a sample file get corrupted during the process of loading it from the cf card. It happened twice to the same sample. After it failed to load to the proper pad, I checked it in the card, and it had somehow been reduced to a mess of white noise.

I think people treat it lightly because the OS is so new, and there are bound to be bugs. I am sure they will be addressed.

it also may be that every DAW out there is much worse in terms of bad behavior. at least, every one ive used (i've used most, definitely not all tho).

no doubt about it - samples, or anything, getting messed up on the storage media (cf card, hard drive etc) is very bad.

when it gets messed up in the RAM, eh no big deal. just reload the sample (assuming the card has no major corruption).

DP's been much worse for years. a juno 106 acts REALLY strange in comparison but it's dismissed because it's "analog."

mine does this as well. a couple of times during a sequence the sample has just given out and went blank for a bar but comes back next bar. not a big deal but yeah its a glitch.

Doesn't it bother anyone how some people don't experience this problem... I guess that the grass seems a little greener to me for some users.

I agree with you. I don't see problems, but hardware should not glitch. period. crappy manufacturing or design if it does. I don't subscribe to the "oh well, it failed, I can just reload my sampled from CF" camp at all. Mostly because I do alot of jams & live play, so there's no room in my book for failure. Studio, *maybe* you can say it's acceptable. If you record in your own studio, and don't pay for studio time. If I experienced what you see, I'd be all over Akai.

I am basically in a position where I am still able to make a legitimate argument to get my money back. If this is not a software issue that can be resolved, then I am definately returning it. From what I can gather, it is really starting to seem like a hardware problem.... it does not make a lick of sense how some people don't experience this. I "really" wished that it would function flawlessly, but for now, I am going to have to leave "mpc land" until I can be confident in an mpc that is in my price range.

I'm treating it like a non issue since I can't seem to isolate it, or for that matter, repeat it since I first posted about it.

If it kept on happening I'd get mad, but so far it hasn't really become an issue.

... and I like my MPC too much to try to get my money back.

has anyone tried changing the length of the sample or the decay time to see if that helps ? it sometimes fixes things when the sample is retriggering all the time...haven't had the problem on the mpc (yet) but it's happened with other samplers...

returned it.

best of luck to the rest of yall

i just got my mpc1000 a couple of days ago and have noticed this bug as well. does akai have official channel for reporting bugs. it happens only occassionally with hours of use so it is not devastating. but it should be dealt with by aka ASAP.

Ive only noticed it happen to me when Im in song mode...Every once in a while it will not trigger a sample if its on the 1 beat of the next sequence in the song...but this only has happened to me 1nce or 2wice, doesnt seem to be a devastating problem for me at this point...

"does akai have official channel for reporting bugs."

Not that I know if. I am not sure if they would even admit to it.

"it is really starting to seem like a hardware problem"

Not likely on the MPC1000. On the former models, possibly, but not the MPC1000. Sginificant differences in the design.

Does it have something to to do with Polyphony (how many voices or sounds it can play at once)?

Mine does it every once in a while - however when it's time to record it works fine -

Maybe memory? I dunno

I've written in another post about pad sensitivity, and this just makes me think the quality control is not as good on the 1000. It's a great design, but I tried several and couldn't find one where the pads all felt the same. Even with the "hidden" velocity page I couldn't get them even. I even tried one at a store in NYC where the top four pads only triggered full velocity even with full level off. The velocity didn't come close to evening this out. The one decent unit had a ticking sound coming from the didgital out. Some kind of clock noise I couldn't get rid of. I'm bringing it back to Guitar Center. I don't know if I have the patience to try anymore right now. I might wait a month or two for another batch. I should never have sold my 2000XL.