Forums > MaxMSP

dial range with size attribute?

November 13, 2011 | 9:08 pm

I posted this as part of an answer to another thread but I’m curious to know whether this is normal, a bug, or what. When I specify the size for a dial and the dial has float output off the range is 0 to size-1. When I specify the size for a dial and the dial has float output on the range is 0 to size. Hmmm?

– Pasted Max Patch, click to expand. –

November 13, 2011 | 11:02 pm

Apparently for integer the size is defined by ‘Number of Steps’ (360 steps –> values 0-359).


November 14, 2011 | 12:37 am

What exactly does the number of steps mean?
When I turn the integer dial it jumps 0, 9, 18, 27… and seems to have 40 steps between 0 and 359.
The float output dial does the exact same thing except for landing on 360 instead of 359 on the last step.


November 14, 2011 | 12:45 am

In integer (default) mode Range represents the number of possible values, including lowest and highest values.

In float mode the Range represents the numerical distance between the minimum and maximum value but does not give any indication about the number of values but usually you get a much higher number.


November 14, 2011 | 1:23 am

First, thank you both for your help and information.

I guess my initial purpose for the post was to suggest that it would be better if these were consistent. Probably making the float version agree with the integer version – number of values possible in a zero-based system. The highest possible value = size minus one.

All of this however does lead me to a question I’ve wondered about before: why do the values jump in such large increments when I turn the dial? The on-screen dial really can’t be used for fine-tuning. Am I missing something?


November 14, 2011 | 4:49 pm

Hold shift key while turning the dial, the values will change with a smaller increment.


November 14, 2011 | 11:03 pm

Thank you. That’s very helpful.

I notice that in "shift-clicking" my example patch, with a size of 360, the integer version jumps in increments of 2. The float version by 1.8. Still not really what I would call fine control.

BTW, where is this technique documented? Do other UI elements have similar functionality?


Viewing 7 posts - 1 through 7 (of 7 total)