Basic timecode

[Lars Huijgen]

Hello,

I am fiddling around with timecode at the moment but i don't seem to get it working. I've got an M-audio uno and Qlab 3 running an timecode and the device tells me it's working but i can't get it working in the desk itself.
I have an cue list set up and I selected MIDI as an input with the right frame rate. But when I play the song (which is linked to the timecode) the desk doesn't tell me it's receiving any. It says: Recording 00:00:00:00 and that doesn't change. Am I missing something obvious?
Instead of Qlab I also tried Reaper as an timecode source.
The desk is an Titan Mobile which runs V8.0

Hope you can help

[niclights]

Are you running MIDI into the physical MIDI port on the Titan Mobile? It will not work any other way.

[Lars Huijgen]

Yes I have an physical cable attached to the midi in port

[Lars Huijgen]

i tried it again with an Windows laptop today and from there it works like a charm. So the output on my mac is against me. Is this an common problem or does my computer have an problem? It doesn't work on both Qlab and Reaper.

[gis]

Never had any issue with running midi from my MacBook Pro, with 10.6.8 and various versions of Reaper, to Titan Mobile.

Check if MTC is outputting right with http://www.snoize.com/MIDIMonitor/.

[Lars Huijgen]

It seems like the output works normal. I am guessing that it's an setting on the desk itself. Would it be possible for me to send the show file to someone to check it out. I am sure i am missing something small.

[Lars Huijgen]

Oke I have another question, Avolites says that Usb midi is not supported but does that also mean that my setup which is now: Mac (usb out) -> m-audio uno (midi out) -> desk (midi in) is invalid?

[gis]

No, it means Avolites software gets midi only from the MIDI input on the console.

[Lars Huijgen]

I figured out the problem, it was the driver for the midi interface. I installed it but for some reason it deletes itself after shutting down or closing my laptop.