I'm trying to bring in the position of the knob on my MotorMix but it

only sends a direction (see my solution).

Using counter, every time a 1/0 (knob direction) comes in through

MIDI, it triggers a bang which is counted. When the maximum count is

reached (knob max.), counter sends out a bang which closes the gate.

This works but when the knob reaches the minimum count, it resets to

the max value. I can send a patch to demonstrate this solution later

Seems like it would be a simple solution, but is there a way to create

a minimum and maximum for counter that does not reset? I can use a

gate but then I need to be able to re-open the gate when the opposite

Another thing is my solution does not account for accelerated knob

twisting to speed up the values inc/decrementing. I could be doing

this all wrong, so I would love to hear of a better solution

What I'm trying to accomplish:
I'm trying to bring in the position of the knob on my MotorMix but it
only sends a direction (see my solution).

My Solution (not completely working):
Using counter, every time a 1/0 (knob direction) comes in through
MIDI, it triggers a bang which is counted. When the maximum count is
reached (knob max.), counter sends out a bang which closes the gate.
This works but when the knob reaches the minimum count, it resets to
the max value. I can send a patch to demonstrate this solution later
as I'm not at my Max/MSP computer.

Seems like it would be a simple solution, but is there a way to create
a minimum and maximum for counter that does not reset? I can use a
gate but then I need to be able to re-open the gate when the opposite
knob direction comes back in via MIDI.

Another thing is my solution does not account for accelerated knob
twisting to speed up the values inc/decrementing. I could be doing
this all wrong, so I would love to hear of a better solution
all-together.

not-allowing-counter-to-reset-on-maxmin

On Mar 28, 2008, at 11:30 AM, Wade wrote:

> Seems like it would be a simple solution, but is there a way to create

> a minimum and maximum for counter that does not reset? I can use a

> gate but then I need to be able to re-open the gate when the opposite

> Another thing is my solution does not account for accelerated knob

> twisting to speed up the values inc/decrementing. I could be doing

> this all wrong, so I would love to hear of a better solution

I used accum to accomplish this in my MaxieControl package. Here's the 

vpot patch from there (none too well commented, I'm afraid.) It does 

accomplish what you're interested in, I think; clips at the extremes, 

On Mar 28, 2008, at 11:30 AM, Wade wrote:
> Seems like it would be a simple solution, but is there a way to create
> a minimum and maximum for counter that does not reset? I can use a
> gate but then I need to be able to re-open the gate when the opposite
> knob direction comes back in via MIDI.
>
> Another thing is my solution does not account for accelerated knob
> twisting to speed up the values inc/decrementing. I could be doing
> this all wrong, so I would love to hear of a better solution
> all-together.

I used accum to accomplish this in my MaxieControl package. Here's the  
vpot patch from there (none too well commented, I'm afraid.) It does  
accomplish what you're interested in, I think; clips at the extremes,  
and allows for knob deltas > 1.

Chris Muir
cbm@well.com	
http://www.xfade.com

Wicked, thanks Chris for sending that! I'll take a look at it when I get home.

By 'knob deltas > 1' are you referring to knob acelleration based on

speed of knob rotation or are you referring to allowing the knob

max/min to be re-mapped to different values?

On Fri, Mar 28, 2008 at 3:26 PM, Chris Muir wrote:

> I used accum to accomplish this in my MaxieControl package. Here's the

> vpot patch from there (none too well commented, I'm afraid.) It does

> accomplish what you're interested in, I think; clips at the extremes,

By 'knob deltas > 1' are you referring to knob acelleration based on
speed of knob rotation or are you referring to allowing the knob
max/min to be re-mapped to different values?

On Fri, Mar 28, 2008 at 3:26 PM, Chris Muir  wrote:
>
>  I used accum to accomplish this in my MaxieControl package. Here's the
>  vpot patch from there (none too well commented, I'm afraid.) It does
>  accomplish what you're interested in, I think; clips at the extremes,
>  and allows for knob deltas > 1.


On Mar 28, 2008, at 12:44 PM, Wade wrote:

> Wicked, thanks Chris for sending that! I'll take a look at it when I 

> By 'knob deltas > 1' are you referring to knob acelleration based on

> speed of knob rotation or are you referring to allowing the knob

> max/min to be re-mapped to different values?

While I do allow the max value to be remapped in this patch, what I 

was referring to was acceleration. What the Mackie Control sends for 

its VPots, is a controller value. The controller is to be interpreted 

as bipolar, centered on 64: 64 is positive. The 

distance away from the midpoint is how many ticks to move. If you get 

a CC message of 65, you would move one tick higher, if you get a 

On Mar 28, 2008, at 12:44 PM, Wade wrote:
> Wicked, thanks Chris for sending that! I'll take a look at it when I  
> get home.
>
> By 'knob deltas > 1' are you referring to knob acelleration based on
> speed of knob rotation or are you referring to allowing the knob
> max/min to be re-mapped to different values?

While I do allow the max value to be remapped in this patch, what I  
was referring to was acceleration. What the Mackie Control sends for  
its VPots, is a controller value. The controller is to be interpreted  
as bipolar, centered on 64: 64 is positive. The  
distance away from the midpoint is how many ticks to move. If you get  
a CC message of 65, you would move one tick higher, if you get a  
message of 66, two ticks, etc.

Not allowing Counter to reset on Max/Min