Atte André Jensen wrote:
Where is this set-ability documented? Now I'd like to do kinda the same
with dac~, but that doesn't work:
[set 4(
|
[dac~ 1]
Naturally a bit more elaborate in real life, bit the idea is to have an
abstraction output to some channel in dac based on creation arguments...
try the attached patch.. note, you can put the [r~]-[dac~] block anywhere,
it doesn't have to be in the same patch.
What's different about dac~ compared to throw~, where can I read about
it, and how can I do what I'm trying to (set the channel of dac~)?
[dac~] is for connecting to the soundcard - best practise is probably to
have only one [dac~] object in your whole patch of patches, because then
you can do nice things like have a master volume control.
[throw~] and [catch~] on the other hand are for routing signals.
imagine the [dac~] as your master mixing desk and P/A, and [throw~] and
[catch~] (and [r~] and [s~]) as audio signal cables connecting your various
bits of gear.
--
damian stewart | +31 6 8178 5197 | [EMAIL PROTECTED]
frey | live art with machines | http://www.frey.co.nz
#N canvas 500 305 333 312 10;
#X obj 42 271 dac~ 1 2 3;
#X obj 144 189 == 3;
#X obj 96 189 == 2;
#X obj 44 190 == 1;
#X obj 22 147 r~ signal;
#X obj 144 147 r signal-dacchannel;
#X obj 22 213 *~ 0;
#X obj 74 216 *~ 0;
#X obj 122 216 *~ 0;
#X obj 29 18 osc~ 440;
#X obj 29 45 s~ signal;
#X obj 144 47 s signal-dacchannel;
#X msg 143 20 1;
#X msg 176 20 2;
#X msg 209 20 3;
#X connect 1 0 8 1;
#X connect 2 0 7 1;
#X connect 3 0 6 1;
#X connect 4 0 6 0;
#X connect 4 0 7 0;
#X connect 4 0 8 0;
#X connect 5 0 1 0;
#X connect 5 0 2 0;
#X connect 5 0 3 0;
#X connect 6 0 0 0;
#X connect 7 0 0 1;
#X connect 8 0 0 2;
#X connect 9 0 10 0;
#X connect 12 0 11 0;
#X connect 13 0 11 0;
#X connect 14 0 11 0;
_______________________________________________
Pd-list@iem.at mailing list
UNSUBSCRIBE and account-management ->
http://lists.puredata.info/listinfo/pd-list
