Realigning MIDI Clock Delay on Cubase 4.5 (PC)

[Mushy Mushy]

Avoid the 500. Save a little more and get a 1000, 2000xl or ASQ10.
Those are the next cheapest MPC options.
You'll probably still want an inner clock though.

Part of the 500's appeal is the ability to run on batteries.

I think I might just suck it up and stump for the InnerClock.

[UltraJv]

Avoid the 500. Save a little more and get a 1000, 2000xl or ASQ10.
Those are the next cheapest MPC options.
You'll probably still want an inner clock though.

Part of the 500's appeal is the ability to run on batteries.

I think I might just suck it up and stump for the InnerClock.

Did you read my post about firmware update?

[Mushy Mushy]

Did you read my post about firmware update?

Yes I did. I wasn't ignoring you, just bouncing from meeting to meeting and replying in between

I do already have 1.1 on it.

The annoying thing is the delay varies every single time.

I've added delay to compensate and it's fine for a moment. Then I stop and start playback again, and the delay is an altogether different amount. It's just impossible to work with.

Another option is to buy an el cheapo mixer and not monitor the TT through Cubase.

[UltraJv]

Did you read my post about firmware update?

Yes I did. I wasn't ignoring you, just bouncing from meeting to meeting and replying in between

I do already have 1.1 on it.

The annoying thing is the delay varies every single time.

I've added delay to compensate and it's fine for a moment. Then I stop and start playback again, and the delay is an altogether different amount. It's just impossible to work with.

Another option is to buy an el cheapo mixer and not monitor the TT through Cubase.

Do you have direct monitoring enabled on your audio interface?

[Mushy Mushy]

Do you have direct monitoring enabled on your audio interface?

Oh now we're getting somewhere. The answer is I don't know.

Off to investigate

[Mushy Mushy]

Do you have direct monitoring enabled on your audio interface?

Oh now we're getting somewhere. The answer is I don't know.

Off to investigate

Just discovered what this is.... Very useful.
I'll have a play tonight. I'm using hardware effects, so it's not like I'll be missing any software effects by direct monitoring.

Fingers crossed

[Acid Mitch]

The annoying thing is the delay varies every single time..

This is something I could never get rid of when syncing to a computer via MIDI.
I never seem to notice it when syncing to a hardware based clock.
I get far better results with FSK or SMPTE. Inner clock also sorts this out.

I'll go into a bit more detail if I get a chance but I'm having trouble typing it in a way that won't cause more confusion atm, lol.

[Mushy Mushy]

The annoying thing is the delay varies every single time..

This is something I could never get rid of when syncing to a computer via MIDI.
I never seem to notice it when syncing to a hardware based clock.
I get far better results with FSK or SMPTE. Inner clock also sorts this out.

I'll go into a bit more detail if I get a chance but I'm having trouble typing it in a way that won't cause more confusion atm, lol.

You're bang on.

Sequencing MIDI seems to be relatively ok and workable.

It's only when I'm using the TT's internal sequencer via MTC that it goes all wonky.

[Mushy Mushy]

Re direct monitoring: If I understand it correctly, I will hear the TT as it enters the audio interface thereby eliminating all latency because it doesn't need to do the round trip back into Cubase.

I will still be able to record this though won't I? It's simply a monitoring change. I understand the actual recorded audio may be out of sync but I can simply nudge that back retrospectively.

Granted the easiest way to check this is to try it, but I'm at work now and am excited for an answer

[ZenPunkHippy]

Direct monitoring cures the latency problem: the input to the sound card is routed directly to the output for live monitoring, but it doesn't have anything to do with MIDI timing and therefore won't solve your problem.

Unfortunate as it is - buying utility gear like the Innerclock, which does not go "bleep bloop shhhhwwwaaargggnneeegglllrree", is kind of annoying but there is no other way to say this:

You are pissing in the wind trying to solve the MDI sync problem, and will go mad if you keep chasing solutions that don't help. I've been there, it's not fun.

Innerclock Sync Gen II solves this once and for all.

Peace,
Andy.

[Mushy Mushy]

Direct monitoring cures the latency problem: the input to the sound card is routed directly to the output for live monitoring, but it doesn't have anything to do with MIDI timing and therefore won't solve your problem.

Unfortunate as it is - buying utility gear like the Innerclock, which does not go "bleep bloop shhhhwwwaaargggnneeegglllrree", is kind of annoying but there is no other way to say this:

You are pissing in the wind trying to solve the MDI sync problem, and will go mad if you keep chasing solutions that don't help. I've been there, it's not fun.

Innerclock Sync Gen II solves this once and for all.

Seems like this is the only inevitable path really...,

I've just spent many many thousands of pounds on various other things so the ICSG will be a couple months off at least. And having an unusable TT sitting there winking at me in the meantime is quite painful indeed.

[Mushy Mushy]

Do you have direct monitoring enabled on your audio interface?

EDIT: No, it's still broken

Time for the Inner Clock then. Who needs food anyway.

[Mushy Mushy]

Absolutely positively fixed now.

Sending MIDI Clock directly from the 2626's MIDI out instead of the Midex8.

Seems pretty bank on now. Haven't been this happy since the Easter Bunny came

[UltraJv]

Cool, I thought it might be do able by changing what you clock from.