aboutsummaryrefslogtreecommitdiff
path: root/pd/doc/5.reference/send~.pd
diff options
context:
space:
mode:
Diffstat (limited to 'pd/doc/5.reference/send~.pd')
-rw-r--r--pd/doc/5.reference/send~.pd32
1 files changed, 0 insertions, 32 deletions
diff --git a/pd/doc/5.reference/send~.pd b/pd/doc/5.reference/send~.pd
deleted file mode 100644
index 5c9db395..00000000
--- a/pd/doc/5.reference/send~.pd
+++ /dev/null
@@ -1,32 +0,0 @@
-#N canvas 31 28 678 406 12;
-#X floatatom 344 238 0 0 0;
-#X obj 344 189 receive~ signal1;
-#X obj 17 215 send~ signal1;
-#X obj 17 192 sig~ 50;
-#X obj 344 213 snapshot~;
-#X obj 42 22 send~;
-#X obj 94 23 receive~;
-#X text 178 23 - one-to-many nonlocal signal connections;
-#X obj 507 133 loadbang;
-#X obj 507 194 metro 200;
-#X msg 517 155 \; pd dsp 1;
-#X floatatom 18 168 4 0 0;
-#X text 48 51 A send~ object copies its input to a local buffer which all receive~ objects of the same name read from. They may be in different windows or even different patches. Any number of receives may be associated with one send~ but it is an error to have two send~s of the same name.;
-#X obj 179 344 tabreceive~;
-#X text 405 368 updated for Pd version 0.33.;
-#X obj 148 187 sig~ 25;
-#X obj 148 215 send~ signal2;
-#X msg 355 139 set signal2;
-#X msg 356 161 set signal1;
-#X text 34 287 Send~/Receive~ only work for the default block size (64) \; for FFT applications see also:;
-#X text 35 262 Receive~ takes "set" messages to switch between send~s.;
-#X connect 1 0 4 0;
-#X connect 3 0 2 0;
-#X connect 4 0 0 0;
-#X connect 8 0 9 0;
-#X connect 8 0 10 0;
-#X connect 9 0 4 0;
-#X connect 11 0 3 0;
-#X connect 15 0 16 0;
-#X connect 17 0 1 0;
-#X connect 18 0 1 0;