[PD] tight syncing of two pd machines...

Hans-Christoph Steiner hans at eds.org
Tue Dec 16 10:19:26 CET 2003

Well, if you can get the timetag aspect of OSC working, then it would  
be good.  You just need to set the delay on the OSC timetags to be  
greater than the jitter, then it will be reliable (as reliable as your  
computer's clock).  That is, of course, depending on implementation.   
Many if not most OSC implementations do not do timetags, AFAIK.


On Wednesday, Dec 3, 2003, at 13:43 Europe/Brussels, joreg wrote:

> halo.
> in a recent setup i had to sync a pc that generated sounds to another
> that did the visuals. all tests with udp or tcp connections were
> unsatisfying. the beat was not received constantly on the other
> machine. now i do it with midi and am happy. i didn't measure anything
> but a jitter is no longer obvious.
> osc will not be better than netsend via udp since it still uses udp.
> grkks.
> joreg.
> JS> does anyone have any good experience getting *very* tight timing  
> sync
> JS> between two computers running pd?  for my first attempt i just used
> JS> [netsend]/[netreceive] to send a message (the number of the current
> JS> measure) and got really nasty jitter (10's of ms).  last night i  
> banged
> JS> out a little net latency test patch and the results were so bad i
> JS> decided i was tired and it must be a problem with my code ;)
> JS> so... how have you achieved tight timing sync?  should i give up on
> JS> network sync and just use a midi cable?  how about OSC?
> --cut here-------------------
> current: http://vvvv.meso.net
> allstar: http://joreg.ath.cx
> _______________________________________________
> PD-list mailing list
> PD-list at iem.at
> http://iem.at/cgi-bin/mailman/listinfo/pd-list

Using ReBirth is like trying to play an 808 with a long stick.
								-David Zicarelli

More information about the Pd-list mailing list