Timing is off

Maybe I'm crazy but over the past few days I could swear that the timing of my MPC is either stuttering or skipping just slightly. I heard about second-hand and older MPC's needing some chips replaced after many years of use, has anyone ever had this issue?

Does this happen when using it as the master as well as being slaved?

Standalone and Master, I've never made my MPC the slave...

Did you check for internal Program Change Commands?

TSR

I did check that too! Hell I initialized the MPC as soon as I hooked it up to be safe. Let me be a little more specific... Is there a way to 'loosen' up the (TC)quantize on the 4k because I think the timing is just a little too precise...

Mike Boogie wrote:I did check that too! Hell I initialized the MPC as soon as I hooked it up to be safe. Let me be a little more specific... Is there a way to 'loosen' up the (TC)quantize on the 4k because I think the timing is just a little too precise...

What seq resolution are you using ie: 1/8, 1/16, "?

16th's mostly, sometimes I use 32nd's to freak hats. I use tripplets sometimes but not often.

Mike Boogie wrote:16th's mostly, sometimes I use 32nd's to freak hats. I use tripplets sometimes but not often.

Regardless of what you're using, I wouldn't worry too much about that, especially if you're going to drop the drums or samples to daw for further editing anyway.

Of course you want your stuff straight from the jump, but if it's near perfect before it goes to disk, then the rest can be worked out through dropping it in and tweaking it out on the daw (ie: track offset or whatever).

Im having this problem also. It seems like sometimes my 4000 works and then other times it doesnt...it wont catch notes, like say Im trying to put my snare at .03 in the sequence it wont catch. Then when I try to play my Motif in 16th note the notes are always off...Does anyone know how to fix this problem? Its irritating as ****, I never had this problem with my 3000.

I did get it figured out. Well not really. I kinda made some work-arounds.

1. Double-time sequencing

2. Like Dab said correct it later.

3. Turn the T/C OFF, or to OFF (96) and just experiment

4. Manually edit the hit in the seq edit menu (my fav)

Mike Boogie wrote: I heard about second-hand and older MPC's needing some chips replaced after many years of use

lmao - you really have no clue how digital electronics works, do you?

Yeah and you should talk to you MPC as well - read it stories at bedtime and it will be more responsive.

feline1 wrote:

Mike Boogie wrote: I heard about second-hand and older MPC's needing some chips replaced after many years of use

lmao - you really have no clue how digital electronics works, do you?

Yeah and you should talk to you MPC as well - read it stories at bedtime and it will be more responsive.

But don't feed it after midnight!!

feline1 wrote:

Mike Boogie wrote: I heard about second-hand and older MPC's needing some chips replaced after many years of use

lmao - you really have no clue how digital electronics works, do you?

Yeah and you should talk to you MPC as well - read it stories at bedtime and it will be more responsive.

How do digital electronics work Mr. Feline? LOL...I would like to know...do the MPC's go out?

Mike Boogie wrote:I did get it figured out. Well not really. I kinda made some work-arounds.

1. Double-time sequencing

2. Like Dab said correct it later.

3. Turn the T/C OFF, or to OFF (96) and just experiment

4. Manually edit the hit in the seq edit menu (my fav)

You know what...I think the problem might be that when you sync your MPC up it throws off the Clock of the sequencer ... maybe you have to initialize it to defaults to get it back right or something, I dont know, Im no MPC expert but something is definitely wrong if we are having the same problem.