Forums > MaxMSP

changing rslider range?

May 17, 2007 | 2:41 pm

Hi
I want to change the range of the rslider itself i.e the values you get in the inspector rather than the input values. Maybe a message to set the actual range rather than the min max range of the data coming in? I just want to display loop points for new files I load in. my other parameters work by using a "get" message like get duration for example and then sending that on.

is this possible, if not what are the alternatives to using rslider to set and display loop points graphically?
Carl


May 17, 2007 | 3:40 pm

On 17 mai 07, at 16:41, Carl Rohumaa wrote:

> Hi
> I want to change the range of the rslider itself i.e the values you
> get in the inspector rather than the input values. Maybe a message
> to set the actual range rather than the min max range of the data
> coming in? I just want to display loop points for new files I load
> in. my other parameters work by using a "get" message like get
> duration for example and then sending that on.

You can use the size message to change the range of rslider.
Everything you can do in the inspector can be made via messages
(inspectors are just patches).

Cheers,
ej


May 17, 2007 | 4:05 pm

There is a nice JS rangeslider called ad.rangeslider
that allows you to set the range, and also to move the
whole range bar, ie. not just the ends.
You can get it from
http://www.underhund.com/anders/max.php
cheers
Roger
— Carl Rohumaa wrote:

>
> Hi
> I want to change the range of the rslider itself i.e
> the values you get in the inspector rather than the
> input values. Maybe a message to set the actual
> range rather than the min max range of the data
> coming in? I just want to display loop points for
> new files I load in. my other parameters work by
> using a "get" message like get duration for example
> and then sending that on.
>
> is this possible, if not what are the alternatives
> to using rslider to set and display loop points
> graphically?
> Carl
>


May 17, 2007 | 4:24 pm

JS rangeslider looks good but only seems to spit out floats. i really need a raw integer for this. I just had a go at doing this>
[NumberBox]-[size $}-[rslider] with no luck. Max window just says "bad arguments for message "size"


May 17, 2007 | 4:33 pm

On 17 mai 07, at 18:24, Carl Rohumaa wrote:

> JS rangeslider looks good but only seems to spit out floats. i
> really need a raw integer for this. I just had a go at doing this>
> [NumberBox]-[size $}-[rslider] with no luck. Max window just says
> "bad arguments for message "size"

you do mean [size $1], right?

ej

#P window setfont "Sans Serif" 9.;
#P number 235 185 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
#P number 98 185 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
#P number 98 87 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
#P user rslider 98 151 147 17 99 1 0 0 0;
#P window linecount 1;
#P message 98 117 43 196617 size $1;
#P connect 1 1 4 0;
#P connect 1 0 3 0;
#P connect 2 0 0 0;
#P connect 0 0 1 0;
#P window clipboard copycount 5;


May 17, 2007 | 4:59 pm

At 5:24 PM +0100 5/17/07, Carl Rohumaa wrote:
>JS rangeslider looks good but only seems to spit out floats. i really need a raw integer for this. I just had a go at doing this>
>[NumberBox]-[size $}-[rslider] with no luck. Max window just says "bad arguments for message "size"

The size message works for me here:

#P window setfont "Sans Serif" 9.;
#P number 365 200 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
#P number 183 200 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
#P number 183 116 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
#P window linecount 1;
#P newex 183 141 66 196617 prepend size;
#P user rslider 183 170 192 24 87 1 0 0 0;
#P connect 0 1 4 0;
#P connect 0 0 3 0;
#P connect 1 0 0 0;
#P connect 2 0 1 0;
#P window clipboard copycount 5;

-C


Chris Muir | "There are many futures and only one status quo.
cbm@well.com | This is why conservatives mostly agree,
http://www.xfade.com | and radicals always argue." – Brian Eno


May 18, 2007 | 8:21 am

yes both of those work I was just being lame and using [size $] and not [size $1] Doh!

Thanks
Carl


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