So i've been trying to get this to work for a while:
- 2 MacBook Pro's
- Traktor 2
- 1x Audio4DJ, 1x Audio8DJ
i've got the whole midi clock sync to work last week on the 2 laptops using the midi ports from the Audio8 and my Maschine. Only bad thing is the fluctuation of about 0,2 bpm between the two systems which gets worse after a while causing both Traktors to lose sync after a while.
This made me do some more research and i found out that you can send midi trough ethernet and even use a different signal than the usual Midi Clock, called Midi Time Code. This quote explains the difference pretty well:
This makes it seem obvious that MTC is better than MBP, especially considering the lost packages and resyncing etc.MIDI Beat Clock
The MIDI Beat Clock signal works pretty simple, it sends 24 tick signals for each quarter note. A start signal is send to indicate when to start playing. From that moment on, the MIDI slave has to keep track of the ticks.
The problem is that small delays in the tick signal cause speed (BPM) variations. Missing ticks can make a MIDI slave run out of sync. The BPM value tends to jump around all the time with sometimes deviations of over 2 BPM.
Once the MIDI slave has gone out of sync it requires a re-sync. There is no way to detect that it is out of sync because the MIDI Beat Clock uses a relative value that every slave needs to keep track of.
A re-sync has to be done manual. But applications like Ableton Live will simply wait for a new start signal to be triggered. When the MIDI Beat Clock master is Ableton Live, there is no way to retrigger the start signal without interrupting audio playback.
MIDI Time Code (MTC)
The MIDI Time Code signal sends an absolute time position according to the SMPTE Time Code standard. This means that at any time all MIDI slaves know where they should be. Even if there is a short interruption, the next correct SMPTE Time value will tell the software where it should be.
Because MIDI Time Code is not telling anything about beats you can sync MIDI slaves with different BPM values. Thus every MIDI slave maintains its own tempo which is synced to the MIDI Time Code position of the master.
Problem is: MTC isn't supported by Traktor atm. The writer of this article is trying to make it work inside Ableton, which does support it.
Wouldn't it be great to get this to work in Traktor? No more 0,2bpm fluctuations, no more loss of midi sync out of the blue etc. I can't seem to find anyone who has gotten it to work this far though.
So can any of you guys help me out? Anyone who has an idea how to get this to work?