Henning Thielemann <[EMAIL PROTECTED]> writes: > However I consider it a slight hack to first add magic number 2208988800 > in utc_ntp, then subtract it in ntpZeroed again. Would you mind making the > Bundle time zero based and add the appropriate offset at encoding the > message?
2208988800 = (70 * 365 + 17) * 24 * 60 * 60 NTP epoch = January 1, 1900 Unix/UTC epoch = January 1, 1970 Deleting the -/+ would mean making a local variant of encodeOSC and I'm not sure it is really important? (ie. I don't this this is going to slow anything down too much?) All timestamps are zero based, it is just a matter of when the zero was :) The integer OSC NTP time format is not very nice at user level so the convention is to us real-valued UTC times. > Btw. Sound.SC3.Server.Private.mkDuples should be mkPairs ? I thought that duple and pair were synonyms in this context? It seems perhaps not very common, google does show some uses given 'duple 2-tuple'. > Your example didn't work here (message length >8192 error), but let me > incorporate and test with your past patches before worrying about it. :-) OK, I've not seen any message length errors here. _______________________________________________ haskell-art mailing list [email protected] http://lists.lurk.org/mailman/listinfo/haskell-art
