Page 1 of 1

MIDI-clock issues

Posted: Mon 9 Nov 2020 09:39
by sektoderselters
Hey folks,

I have a problem transmitting the BPM-Info via MIDI-clock to lumidesk.

I use traktor in its newest version and lumidesk on the same laptop. As a virtual port I installed LoopBe1. According the MIDI-monitor Traktor sends its MIDI information correctly to the virtual MIDI-port. Lumidesk allows to select that virtual MIDI-port as MIDI clock in its setting but obviously receives no data (no BPM-signal).

What am I doing wrong? Any help is kindly appreciated.

Kind regards

Re: MIDI-clock issues

Posted: Mon 9 Nov 2020 12:06
by lumidesk

did you select the Midi Clock option under General settings -> General ?

Thank you

Re: MIDI-clock issues

Posted: Mon 9 Nov 2020 22:18
by sektoderselters

yes - MIDI clock is enabled and the correct port is selected.

Kind regards

Re: MIDI-clock issues

Posted: Tue 10 Nov 2020 09:24
by sektoderselters
Hey there,

so - I somehow managed to get it working ...

There is a very tricky thing of setting it up - to shorten the long story:

It only works on my system when I set up the configurations correctly an THEN RESTART lumidesk. As soon as I click on the "configuration"-tap on lumidesk sometimes an hourglass appears as my mouse-pointer (lumidesk seems to be working and does`nt respond for a couple of seconds) and then lumidesk looses the connection to the MIDI-port. Thereafte it is not possible to get it working again but to restart lumidesk.

Besides it seems to me that there is a mix-up with the MIDI options in the "general settings"-tab. In order to work I had to check the second MIDI-option (MIDI output device) and NOT the third MIDI-option (MIDI clock), what I supposed.

Please be so kind and take a closer look at that - it seems to me like a bug and it took me hours of troubleshooting ;) and during a live performance it is a crucial problem.

Kind regards,

Re: MIDI-clock issues

Posted: Tue 10 Nov 2020 14:42
by lumidesk
Hi Robert,
thank you for the feedback,

we will check that and should be fixed with the next release