Midi Timecode into Qlab - via M Audio Uno - not working

[Gary Parke]

Question on MTC for triggering cues. I have a pro audio license and we are using an M Audio Uno with the latest driver for OSX 10.12.2 and the timecode window just says waiting. The cuelist has timecode triggers enabled and it also shows my device as the M Audio uno. When I roll timecode, my uno midi in lights up when timecode is running, but qlab just says waiting. Thoughts?

Running Qlab 4.0.5

[Rich Walsh]

Have you:

1. Checked MIDI Monitor sees MTC coming in?
2. Checked https://github.com/Figure53/TimecodeDisplay can decode the MTC?
3. (Selected the right Sync source in the Timecode tab in the Inspector for the cue list – I think you have, but worth checking)
4. Read this thread: https://groups.google.com/d/topic/qlab/KD5UJxIBv3E/discussion…

Rich

[Gary Parke]

Thanks for the info. The app that you linked to is not seeing midi either. I may investigate a difference device but we have used those little Uno's for timecode tracking to other devices. I do have smpte available via Dante and that is working for now so I may just use LTC via Dante but I am still going to try and get my MTC going.

[Jay Hogg]

Gary,

Watch how close your timing is if you switch between LTC (internal) and MTC.  MTC takes 8 quarter-frame MIDI messages which would put it 2 frames behind coming in via LTC, since LTC has to be decoded first then sent as MTC.  

I ran into this with custom software (not Qlab, mine) between an external MOTU converting LTC to MTC, MOTU audio in to LockStep (Figure 53 LTC to MTC) and Dante audio in to LockStep.  It is also affected by the audio incoming buffer size that typically defaults to 1024 (~21ms at 48khz).  

I need to put a request in for qLab to support skewing timecode by +/- X ms to account for the differences.

Jay

[Drew Dalzell]

That interface does not support MTC. You'll need to switch to something other than the M-Audio Uno.

Drew