I’ve had my MPC 500 for a couple of weeks and in my limited experience using it, I appear to be having an issue. I’m not sure if it’s a setting that needs changing, if the 500 is faulty, my limited RAM (I have 128MB on order) or if it’s purely a limitation of the 500 model.
In a nutshell, I have created a sequence and have it looping while I play with some samples over the top. When playing patterns over the top, it appears to be affecting the playback of other samples in the sequence.
More often than not, by pressing a pad to trigger a sample it is causing another sample in the sequence to end prematurely. Also, when holding down a pad the assigned sample only plays for 1 bar and then cuts out.
Here is a YouTube video of my problem
The set-up:
- 8 Bar loop.
- Six tracks.
- Default programs in memory.
- Loaded Strings (mono) program.
- Loaded program of mono samples from a TV show I’ve sampled.
- Tracks 2, 3, 4, 5, 6 Muted.
- No effects applied to any samples.
Explanation:
- 00:03 – Track 1 playing. Low strings.
- 00:19 – Un-mute track 2. Drums.
- 00:36 – Un-mute track 3. Unknown, could be empty!
- 00:52 – Un-mute track 4. Synth?
- 01:07 – Un-mute track 5. High strings.
- 01:24 – Un-mute track 6. Voice.
- 01:40 – Load strings into track 7.
- 01:47 – Demonstration of sample not playing to end.
- 02:10 – Playing pattern with strings, voice sample play to end.
- 02:20 – Playing pattern with strings, voice (track 6) sample cuts out.
- 02:35 – Playing pattern with strings, voice (track 6) sample cuts out.
- 03:03 – Demonstration of sample not playing to end.
- 03:14 – Stop loop, show full length of string sample.
- 03:22 – Start loop. Demonstration of sample not playing to end.
- 03:40 – Playing pattern with strings, low strings (track 1) not playing to end.
- 03:55 – Select program with voice samples.
- 04:17 – Demonstration of voice (track 6) sample cutting out.
- 04:25 – Stop loop and show full length of voice sample.
There’s quite a bit of unnecessary bits in the video and explanation, but I tried to capture as much of the problem as bearable.
I have updated the firmware from 1.10 to 1.13, which didn’t fix the problem.
Is this a hardware or software limitation? Is it likely to be fixed in a later firmware update, or can the audio processors only handle a certain amount?
I have dropped Akai Pro an e-mail explaining the above hoping that they can offer an explanation and/or fix.
Nora McGill
March 14th, 2008 at 4:30 pm
I had similar problems with the MPC 1000. Sometimes it would work alright then everything would go crazy for no valid reason. I sent mine back to where I bought it from for service and when it returned it was just the same. I heard your model number (500) has problems too. Sorry for that feedback, I thought it might be worth something.
Chris
March 15th, 2008 at 3:30 am
Hi, I have the same exact problem – did you solve it?
Kris
March 15th, 2008 at 5:51 pm
No, unfortunately not – Akai are saying that I am running out of polyphony, but I just can’t see that being the issue… The 500 has a 32-voice polyphony and I’m using nowhere near that amount in my demo sequence.
Wes
May 13th, 2008 at 4:36 am
Did you ever upgrade the ram? I have the same problem with my 500, and am wondering if the 128 upgrade will fix the problem.
Kris
May 13th, 2008 at 9:19 am
Hi Wes, I did upgrade the RAM and it did not fix the problem.
chris
May 19th, 2008 at 8:57 pm
did this ever get fixed ?
Mills
June 28th, 2008 at 10:07 pm
One sample (when triggered by hitting a pad) is essentially muting another that is playing from the same program.
You have the program set to monophonic, or the sample in the program set to monophonic. if you change to poly then you shouldn’t have this probelm……..
Peace
sam
October 24th, 2008 at 3:39 am
MAKE SURE THE MUTE GROUP FUNCTION IS SET TO OFF
poiz
February 26th, 2009 at 8:13 am
yoooo! that second last comment was it! BIG UP!
andy
September 17th, 2009 at 4:24 am
i have the exact same problem and i tried everything stated above: this problem occurs with only 6 drumsamples in memory playing at the same time and most likely if the reverb is assigned to one of those samples…this happens after playing for a few minutes…
nothing works except switching the effect off but then, effects can’t be used again, especially not the reverb, not even if only one sample is played with that effect… the mpc seems crashed….switching off the mpc and starting again with the same project: all fine again (for some minutes).
what is this sh*t???
Jaman
February 9th, 2010 at 5:45 pm
Hi!!!!! I had the same problem…. I solved it by turning every sample that was played the same time into monophonic and only the sample I was having the problem turned into polyphonic!!!! I hope it helps!!!!