Syncing two traktors

I synced two Traktors Pro running on different computers.

I own an Allen & Heath Xone 3D and a Sony Vaio running Vista. On the second computer (also running Vista) I used its integrated sound card, until an external one will be bought.

First I tried to make my Xone 3D the master, with both Traktors synchronized to it’s output midi clock. My Traktor was in sync… but I was not able to route the midi clock to the other Traktor because of the midi interfaces I tried to use (Akai MPD 32 and Edirol PCR 300). As soon as we will receive the M-Audio ProFire 610, I will try it).

The other option was using the software called MidiOverLan CP. This software creates a virtual Midi Out port on one computer and a virtual Midi In port on the second, and transmits midi data between them over the LAN. So you need both computers to be in the same physical LAN. You can do this using a router or a crossover cable.

You then activate the virtual Midi Out port on the first computer and check the “Send midi Clock” option. Also, in the master clock panel I set the midi clock to manual and choose the value I desired (128 BPM), and press the Send Midi Clock button.

On the second computer you activate the virtual Midi In port, and in the master clock section you choose “external” mode.

All decks from both Traktors should have the sync button pressed.

If you are lucky, that is all. Unfortunately, my Xone 3D sound card is much faster than the onboard soundcard on the second computer, so tracks on different computers are delayed (because of the different latency values).

Now you have to adjust the Midi Clock Sending Offset until the tracks are perfectly in sync.

That’s all!

PS: The computer with the slower sound card must be the master, because the midi clock signal can only be delayed :slight_smile:

What version of Traktor Pro were you using ? They must have fixed the midi sync issue because it wasnt working last at all last time i tried - Traktor was just plain out refusing to sync to a master clock and it took a little while for NI to admit it didnt work heh.

I was using version 1.02

That would probably explain it was trying on V1.0.1 - thanks for your contribution

Thanks istrateo, I have been looking for this information long time! :smiley:

hmm odd since Traktor pro 1.0.2 was working alright with midi syncing, then i upgraded to traktor pro 1.1.1 and the sync goes mental - getting about a 2 or 3 bpm fluxuation in the sync which is just mental.

eh…ok im lost…now what is this OCS:confused:

OSC = open sound control

Think of as kinda like midi on steroids

Ill have to give this a try out soon!

Me and Kaon have been discussing different options of simultaneous control when we play out, have two separate systems would be tight when there is enough space etc,

I want to share this with you guys, I havent test it yet, but I have two macbooks in my house. So I guess Ill try tonight & also on sunday…wish me luck ipMIDI for Mac OS X

[QUOTE]


ipMIDI Mac OS X ipMIDI 1.4 for Apple Mac OS X 10.4.x tiger / 10.5.x leopard (universal binary)
ipMIDI offers up to 20 multicast MIDI over LAN ports to connect your Apple Macintoshs with Windows PC’s in your local network.
ipMIDI is a native OS X MIDI driver. You will find it in Apples’s “Audio MIDI Setup”. Double click the ipMIDI icon to adjust the number of ports. The new ports will show up in all of your music applications.
Get your free copy!
Visit our download page to get your free copy of ipMIDI.
Please do not hesitate to contact us for any suggestions and
[/QUOTE]

*** Looks like I need a crossover cable or I have to look up some DIY options. I really dont want to use a router.

easy easy boy i think you have an mac its not really important if its a crossover or and patch cable…

let hear from you soon:smiley:

With new computers it doesnt matter - all the NIC’s automaticly detect if its a patch or crossover cable, thats not something that is a mac only feature.

Also if i have said it once, i have said if a million times, midi sync sucks ass :disappointed:
Your better off syncing manually - if you need to do tempo changes then have 1 midi knob change the tempo on both computers at the same time - then nudge the tracks to keep them in time. This works a billion times better than midi sync.

OSC it is then, Ill check up if I get it working, if not, stand by bento.

Traktor Pro doesnt support an OSC sync from what i could tell sadly :disappointed:

I dont use Traktor Pro, Im still stuck in the Traktor 3 world

oh cool well you might be able to get the OSC sync going then ! good luck !

Can’t wait! :smiley:

guys i have spent last 2 weeks going through different audio/midi interfaces tweaking shit out of different settings using external software plugins virtual cables and tons of other shit…

IF YOU WANT TO AUTO BEAT MATCH 2 COMPUTERS STOP LOOKING FOR OTHER THREADS AND READ BELLOW

MIDI IN TRAKTOR is fed up it doesnt work like it should!!
traktor does not receive midi!!,

the only way to sync 2 traktors on 2 computers at this moment is using OSC like bento san mentioned before.
The effect you can get from it is - sending a signal from one to another computer to adjust tempo!! thats it!!

You still need to manually adjust a phase and beat match.

Traktor pro doesnt even have OSC so i guess you have to use master tempo and have great communication with the person whos playing with you

anywho we had fantastic effects using manual beat matching and loop techniques. Good Luck to all of you!!

I hope someday NI will fix the issues so traktor can send and receive midi msgs back and forward and you don’t have to adjust the phase.

thnx :smiley:

all this really does confuse me. I’m tellin ya tho, it sound freakin awsome. just wish i spoke the lingo

has anyone ever gotten any of the OSC features of traktor3 to work? in searching around a bit, i’ve yet to read of any tales of success, only those of confusion and frustration.

i’ve tried several OSC clock message combinations targeting traktor3 and i can’t seem to excite any change in the application’s state. perhaps it uses a custom message for its tempo syncing and not the standard OSC clock message types?

in which case, the expected:

/IDENTIFIER/clock,VAL
/clock,VAL

would fail. guess i could set traktor3 to be the OSC tempo master and sniff the output to divine the message format…