Is It Just Me?

Spirez wrote:

Rozzer wrote:MTC is based on absolute time, days, hours, minutes, seconds, so syncing tends to be tighter. Midi clock is essentially just a bunch of blips with some tempo info.

So now I'm curious to know if ANYONE can actually use the 2500 as an MTC slave.

Cool, thanks for the tip.

So, which is best, MPC as slave or master?

Is one tighter than the other?

In theory no. Just depends how you want to work. I do both (well not with 1.21!) depending on what I'm doing. You can actually setup it up so both mastering and slaving works at the same time (so no matter if you press PLAY on MPC or Cubase, the other will sync up nicely).

Cool, i'll try that when they fix it then, can't be bothered to mess with 1.20 again, even though i didn't get the system test.

I take it to do this you just setup sync in and sync out on the MPC in MTC mode then have Timecode source set to MTC and also check the MTC out?

Do you usually check off the 'Midi timecode follows project time' box? If so does it work as expected, with the MPC looping and jumping to the same point that Cubase is set to?

I'm guessing that's something that would only have worked on 1.20?

And do you guys always have MMC send and receive on? This is just for transport controls right?

Spirez wrote:Cool, i'll try that when they fix it then, can't be bothered to mess with 1.20 again, even though i didn't get the system test.

I take it to do this you just setup sync in and sync out on the MPC in MTC mode then have Timecode source set to MTC and also check the MTC out?

Do you usually check off the 'Midi timecode follows project time' box? If so does it work as expected, with the MPC looping and jumping to the same point that Cubase is set to?

I'm guessing that's something that would only have worked on 1.20?

And do you guys always have MMC send and receive on? This is just for transport controls right?

Yep you pretty much got it. I don't think I have 'Midi timecode follows project time' enabled. It seems to work without it, but try experimenting.

I don't use MMC, its not necessary when using MTC.

btw... has anyone actually contacted Akai regarding the MTC sync problem in 1.21? I've just emailed them. I know they never reply, but they might read them....

you're best of phoning them from what i;ve heard.


i wonder if the system test error was a spin off problem from when they added MTC.

OK, I just spoke to tech support in the UK. Apparantly someone else phoned about the MTC sync issue a few days ago, so they're looking into it (which I guess means sending emails to Japan for confirmation). He said he'd ring me back when he got news.

If anyone in the UK wants to phone tech upport, their number is 01252 353 850, and the man to speak to is Ian.

Rozzer wrote:
btw... has anyone actually contacted Akai regarding the MTC sync problem in 1.21? I've just emailed them. I know they never reply, but they might read them....

I contacted them. They are aware of the issues with MTC and as well as the Note Repeat problems.

I spoke to Ian in UK support a coulpe of days ago and reported the MTC issue and frozen transport fault.

Also ponited him towards the forums so he could see how this bug was effecting other users and get a better understanding of the senarios and symptoms.

Im awaiting a call or email from him today if anything interesting comes about I will post up

Rozzer wrote:Apparantly someone else phoned about the MTC sync issue a few days ago,

maxim1 wrote:I spoke to Ian in UK support a coulpe of days ago and reported the MTC issue and frozen transport fault....

Ah it was you then

Rozzer wrote:MTC is based on absolute time, days, hours, minutes, seconds, so syncing tends to be tighter. Midi clock is essentially just a bunch of blips with some tempo info.

So now I'm curious to know if ANYONE can actually use the 2500 as an MTC slave.

There really isnt any tempo info per se in midi clock. It just sends 24 pulses per quarter note and the receiving device advances its sequencer as it sees these pulses. The faster the pulses the faster the resulting tempo and visa versa. Its the speed of the pulses that determine the tempo, not an specific tempo message itself.