grimepoch

I have a multislider feeding into a pipe. When I bang the multislider it sends all its values into the pipe and delays them all at once, so the whole mess of numbers comes out after the ms setting.

What I am trying to do is get each of those values to come out after 1000ms between them.

Is this something where I should use metro and a counter to get the values out? I'm trying to understand what the best way to do this as I get myself thinking in 'max' ways of doing things.

I have a multislider feeding into a pipe.  When I bang the multislider it sends all its values into the pipe and delays them all at once, so the whole mess of numbers comes out after the ms setting.

Is this something where I should use metro and a counter to get the values out?  I'm trying to understand what the best way to do this as I get myself thinking in 'max' ways of doing things.


using-pipe-how-do-i

> What I am trying to do is get each of those values to come out after

> What I am trying to do is get each of those values to come out after
> 1000ms between them.

It seems that speedlim would just then output the first and last value I send it as the documentation says that new messages will overwrite ones already there during that delay. Essentially filtering the number of messages out based on how many messages over time.

It seems that speedlim would just then output the first and last value I send it as the documentation says that new messages will overwrite ones already there during that delay.  Essentially filtering the number of messages out based on how many messages over time.


On 9 Feb 2007, at 20:33, Patrick Delges wrote:

That will throw away intermediate values.

A solution I've used: pump the values into a coll, indexed by a 

timestamp counter. Have a metro/counter run through the timestamps, 

triggering (and the deleting) entries from the coll. (I have the 

patcher somewhere, but I wrote it 15 years ago, so it would take a 

A solution I've used: pump the values into a coll, indexed by a  
timestamp counter. Have a metro/counter run through the timestamps,  
triggering (and the deleting) entries from the coll. (I have the  
patcher somewhere, but I wrote it 15 years ago, so it would take a  
while to find it.)

there's an L object that does this... hrm.... I do believe its called....

It can be found in lobjects 2. Yes, it can.

> I have a multislider feeding into a pipe. When I bang the multislider it

> sends all its values into the pipe and delays them all at once, so the whole

> mess of numbers comes out after the ms setting.

> What I am trying to do is get each of those values to come out after 1000ms

> Is this something where I should use metro and a counter to get the values

> out? I'm trying to understand what the best way to do this as I get myself

> thinking in 'max' ways of doing things.

On 2/9/07 3:07 PM, "Rick Burnett"  wrote:

>
> I have a multislider feeding into a pipe.  When I bang the multislider it
> sends all its values into the pipe and delays them all at once, so the whole
> mess of numbers comes out after the ms setting.
>
> What I am trying to do is get each of those values to come out after 1000ms
> between them.
>
> Is this something where I should use metro and a counter to get the values
> out?  I'm trying to understand what the best way to do this as I get myself
> thinking in 'max' ways of doing things.

Cheers
Gary Lee Nelson
Oberlin College
www.timara.oberlin.edu/GaryLeeNelson

if you need the values one by one, why dont you call single 

values from the multisider instaed of a list?

if you need the values one by one, why dont you call single 
values from the multisider instaed of a list?

Just for the pleasure of trying to add my solution. Of course, not as 

elegant as Gary Lee Nelson's one, I'm afraid.

Just for the pleasure of trying to add my solution. Of course, not as  
elegant as Gary Lee Nelson's one, I'm afraid.

> Just for the pleasure of trying to add my solution. Of course, not as 

> elegant as Gary Lee Nelson's one, I'm afraid.

I am still in for another solution... ;-)

The mousefilter is for having it send only on releasing the mouse. If 

you don't want to delay the first output, connect the bang of [t b l] 

jln wrote:
> Just for the pleasure of trying to add my solution. Of course, not as  
> elegant as Gary Lee Nelson's one, I'm afraid.

I am still in for another solution... ;-)
The mousefilter is for having it send only on releasing the mouse. If 
you don't want to delay the first output, connect the bang of [t b l] 
directly to [zl queue]...

-- 
Stefan Tiedje------------x-------
--_____-----------|--------------
--(_|_ ----|-----|-----()-------
-- _|_)----|-----()--------------
----------()--------www.ccmix.com


I know I'm late to this party, but iterating through the slider 

values seems like a better approach to me.

Chris Muir | "There are many futures and only one status quo.

cbm@well.com | This is why conservatives mostly agree,

 | and radicals always argue." - Brian Eno

I know I'm late to this party, but iterating through the slider 
values seems like a better approach to me.

-- 
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


Using pipe...how do I...