Torsten Anders wrote:
>Unfortunately, using [unpackOSC] -- just using routeOSC-help.pd -- I
>was not able to delay the effect of OSC messages either. This
>helpfile patch shows some delay, but that is always negative
>(something in the order of -3.5e+06 msecs), even if my OSC bundle
>timestamp is several seconds (up to a minute) in the future. I
>meanwhile confirmed that it works in SuperCollider, so my OSC bundles/
>timestamps are seemingly fine.
>
>Does there perhaps exist a problem with the delay output by unpackOSC?
>PS: I am using Pd-0.40.3-extended-20070830 for Intel Mac.
I just tried the same version of pd on an intel mac and I have no trouble sending timestamps between pd on the same machine or to another one running linux.
It could be that the timestamp format is wrong somehow, but the code was basically lifted from OSC-timetag.c in OSCx, which is the same code that sendOSC uses.
Did you try sending to and from pd on the the same machine?
The timestamps in packOSC are specified in microseconds relative to now, but unpackOSC outputs the delay in milliseconds to be compatible with pd's delay.
Notice that 3.6 million milliseconds is one hour. It may be a timezone thing. The OSC spec says that the timestamp format is the same as NTP format but it doesn't talk about time zones or daylight saving time, so I assumed it means GMT/UTC.
Martin