Syncing two traktors

[BentoSan]

What are you trying to sync it to ?

I have heard there is some kind of OSC handshake that has to take place first before the programs will start exchanging messages.

[jean_pierre]

ahh, a handshake - that could explain why it is silent. just as a first point of investigation, i was creating a clock source in QuartzComposer, but i also gave sendOSC a shot to see if i could get anything going - neither of course did.

sniffing the UDP traffic on the loopback and ethernet interfaces, nothing seemed to be coming from Traktor. the application is probably waiting for the handshake before it starts spitting out a master OSC tempo sync message stream, so that won't likely help.

what is the expected workflow for the OSC clock tempo syncing feature? two machines, two copies of 3.3, one as the master the other the tempo slave -- locally this doesn't work and i wonder if it works at all, which might explain why it was removed in Pro.
?

[BentoSan]

I havent had the opportunity to test it as i dont currently have two computers to test it on. After some reading on i though i have read that it was broken in later released of T3 but it did work once upon a time - not sure what release it does work and i cannot at this time confirm anything i am actually saying here so take that into consideration.

[jean_pierre]

fired up traktor 3.3.2 on two machines -- while i could select the OSC tempo master's local identifier as the second machine's tempo sync source, it didn't actually do anything. i might still be misunderstanding how the feature works, but changing the tempo of the master playback machine didn't do anything to the secondary machine nor did hitting the sync button on the secondary machine… nada.

might be able to sniff the handshake and see the OSC messages going to and fro now though.

[BentoSan]

Keep up the good work and keep us updated on any breathoughs that you can make. I moved these posts over to the right thread so people can more easily find any infomation thas uncovered.

[jean_pierre]

sending control data from the master traktor to the slave version seems to work and using wireshark to dump the packet payloads, the OSC control messages can clearly be seen -- tempo syncing remains elusive.

the tempo master appears to deliver periodic tempo/time related packets to which the slave ACKs. viewing the master > slave packet payload in ascii, it contains a "#time" portion, but i haven't looked into it much further than that.

[Flaekiface]

I just noticed this in the NI forum official Traktor Pro update thread:

The update will include the following improvements:

Fixes:

* Hardware Wizard functionality improved
* Deck filter resonance fixed
* Automatic "Load next track" function fixed
* Weird pitch readouts when syncing with stopped timecode fixed
* AUTO mode sync issues after radical pitch changes in timecode mode fixed
* MIDI clock fluctuations fixed
* Missing tracks after relocate fixed
* Modified import date after relocate fixed
* Non-functional pre-listen button fixed
* Missing color assignements in Mac finder after tag writing fixed
* Disappearing iTunes ratings after mouse-over fixed
* Missing tracks after interrupted playlist export fixed
* Broadcasting of preview player track metadata fixed
* WASAPI device-related crash fixed
* Reloop MIDI device detection fixed

This sounds promissing for the Midi sync option. Or what?

[BentoSan]

Its an improvement yeah, but its still better to sync how i have described because tempo changes will still throw things off really badly, so doesnt really make me excited.

[Flaekiface]

Yeah, I personaly use the manual way. Sticking to one BPM, and the phase sync by ear. Works fine and is actually lots of fun

[denisps2]

Just so you know, working on syncing two traktors now in TP 1.2 and it works quite ok!. Actualy it works the same as syncing traktor and maschine, So from what i have been testing it works, maybe it fluctuates for a milisecond too much, but still good enough. Still didnt test it live though.