Originally [range] was only there so that when I convert jMax patches
to Pd patches, I wouldn't have to do elaborate search-and-replaces.
Although later on I could have decided to let it go and do things the
Pd way, instead I came with the idea that [moses] was not enough and
that if [sel] and [route] and such, take multiple number of arguments,
[moses] should. In some patches I had to string 8 [moses] together.
btw such "range" is very feasible with only pd language and dynamic
patching.
see attached patch ;-)
--
Federico Ferri
#N canvas 1342 197 555 476 10;
#X obj 40 42 loadbang;
#N canvas 0 0 450 300 serialize_list 0;
#X obj 99 56 inlet;
#X obj 99 99 list split 1;
#X obj 112 223 outlet;
#X obj 80 161 t b a;
#X obj 142 132 list;
#X connect 0 0 1 0;
#X connect 1 0 3 0;
#X connect 1 1 4 1;
#X connect 3 0 4 0;
#X connect 3 1 2 0;
#X connect 4 0 1 0;
#X restore 40 100 pd serialize_list;
#X obj 40 157 namecanvas $0-cnv;
#N canvas 1933 36 539 577 dyn_patcher 0;
#X obj 42 38 inlet;
#X obj 42 412 s $0-cnv;
#X obj 42 86 t b f b;
#X msg 125 104 0;
#X obj 107 144 f;
#X obj 146 145 + 1;
#X obj 42 119 t b b;
#X obj 64 176 * 80;
#X obj 64 200 + 40;
#X obj 171 240 + 1;
#X obj 125 76 loadbang;
#X obj 116 171 * 2;
#X obj 117 192 + 5;
#X obj 143 215 + 2;
#X msg 42 367 obj $2 260 moses $3 , obj $2 300 outlet , connect
$5 0 $6 0 , connect $4 1 $5 0;
#X obj 42 330 pack 0 f f f f f;
#X connect 0 0 2 0;
#X connect 2 0 6 0;
#X connect 2 1 15 2;
#X connect 3 0 4 1;
#X connect 4 0 5 0;
#X connect 4 0 7 0;
#X connect 4 0 11 0;
#X connect 5 0 4 1;
#X connect 6 0 15 0;
#X connect 6 1 4 0;
#X connect 7 0 8 0;
#X connect 8 0 15 1;
#X connect 9 0 15 5;
#X connect 10 0 3 0;
#X connect 11 0 12 0;
#X connect 12 0 13 0;
#X connect 12 0 15 3;
#X connect 13 0 9 0;
#X connect 13 0 15 4;
#X connect 14 0 1 0;
#X connect 15 0 14 0;
#X restore 40 130 pd dyn_patcher;
#X obj 40 71 dollarg;
#X obj 40 215 t a a;
#X obj 40 189 inlet;
#X connect 0 0 4 0;
#X connect 1 0 3 0;
#X connect 4 0 1 0;
#X connect 6 0 5 0;