IEEE 1588 precise time protocol

Now that this standard is so mature it is time to consider how to use it in OSC. It is already integrated into high quality time reference hardware and in Intel network processors.

This paper on packet timestamping seems particularly useful:
IEEE 1588 Implementation and Performance of Time Stamping Techniques

ntpd, ptpd etc

There is an IEEE 1588 software implementation available for linux machines at http//ptpd.sourceforge.net/ The authors claim synchronization accuracy far in excess of what is currently possible with ntpd.

Many of the problems voiced regarding clock jitter problems observed with NTP sync will go away when PTP replaces NTP as the preferred method of time synchronization for local area networks.

The question then is what, if anything, must be done to OSC to support PTP. OSC timestamps use the NTP format but given that the format resolution is sufficient it would seem that this does not need to change (the OSC 1.0 spec leaves the issue of how to synchronize time to other technologies). The further question of how to use precise timing effectively in distributed multimedia is one of best practices and algorithms.

-aws

Precision Time Protocol available

in case PTP (Precision Time Protocol) IEEE 1588 is still considered - we also have a solution without extra hardware required - uses regular network interfaces. www.real-time-systems.com (low Microsec. Jitter)

Gerd

and ptpd

PTPd [ http://ptpd.sourceforge.net/ ] is another pure software solution which is open source and runs on embedded linux including several embedded variants. How does it compare with the above?