Inaccurate midi sequencing with VIs using external sequencer

[Actionmusic]

This is really bugging me, any pointers from the DUC welcome. I'm running 7.3.1 HD latest CS on a g5 2.7, Midex 8 interface.

I'm using my MPC 4000 sequencer to trigger virtual instruments including Structure by setting up a couple of instrument tracks and assigning a specific input to each track eg MPC out 1 to Structure, out 2 to Minimoog VI etc. Tools transport is not running, they are just sitting there being triggered by the pattern on the MPC. The only way i can get any kind of accurate sequencing is by having the buffer at 128 and 1 processor on. Even with this setup the timing is very loose. A simple MPC straight 16 hihat pattern seems to lurch, or change each time of the loop whether it is on Structure or Minimoog or whatever. The same MPC out to a hardware synth shows the timing to be rock solid.

So my question is anyone else doing this ? When i record midi and play back internally in tools all is as expected but i'm trying to use the MPC as my main sequencer and print the audio live to retain the feel and the ease of this way of programming. Any suggestions what to do? An interface issue?

[Lee Blaske]

So my question is anyone else doing this ? When i record midi and play back internally in tools all is as expected but i'm trying to use the MPC as my main sequencer and print the audio live to retain the feel and the ease of this way of programming. Any suggestions what to do? An interface issue?

I think you're just going to stack up cumulative timing errors that way. You could always use something like Beat Detective to correct the flaws, but you certainly wouldn't save any time.

If timing is important, it's best to work within your DAW application, and put the MPC out to pasture.