Counter MSP

Sah~ could help

Thanks ! It's a good beginning ! But is it enough precise ? Because phasor doesn't really reach 1, so the value 0.9999 si an approximation, no ?

Now, when the direction change, it doesn't countdown from the previous value. Maybe the way I made the countdown isn't the best way to do this ?

Here's some tweaks. I've swapped out some of the logic (e.g. the if else) for things that may be a little more Max-ish. Ultimately, however, this is the type of thing that would best be handled in gen~ because the logic is much simpler when you can base it on previous states of the counter (since you can have single sample feedback in gen~)

Thank you for the help Peter ! Clever ideas in your version !
The first part is clear for me and way better than mine, but I don't understand all the second part (pong and modulo subpatch). Why there is %~ 8 / +~ 8 / %~ 8 in the modulo subpatch instead of only %~ 8 ? Because the result seems to be the same no ?

Edit : I understand now the subpatch modulo (to avoid negative value in down direction).

Why the abs~ object is useful here ? Because when I check the out value from delta~ with number~ and print, it's always positive (0.000023). But if I erase the abs~ to test, it does not work anymore.

I made a version based on yours. I can't see how to reset the signal accumulator at the tempo and in signal domain. In your version, it works great but the reset isn't synchronize with the main tempo.

You can use rate~ to run the reset at a multiple of the accumulator's clock signal. (e.g. rate~ 16 should reset once per 16 pulses)

The abs~ is there so if you had a negative frequency in your phasor~, it would still work, since you're just looking for a big jump, regardless of direction. You shouldn't be seeing negative frequencies if you're just specifying in milliseconds, but say you add an LFO, etc. later...one less bug to find.

Thanks Peter ! It works perfectly, but I have a problem to reset the signal accumulator at the right tempo, because if I change the min or max value, it updates the rate immediately.
I think the max value must be stored and send only when the count reach the min value. I try with gate and sah but it doesn't work... any idea to achieve this only in MSP ?

I think you need to sample and hold the min/max values.
What about using scale~ for that?

Thanks for your help !
I have an error with the scale~, it's an external object ?
The sah~ is a good beginning, but the timing isn't perfect yet.

I try a new version with your ideas and without the pong~ object, but I don't succeed to make it work... If I want to update the min and max values without breaking the tempo, I must update the rate~ only when the phasor~ ramp is over, but when the sah~ is connected to rate~, the counter doesn't work anymore...

scale~ is a native object. I guess you have something wrong in your search path.
Look for a file in your search path with the same name.

" but when the sah~ is connected to rate~, the counter doesn’t work anymore…"

If you want to process the same vector you will need to introduce a vectorsize delay. Send~ and receive~ will do the job.

Have you tried with gen?