Re: Is clocker misbehaving for anyone else in Max 6?

Forums > MaxMSP > Is clocker misbehaving for anyone else in Max 6?
Nov 08 2011 | 2:26 pm

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.

-- Pasted Max Patch, click to expand. --

  1. setstate.js

Subscribe to the Cycling ’74 Weekly Newsletter

Let us tell you about notable Max projects, obscure facts, and creative media artists of all kinds.

* indicates required