David

I have a transport object running in a Max For Live patch with a [==] object testing the third output (ticks) and triggering the creation of a MIDI note when ticks ==0. when I record the output in a track in Live I find that there seems to be a lag of about 15 ticks before the note is actually recorded. Is this expected behaviour? Is this lag time likely to be constant or will it be likely to change under differng conditions? I can adjust my test of the [transport] ticks outlet so the note is triggered 15 ticks earlier, but I wonder if anyone can suggest are any more elegant solutions. I want to create MIDI messages at specific times. Thanks.

midi-lag-time

How is the transport triggered? Are you using metro with quantize attribute?

The transport was triggered by a metro with a message box saying "1 ticks" into the metro's right inlet. I tried using the metro as follows [metro @quantize 1 ticks], but the lag is even greater that way. Also, when using the quantize attribute the transport tick output starts missing values at higher tempos, which is not going to be any use for triggering MIDI messages at specific tick values. Is it unrealistic to expect to be able to test ticks values sequentially in this way? Should I be fiddling with the scheduler settings?

I have also discovered that the lag increases as I increase the tempo.

Make sure that 'Delay Compensation' is activated in Live.

Yes Delay Compensation is activated, although I can't see what that could have to do with it. I have worked around this delay with a number box and an addition object. Thanks for your help.

MIDI lag time