blob: 80d77854989ba6696d14a3314423774d5d81f3fa (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
|
#N canvas 731 31 478 597 10;
#X text 130 258 Inlet 2 changes the lower scaling bound;
#X text 228 288 Inlet 3 changes the upper scaling bound;
#X floatatom 131 273 5 0 0 0 - - -;
#X floatatom 232 304 5 0 0 0 - - -;
#X floatatom 31 253 5 0 0 0 - - -;
#X floatatom 31 363 5 0 0 0 - - -;
#X text 29 236 Inlet 1 is the standard commun input;
#X text 340 552 2008 Luke Iannini;
#X text 2 573 Originally based on [commun-scale] by Frank Barknecht
;
#X text 13 26 Use sft.commun.sc(ale) so that 0-1 values coming out
of OSC stuff (like Controctopus) can be rescaled appropriately.;
#X text 14 145 sft.commun.sc's first and second args are swapped from
sft.commun (i.e. \$0 and /parametername);
#X text 15 182 Optionally prepend a unique ID to the parameter when
using with an abstraction that will have multiple copies;
#X obj 31 327 sft.commun.sc \$0 \$3/parameter 5 37;
#X text 13 109 Don't use this for communs that are meant to store symbolic
or list data (use regular sft.commun for that).;
#X text 34 404 * Argument 5 and 6 can be "round" and/or "hide" (the
order doesn't matter).;
#X text 34 434 * "hide" hides the parameter from Controctopus sniffing
(useful to pare down the options to just the most interesting inputs).
;
#X text 34 476 * "round" rounds up from 0.5 increments so that an integer
is always output (useful for communs connected to v/hdials and toggles).
;
#X text 14 62 0-1 data should be directed to /paramatername-normalized.
The address /parametername still exists and will output arbitrary data.
;
#X text 328 537 made more confusing by;
#X connect 2 0 12 1;
#X connect 3 0 12 2;
#X connect 4 0 12 0;
#X connect 12 0 5 0;
|
