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
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
|
#N canvas 281 92 863 548 10;
#X text 9 28 GETTING YOUR MESSAGE ACROSS;
#X text 10 43 The [send] and [receive] objects are useful for linking
objects and subroutines together in a single canvas or throughout multiple
patches. Understanding these objects will help 'clean up' your patches
and allow you to communicate messages between various modules that
you build or between objects where patch cords are not possible.;
#X text 10 175 In the [send] and [receive] help files \, you will see
message sent within a single patch - from a [send] object to a [receive]
object in the same patch. But the functionality of these objects goes
far beyond the scope of a single patch.;
#X text 10 385 A [send] object is a little like a radio station...it
broadcasts information throughout Pd \, for all the [receives] to hear!
A [receive] object is a little like your own AM/FM tuner...it will
receive messages from all the [send] objects that it is 'tuned' to.
Hence \, naming your [send] and [receive] objects becomes very important.
A [receive] object named "dave" (as in [receive dave]) will pick up
all messages from [send dave] \, regardless of which patch it is in.
In this manner \, you can get messages across multiple patches \, or
into abstractions or subpatches -- without patch cords.;
#X text 439 42 However \, controlling the 'scope' of a [send] or [receive]
object is important if you want to ensure that a message is only transmitted
within a single patch \, or within a single abstraction. Check out
the following information about 'scope' and 'locality'.;
#X obj 466 121 all_about_scope_and_locality and inheritance;
#X text 530 471 hmm...also see;
#N canvas 0 123 827 456 special-send-and-receives 0;
#X text 19 10 SPECIAL OBJECTS;
#X obj 28 41 bng 15 250 50 0 empty empty empty 0 -6 0 8 -262144 -1
-1;
#X obj 28 66 tgl 15 0 empty empty empty 0 -6 0 8 -262144 -1 -1 0 1
;
#X obj 28 91 nbx 5 14 -1e+37 1e+37 0 0 empty empty empty 0 -6 0 10
-262144 -1 -1 0 256;
#X obj 28 117 vsl 15 128 0 127 0 0 empty empty empty 0 -8 0 8 -262144
-1 -1 0 1;
#X obj 21 386 hdl 15 1 0 8 empty empty empty 0 -6 0 8 -262144 -1 -1
0;
#X obj 154 119 vdl 15 1 0 8 empty empty empty 0 -6 0 8 -262144 -1 -1
0;
#X obj 24 343 hsl 128 15 0 127 0 0 empty empty empty -2 -6 0 8 -262144
-1 -1 0 1;
#X obj 59 208 vu 15 120 empty empty -1 -8 0 8 -66577 -1 1 0;
#X obj 175 20 cnv 15 100 60 empty empty empty 20 12 0 14 -233017 -66577
0;
#X text 46 40 bng;
#X text 46 65 toggle;
#X text 85 89 number 2;
#X text 15 167 Vertical Slider;
#X text 147 166 Vertical Dial;
#X text 40 356 Horizontal Slider;
#X text 42 401 Horizontal Dial;
#X text 101 260 VU Meter;
#X text 202 39 canvas;
#X text 296 55 The objects in this patch \, and likely many more which
I have not included \, include their own send and receive functionality.
This functionality can be accessed by right-clicking on the object
and choosing "Properties" from the menu that appears.;
#X text 289 149 EXAMPLE;
#X text 303 170 In other words \, these objects can send and/or receive
messages without attaching a separate [send] or [receive] object to
them with a patch cord.;
#X text 290 232 THE OL'FASHION WAY;
#X floatatom 296 256 5 0 0 0 - - -;
#X floatatom 350 283 5 0 0 0 - - -;
#X obj 296 280 s a;
#X obj 350 255 r a;
#X text 290 315 USING THESE OBJECTS' INTERNAL SEND AND RECEIVE FUNCTIONALITY
;
#X text 405 259 As you see here \, these number boxes are linked together
with send and receives objects.;
#X obj 301 337 nbx 5 14 -1e+37 1e+37 0 0 b empty empty 0 -6 0 10 -262144
-1 -1 0 256;
#X obj 363 337 nbx 5 14 -1e+37 1e+37 0 0 empty b empty 0 -6 0 10 -262144
-1 -1 0 256;
#X text 310 360 These number boxes are linked together via their 'send'
or 'receive' property.;
#X text 298 8 Some objects in Pd contain their own internal send and
receive functionality.;
#X connect 23 0 25 0;
#X connect 26 0 24 0;
#X restore 639 471 pd special-send-and-receives;
#X obj 4 4 cnv 15 850 20 empty empty all_about_send_n_receive 20 10
1 18 -233017 -66577 0;
#X obj 821 5 pddp;
#X obj 16 290 send one_send;
#X obj 16 334 receive one_send;
#X obj 19 272 hsl 128 15 0 127 0 0 empty empty empty -2 -6 0 8 -262144
-1 -1 0 0;
#X obj 153 290 send one_send;
#X obj 156 272 hsl 128 15 0 127 0 0 empty empty empty -2 -6 0 8 -262144
-1 -1 0 0;
#X obj 291 290 send one_send;
#X obj 294 272 hsl 128 15 0 127 0 0 empty empty empty -2 -6 0 8 -262144
-1 -1 0 0;
#X obj 19 355 hsl 128 15 0 127 0 0 empty empty empty -2 -6 0 8 -262144
-1 -1 0 1;
#X obj 153 334 receive one_send;
#X obj 156 355 hsl 128 15 0 127 0 0 empty empty empty -2 -6 0 8 -262144
-1 -1 0 1;
#X obj 291 334 receive one_send;
#X obj 294 355 hsl 128 15 0 127 0 0 empty empty empty -2 -6 0 8 -262144
-1 -1 0 1;
#X text 7 317 All [receive]s of the same name will receive the "messages":
;
#X text 9 252 You can have multiple [send]s with the same name:;
#N canvas 0 22 454 304 Related 0;
#X obj 16 39 universal;
#X obj 17 76 send13;
#X obj 66 76 receive13;
#X restore 639 497 pd Related Objects;
#X floatatom 45 132 5 0 0 0 - - -;
#X floatatom 99 152 5 0 0 0 - - -;
#X obj 45 149 s aNum;
#X obj 99 131 r aNum;
#X obj 213 150 s aSymbol;
#X msg 213 130 symbol hello;
#X obj 310 130 r aSymbol;
#X symbolatom 310 152 10 0 0 0 - - -;
#X connect 11 0 17 0;
#X connect 12 0 10 0;
#X connect 14 0 13 0;
#X connect 16 0 15 0;
#X connect 18 0 19 0;
#X connect 20 0 21 0;
#X connect 25 0 27 0;
#X connect 28 0 26 0;
#X connect 30 0 29 0;
#X connect 31 0 32 0;
|
