problem with date object in 6.1.5?
I seem to be getting erroneous date and time info from the date object in 6.1.5. Can anyone duplicate this? I ran it in 5.1.8 and the time is correct.
----------begin_max5_patcher---------- 1395.3oc2YssiihCD84juBDR6aYo8ca521Of8KXzpQDvSZ5NAh.xL8til+80 W.ZRHWLIPRqQQhKEDm5bpiKWtxOmOyeY96xReum89h2rY+b9rYFSZCypuel+ ln2iWGUZdM+MxxxnUR+E1mUIeuxXOjIvBND17frcax2UsVVY9ZvZqeKOqpL8 +jZaHP.n171np3WRyV80BYbk0aHTj5wdTBN.QW3AwT8sHd.v6ep+VKWEmuNu .Y+B5QqyAXmWz5HU+6Vo8U88aej1+MiRyf.ALBCqGDAGQHglgC.oHz9i4phn jTYVUWzoGrW2UVk9sz3npz7rtOLMwvS4Ke8O4srjlOxh1X7K++JKIZsz6uyy xadd5prbEmrNM9stiUMxuHvUAgzrlX.Ra6WymqOrvwncU9pUqkmOldjfGhZc kPyIT6wVGaagrTQd8HodQpTMC2FvyKRjEtA8sQEJdsRV7UYVzx0lwCbjPAve fbZWWuKjCCTxT0QsZ8HHN9EY7axjCzZTg.Y0Z5KuTDDdEQvL4OT3r2z004QI KixV49zUH5bSWah3Ln9DqO96EYM+5sOtSHgEd7YGEoQq8mXZQoXJx8f..XjI FDjoOwg2Bw.FHwbMy3OU9c.8YD3YHZrxuiDgJUOcjxv6b9jGblep3Nk4+DYo fgbKqiXVRGx6Q5SlDBhdBvdBAf3wRDAQ38JRfv98WBQ3OVIDkEzQ+fwiu9Y4 tpJE7OqFQaJMS5Zs.mLsLgFfYDHlcakoreN6kJW6s9tVn.h3Biqsu+0M5Rai tNFlbKJGBwbc.63WcwfNFAr4MvMIqMtA9NToxtrsQwu4AzeNtl.O3EkI.ShB BQDnV1QvHpUlCu7Jy5hQWr2oiEBorGW8KkaKTt0279C.J441CiUsLMzl.1Ra PB8x71woogVlG9yslpNixDoo.eNzTOUefjLx0GONZJh3NnoNeGP3vwhYnLgg YT6bf0vL1ZjghgyLjG3dGfHOl2vp6yMQy3PM3GH0jDUIGMVwluACA5Jzvjqk OPOP9nRUFS4XQHXFMfoKW4loD3CjRnpoNdi2bmlEwGm4NfGpVYynM2Aa2IYi PAek7A9dvGmXc5SmJAe0oRTqDqni5sUe10iWmVZpfo47opjAcOpNdaTlb8w4 hy0MAfYAWJhzVJBIzjxfor.06R7h6LrHeWVhLw15hZakuDkj+CsIZe9.dh9O iETF0zQ39W4RidLaxLrEHXh4uSg4zN1Lugud+0G7WCYHMs8849x7cEwMBglt p68wOThrrJMqkq9xGsyryK8RZRhLqaHJIsT24dCWANpJvU+Q2R4K5O76n+3B +naEvcxentvO5dW5AuO9CyE+I7B7ylzjs4p7P0hXBzlLiiBDh5o2GZ5iexwE KPWvBb.XoNwLm9AV3h8MMUXA4BVPC.K7dwEJAN8wEmlCJFlFCQCODK8LMUXA 5BVFfFS+OzXbbVKVvHz9llJrfbAKCPigg8hKpESm73xAxmSfE9cKu5AKobB+ gbcZd.Wehx4s2MELpSH.eUH.Cwl+ZiN28vP.5pP.RvCHXDfIzWK12zCCKvaF KX0RDPzmCz.tkYGMEb7HmcfA2d7.ildsEwkZ1gCaMslrSp4FDBJDiVz2zTfE rK0ydkJKBnWsFsllBrfb.KH1.whMYEFys5pOtaJP.bBPPaJp6DFbo5UJ651g TGEUOSS.VvfoHdXSQcehFHW1WjIgFbH0rZndrfDPYbStJVHdeSSEVbpBK3vm eGxC.0XAa212GllJr.cYE8gDW.lVogCAswEJFZwBv03hsEaQa29cYQYs+Xfg +lnWscAjsvbaZl8VSGF8KjeOs48McSzOpH9kzJYb0tBaqTeWv7mq+c907+GP t5k0. -----------end_max5_patcher-----------
It is correct here. MAX 6.1.5 (32Bit) MacOS 10.8
FWIW, with Max 6.1.3 32-bit on Mac OS 10.8.5 with my computer’s clock synched to time.apple.com at 12:10:30 PST and with http://wwp.greenwichmeantime.com/ showing the time as December 7, 2013 at 08:10:30 GMT, my date object reported 12/6/2013 07:20:05. ?
So I checked and it seems i was running 6.1.5 in 64-bit. I changed it to 32 and it worked, i.e., i got a time and date that matched the system clock. I change it back to 64 and it continued to work. That looks like an initialization problem. Does 6.1.5 default to 64-bit because i don’t remember changing that.
However, if I run my clock patch, and close my notebook, when i open it the next morning the clock starts running again, but at the time displayed when the notebook was closed. Which makes me think that the date object references the system date on load but then runs its own internal clock… because it drifts relative to the system clock – i don’t know how many days this patch has been running but it is currently 11 seconds ahead of the system and widening the gap.
Currently running 6.1.6 32-bit OS X 10.9.
Yep, it’s probably something like that… it may initialize once, but then not do so again after sleep, getting off by as much time as the computer was asleep, or something like that. It works fine here right after restarting Max.
Is there any fix or workaround for this issue? I am making an interactive clock patch but if the computer goes to sleep, the time will remain inaccurate unless I quit and relaunch Max. Closing and reopening my patch does not help as the entire application needs to be relaunched. Is there maybe a different object that will always reference the system’s clock?
there is the [mxj now] object that comes with max i think, if you are willing to have java loaded with your patch