OSCTimeStamp.toDate() not translated correctly

Question

OSCTimeStamp.toDate() not translated correctly

nlowe opened this issue 8 years ago · comments

It's not even close to my local time:

@OSCRoute("/go")
private void onGoNextCue(OSCTimeStamp time, OSCMessage message)
{
    Log.debug("Got GO NEXT CUE message at {}", time.toDate());
}

00:16:11.122 [DEBUG] soundclip.osc.OSCServer - Got GO NEXT CUE message at 2036-02-07T01:28:16.000-0500

Furthermore, it seems to be resolving to the same time each time. I'm not sure if this is an issue with the client (andrOSC), or the server (javaosc-core)

hoijui · Answer 1 · Fri Jan 27 2017 15:06:17 GMT+0800 (China Standard Time)

TODO (for myself or any other dev. working on this): check time-stamp compatibility with liblo.

hoijui · Answer 2 · Sun Jan 29 2017 19:33:28 GMT+0800 (China Standard Time)

.. jup @nlowe, you are fully right. JavaOSC currently uses very wrong code for time-tags. I don't know where it comes from, as it is similar but more complicated then the OSC(==NTP) format.
I am currently fixing the code.

hoijui · Answer 3 · Mon Jan 07 2019 20:21:13 GMT+0800 (China Standard Time)

The fix is on the develop branch: b2cc1a5