Mpc 1000 slave midi timing?

Hey you guys, I am selling my roland mv 8000 becuase it will not keep good timing in slave and it will not let you do slave in mtc mode.
So my question is will the 1000 keep time in slave mode with logic pro. I know it has no mtc but is its basic midi clock good enough?
Thanks

It has been good enough for me so far (slave to machine drum, and sometimes master).

However, I'd get a few more opinions, and also, note that you can't stop and start the mpc on its own, (ie. tempo synced but 'out of phase') the way my machinedrum and evolver can. In other words, it only slaves up when you send a 'play' command from the master machine.

midi clock is just fine. just note that alot of programs will not allow slaving to the mpc (mpc as master) but slaving the mpc to programs are perfect with midi clock.

In other words, it only slaves up when you send a 'play' command from the master machine.

As long as my MPC1k is in song mode, it slaves just fine, even when I stop, ff and rewind.

i don't have to have it in song mode. i can have it on the main screen and it slaves with no problem. i could have it in slave and press stop and it will.

Same here. What I was talking about was SPP. Song position pointer info. In order for it to work with rew, ff, etc... the MPC (and any other drum machine) must be in song mode.

Otherwise, after you press stop and then press play again, it will be out of sync with your computer or other midi gear.

true

yeah, what i was tryin to say was just that if i have my master sequencer playing with mpc as slave, and I hit stop _on the mpc_, i can't just hit start again _on the mpc_, i must restart the master (machinedrum in this case) to bring the mpc back in sync.

its not really a problem, the only reason it would have been cool to do that is for my live show... sometimes i use that feature on my other gear to bring in loops that are ""in sync but lined up at a different point"", you dig?

i've noticed that when i record the mpc 1000 into logic as audio, say a 1 bar pattern, the beats wander a bit. if you look at them in the audio editor. for example,if you record a standard 4/4 pattern, the first 2 snares will be early it will drift a bit so the last 2 snare hits will be slightly late.if it were just down to latency, you could delay the audio by a milisecond or whatever, but the timing error is'nt consistent, wich is obviously a problem. the midi timepiece is a midisport 2x4 and the mpc is the only thing midi'ed up on logic 5.2 (p.c.). the last mpc operating system update said it addressed midi timing errors while in slave mode, can't help but wonder if they nailed the problem 100%.i've done this experiment many times, all the obvious factors( matching tempos,, ect.) have been addressed. anyone else noticed this? it's not by that much, but enough to be a problem to contend with.

[quote="mstrpig"]i've noticed that when i record the mpc 1000 into logic as audio, say a 1 bar pattern, the beats wander a bit. if you look at them in the audio editor. for example,if you record a standard 4/4 pattern, the first 2 snares will be early it will drift a bit so the last 2 snare hits will be slightly late.if it were just down to latency, you could delay the audio by a milisecond or whatever, but the timing error is'nt consistent, wich is obviously a problem.


That is exactly what I mean, does anyone know if they fixed this bug?

that's not the mpc. that's the settings in the program. protools and cubase and logic (to name a few) has been known to do that. you have to adjust some (i don't remember which) setting/configuration in the program. i know this particular issue is not latencey related. do a search in production techniques, i think that was covered some time ago.

i'm not gonna guarantee its not the mpc, but those midisports combined with logic/cubase whatever don't always give the most consistent timing.