Titan Mobile Not recieving MTC

[Atomiclock]

Hi all,

I may have just misunderstood the capabilites of the mobile but I have been trying to send MIDI timecode to my titan mobile via loopmidi and cannot get it to see the timecode.

I can see the messages being recieved in LoopMIDI and checked this again with MIDI OX but titans USB expert wont register any Raw incoming midi messages.

Not sure if it has to be a physical 5 pin midi cable connection or if im missing something.

Aim is to send MTC from ableton for vis programming at home.

Any help would be much appreciated!

Cheers

[icke_siegen]

There were some changes in the latest Windows update which affect the MIDI stack; basically it is now more strict to errors which have been tolerated for many years before. Blame it on whoever you want

In the case of loopMIDI and Titan there are two things:

1. Titan (up to v19.1) uses an external MIDI library which had a bug which is now preventing MIDI from working, and which has recently been fixed.
2. loopMIDI uses a virtual MIDI port which isn't detected by Windows in time

The solution for the first issue is in the process of being integrated into Titan; for a fix upfront and for more information and links see https://avosupport.de/wiki/downloads/midi-fix - download the program and run it once.

For the second issue - which has even less to do with Titan than the first one - you may

1. open windows commandline with administrative rights and do net stop midisrv, net start midisrv, or
2. wait for loopMIDI to be fixed, or
3. maybe wait for Windows to get a fix for this, or
4. use another program like loopBE1

[Atomiclock]

Hi and thanky ou for your reply.

Ended up being soloution 1 just needed the MIDI update for titan. Ive also found that if Loop MIDI doesn't work go to:
Windows tools-->services-->windows MIDI service.
Then stop the service and run the service.

This seems to kickstart it into recognising Loop MIDI again.

Thanks very much for your help!

[icke_siegen]

Thank you for the reply. Yes, you are 100% correct re. restarting the midisrv service, that's exactly what I suggested with the console commands. Explanation by Microsoft: it's the order in which the service is started and virtual MIDI ports are created. Some people even tried automatically restarting the service a certain time after system restart...

Anyway - glad that it works for you now.