to_the_sun

I'm running into a problem with a clocker (highlighted in the LOAD subpatcher) that is not behaving as expected. This patcher is designed to take cues from another patcher, which will load up the mtr with useful bits of midi. In the Max window, you can see the first 'record' command come through, which triggers the clocker. The clocker seems to work for all of 4 milliseconds and then does nothing until the second 'record' command comes through at which point it outputs an insane number. ('Record' commands are designed to come through and prime the mtr repeatedly, restarting the recording every time an unsuitable event is found by the other patcher, until the full cliplength runs its course without an interruption and the stop command is engaged.) I had this set up just a second ago so that the cliplength would feed into the interval outlet of the clocker and the sel 1 would output a 0 any time the clocker output something bigger than 0 (which should have always been the cliplength), but it was outputting insane numbers that way too, rarely ever the cliplength. I'm frustrated with working on this for the time being.. I've never had this much trouble with a clocker before, but I have always noticed that even in the clocker.maxhelp window the clockers always seem to spit out not quite perfect intervals. And what's with all the trailing numbers after the decimal point, when the clocker should have been initiated in integers? Anyone have any advice?

**UPDATE** it looks like the two 'record' commands were actually coming through 4 milliseconds apart, something that can happen with the way i have the code set up currently, but shouldn't really cause a problem.. I don't think. Still wondering about those strange/large numbers the clocker's putting out.

Ok. HERE'S the pic i'm referring to, sorry: 

Ok. HERE'S the pic i'm referring to, sorry: http://imgur.com/Ws3qoR7


clockers-that-send-out-strange-numbers-totally-out-of-tune-with-their-intervals

Oops, I seem to be having problems here...

Here I tried to set up a timer to measure the intervals between print messages. Again, more totally impossible numbers. -8686579.973291? 8686630.724591? How is it that i'm abusing these objects to make them spasm in pain like this?

Unfortunately the timing of M4L devices in edit mode seems somewhat unreliable and different from performance mode. So for serious testing you need to save the device first and then watch the Max window in Live (to open with control-click on the device title bar).

Clockers that send out strange numbers, totally out of tune with their intervals