Is clocker misbehaving for anyone else in Max 6?
I'm messing with Max 6 in a Max For Live setup. The patch I am working on wasn't working in Max 5; however, it is even more broken in Max 6. I am sending a bang to a clocker to restart it, and for some reason, it restarts at 6800.931641 or some such nonsense instead of 0. Is anyone else seeing anything like this?
Every instance of clocker I create up exhibits the same behavior. It's very odd.
Here is the bit that is having problems. Clocker doesn't work at all on my machine running in Max For Live mode. It works fine in straight Max 6. I copied this out, created a whole new m4l patch, pasted it in, and it still misbehaves. If I create it from scratch it still does it. This sucks because the timing seems much more accurate in Max 6 than Max 5 which would make what I am working on so much easier. As it is though, I think I am going to have to wait and see if Max 6 stabilizes a bit before I buy it.
Can't confirm for Max 6 for now, but I tried it on a mbp with osx 10.5.8 and it works, or at least I think so : everytime I click 'everdub', the clocker restarts at 0. Live 8.2.6 and Max 5. When I'll be be back home, I can try it with Max 6.
Edit : Ooops : I'm on my Max 6 machine. This doesn't work on Max 6. The Max window gives this : js: can't find file set_state.js
js: jpatchline_new: index out of range
jpatchline_plugin: box missing outlet number 8
jpatchline_completeconnection: index out of range.
js: no function msg_float
js: no function msg_float
js: no function msg_float
js: no function msg_float
js: no function msg_float
And I can't stop or restart the clocker.
Yea, 5 is fine for me. Only 6 exhibits this problem. I built a finite state machine for controlling a looper with one button, but the functionality relies on clocker to know how long the button has been held on to determine what functionality it should use. This works fine in Max 5, the looper has timing issues, but those are just the nature of live and Max. I had hoped to try Max 6 to see if I could get some less variable results as far as timing later in the patch; however, upon opening my patcher, the clocker starts at an arbitrarily high number and never sets back to 0. That breaks my finite state machine code immediately and I have no way to check if anything else is working. The error you are getting is because you don't have the finite state machine js. I will attach that so you can mess with that if you want. The problem I am having is with the clocker outputting a high number that never resets to 0. Here is an example and I attached the fsm.
Okay, I confirmed it with support. Clocker is broken in Max 6 when used with Max For Live. It works fine when it's actually in presentation mode in the GUI of Live, but when it's not it goes nuts. Here is a workaround using cpuclock and some math.
Make sure you use the setstate.js script with it if you want to see it actually work.