On 4/18/21 10:32 PM, IOhannes m zmölnig wrote:
i checked and double checked the specs but could not find anything about this. where do you get the idea that the OSC specs mandate wall clock time? OSC-1.0 speaks about "NTP format" (but this is just the structure of the 64 bits data chunk) and "the number of seconds since midnight on January 1, 1900" (but it doesn't say whether this is supposed to be wallclock or idealized)
i just thought that maybe we are really talking about different things here.
so i'd like to clarify what I mean by "logical time".
Pd keeps an track of an internal monotonic value "pd_systime" that is incremented whenever time advances within the Pd world. the incrementation of this value is losely synched to the passing of time in the real world ("wall clock time"). "losely" insofar as the increments do not happen at exactly the same time, but the maximum difference between the wall clock time and the logical time is bound to a somewhat small value (<<1sec).
wall clock time is typically provided by the OS by means of gettimeofday() or similar.
while the two times are synched, they have different offsets. Pd's logical time simply starts whenever the Pd instance started. however, gettimeofday() counts seconds since the beginning of the epoch (currently: 1970-01-01 00:00).
to complicate things, NTP-timestamps (as used by OSC) use their own epoch that starts on 1900-01-01 00:00.
using Pd's logical time "as is" as an OSC timestamp, is of course useless (unless you are communicating withing the same Pd-instance), as all participants need to agree on a common epoch.
so what i'm really suggesting to "fix" the timestamps in [packOSC] is to use logical time for *advancing time* (and add some offset to put the timestamps into the same calendar as NTP)
so basically:
time with respect to the NTP time. e.g.: offset=seconds_from_1900_to_1970+gettimeofday()-sys_getlogicaltime()
in the actual implementation there's two issue that should be addressed:
calculation of the offset) should only be perfomed once for all the [packOSC] and [unpackOSC] objects in the running instance, so they are all tightly synched.
2038; this is still far in the future for many, but for [packOSC] birthday is about as far in the past)
gfmsdtf IOhannes