[PD] network

[Stephen Sinclair]

> I think the best way would be to put some kind of timestamp in the
> messages and have the receiver hold the received message until the
> timestamped time occurs. That should get rid of any jitter at the
> expense of a second or so of delay.

In fact that's an interesting point related to OSC.  OSC of course
supports exactly this -- the use of timestamps for synchronizing data.
 And yet it's rarely actually used to its full advantage.  In both the
Pd and Max/MSP implementations there's no way to send data over an OSC
connection scheduled for a delayed timestamp.  In other words, there's
no way to sacrifice a bit of latency for timing precision.  However,
OSC itself should allow you to do it.

I wonder if it would be a good thing to have sendOSC accept another
message, such as "delaysend" or something which allows specifying what
time the message should be deployed on the receiver.  It would be very
useful, for example, for synchronized clocking over multiple clients.

Any thoughts?  How might the timestamp be most easily specified in Pd?


Steve