Re: the time that the message was sent from scsynth

julian.rohrhuber-QYZGCWsIODmAF8UT6DzBU6xOck334EZe@public.gmane.org Thu, 1 Mar 2018 17:16:21 +0100

Newsgroups	gmane.comp.audio.supercollider.devel
Message-ID	<[email protected]>

> On 01.03.2018, at 16:32, [email protected] wrote:
> 
> On March 1, 2018 22:05:03 julian.rohrhuber-QYZGCWsIODmAF8UT6DzBU6xOck334EZe@public.gmane.org wrote:
> 
>> The helpfile for OSCFunc says for time:
>> 
>> "the time that the message was sent (plus the latency if the message was in a bundle)”
>> 
>> Is the helpfile wrong or the implementation?
> 
> AFAIK, when receiving an OSC message, you have access to the timestamp (if it's a bundle), and otherwise the message carries no information at all about the sending time. In the latter case, all you have is the time of receipt... which varies according to network jitter etc.
> 
> AFAIK scsynth does not send send bundles back to the client. So the 'time' argument will not be reliable at millisecond scale.
> 
> Nice try in the help file, but there seems to be a misunderstanding in the wording. You can have the time of sending only if that time is encoded in the packet, and (again AFAIK, I guess I could be wrong but I don't think so) a bundling timestamp is the only standard way of encoding the time. No timestamp, no standardized reference to the sending time.

I’m still not sure if it is the helpfile.

There seems to be no consistent timestamp also in other cases:

OSCdef(\x, { |msg, time| [msg[3], time, time - msg[3]].postln }, "/reply");
n = NetAddr("127.0.0.1", NetAddr.langPort);

// message
fork { loop { 1.wait; n.sendMsg("/reply", 0, 0, thisThread.clock.elapsedBeats) } };

// bundle
fork { loop { 1.wait; n.sendBundle(0.2, ["/reply", 0, 0, thisThread.clock.elapsedBeats]) } };

signature.asc (application/pgp-signature, 833 B)