Gen~ dealing with Multislder list input

Oct 24, 2012 at 9:48am

Gen~ dealing with Multislder list input

Hi, I wondered if there is a way of gen~ handling unpacked multislider lists greater than 16.

This would be a handy param feature as the use of Multislider is quite limited at present with only a max of 16 “ins”

Maybe there is a way but could not figure this out,

many thanks for any help, P

#64910
Oct 17, 2013 at 2:58pm

bump,
Is there a way gen~ can hanlde lists? not really right?
I mean it would be quite convenient not to have to unpack it outside, create a lot of inlets etc..
all the best

#268325
Oct 18, 2013 at 12:29pm

Correct. There is no list input or parameter for gen~ currently.

However, note that parameters are not limited as are inlets. So you could define as many parameters you want–e.g. foo1 foo2 foo3 foo4, etc. and use multislider -> iter -> sprintf foo$i1 $f2 -> gen~ or something like that.

You could alternatively work around this with clever use of a buffer~ object-i.e. write the values into a buffer (one per sample) and read them from within gen~.

#268410
Oct 20, 2013 at 2:07am

@Joshua

yes, buffer~, buffer Gen and poke~ is how I worked around it in the end. It is actually quite an elegant method.

#268494
Oct 20, 2013 at 7:40am

note that one advantage of parameter over buffer is that the parameter is updated only once per vector when gen~ optimize the code. Buffer is updated every samples.

<code>

– Pasted Max Patch, click to expand. –

</code>

#268506
Oct 20, 2013 at 3:39pm

Emmanuel, Nice!. Quite a CPU difference, which additively will make a difference. I will try this tomorrow.

best P

#268544
Oct 20, 2013 at 3:56pm

Only problem Emmanuel’s method is that I am dealing with 1000+ multisliders. The buffer, poke method is so simple, worth the CPU overhead. Both elegant in the right context. Thanks again.

#268547

You must be logged in to reply to this topic.