Just checking if eveybody gets this...

If there's a sequence playing, I get really bad timing lag going to and leaving the sample edit and record windows.

Just me?

King_Vitamin wrote:If there's a sequence playing, I get really bad timing lag going to and leaving the sample edit and record windows.

Just me?

Hmm, not really, but I do get lag in other places when playing a seq, particularly when triggering samples in the Trim page. It seems to make the main sequence glitch. No biggie though really.

yep starts to lag badly if i go to trim mode while a sequence is playing...
i haven't had a chance to upgrade from the os that came with the machine yet tho

No lag here, but sounds drop out and continue triggering again as soon as the page is loaded. One shot phrase samples for example get muted and retriggered not until the next loop.

Timing stays exactly in sync however, for my rhythmic feeling. OS 1.20.

Maybe check if that's the case with you as well...


Stilo.

I just wish they'd update the damn OS as 1.20/1.21 are unusable for me if I want to record into Logic. Back on 1.10 here until they sort the midi issues out.

I'm on 1.21 btw and no, the timing does not stay in sync for me.

pb-sh wrote:
I just wish they'd update the damn OS as 1.20/1.21 are unusable for me if I want to record into Logic. Back on 1.10 here until they sort the midi issues out.

Are you talking about MIDI sync? You can always just record the MPC into Logic as audio until this function is fixed/improved. However...MIDI is even worst in 1.10. 1.10 is completely unuseable when sequencing MIDI instruments..

I'm talking MPC as slave recording audio into Logic.

With the midi settings (just using midi clock) in 1.20/1.21, when I record into Logic the first beat of the sequence plays at the beginning of the count-in bar. Then I get silence (which I should on the count-in bar) then there's no beat when the recorded bar should start and it picks up playing the audio (ie the next beat of the sequence) 'approximately' where the next beat should be. Except the 'approximately' is earlier than it should be.

So the beat on the count-in bar is wrong and the timing of the rest of it is ****. If I'm using 32ms latency the sequence should appear to be 32ms late when recorded, not x ms early.

Since I record drum hits on separate tracks (ie one for kicks, once for hats etc) it makes working with 1.20/1.21 a real pain.

Using 1.10 it works fine, exactly as it should, ergo it's the MPC Midi settings that are **** (for me) since 1.20/1.21.

It could be me at error, but I'm 99% sure it's not. But if someone can pin down what I'm doing wrong here and prove it's me at error and not the MPC software, I'd be grateful.

Why use midi clock and not MTC ?

I can't get MTC to work properly despite rtfm'ing Logic and the 2500 manuals and setting things up exactly as they describe.

Guys...let's not turn every thread into a MIDI sync thread, ok?