-
Notifications
You must be signed in to change notification settings - Fork 29
/
OSCbundle.xml
118 lines (100 loc) · 3.67 KB
/
OSCbundle.xml
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
<refentry id="OSCbundle">
<indexterm id="IndexOSCbundle"><primary>OSCbundle</primary></indexterm>
<refentryinfo><title>OSC</title></refentryinfo>
<refmeta>
<refentrytitle>OSCbundle</refentrytitle>
</refmeta>
<refnamediv>
<refname>OSCbundle</refname>
<refpurpose>
Sends data to other processes using the OSC protocol by packing
messages in a bundle.
</refpurpose>
</refnamediv>
<refsect1>
<title>Description</title>
<para>
Uses the OSC protocol to send one or more messages to other OSC listening
processes in a single bundle. Unlike OSCsend, it can be used to
send multiple messages at the same time, but only standard OSC numeric types
are allowed.
</para>
</refsect1>
<refsect1>
<title>Syntax</title>
<synopsis><command>OSCbundle</command> kwhen, ihost, iport,
Sdest[], Stype[],kArgs[][][,isize]</synopsis>
</refsect1>
<refsect1>
<title>Initialization</title>
<para>
<emphasis>ihost</emphasis>
-- a string that is the intended host computer domain name. An
empty string is interpreted as the current computer.
</para>
<para>
<emphasis>iport</emphasis>
-- the number of the port that is used for the communication.
</para>
<para>
<emphasis>isize</emphasis>
-- maximum packet size in bytes, defaults to 65536.
</para>
</refsect1>
<refsect1>
<title>Performance</title>
<para>
<emphasis>kwhen</emphasis> -- a bundle of messages is sent whenever this
value changes. A message will always be sent on the first call.
</para>
<para>
<emphasis> Sdest[]</emphasis>
-- an array of strings containing the destination address for
each message. Length must agree with Stype[].
</para>
<para>
<emphasis>Stype[]</emphasis>
-- an array of strings containing the types for each
message. Only numeric types ('i' for integers and 'f' for
floats) are supported. Length must agree with Sdest[].
</para>
<para>
<emphasis>kArg[][]</emphasis> -- a two-dimensional array
containing the arguments for each message. Its dimension 1
(number of rows) must agree with Sdest[] and Stype[]. Its
dimension 2 (number of columns) must be large enough to
accommodate the message with the largest number of
arguments. Each row should contain the arguments for the types
of each message. If a row contains fewer arguments, any
remaining data items are filled with zeros. Arguments in excess
of what each type string requires are ignored.
</para>
</refsect1>
<refsect1>
<title>Example</title>
<para>
Here is an example of the OSCBundle opcode. It uses the file <ulink url="examples/oscbundle.csd"><citetitle>oscbundle.csd</citetitle></ulink>.
<example>
<title>Example of the OSCbundle opcode.</title>
<para>See the sections <link linkend="UsingRealTime"><citetitle>Real-time Audio</citetitle></link> and <link linkend="CommandFlags"><citetitle>Command Line Flags</citetitle></link> for more information on using command line flags.</para>
<xi:include href="examples-xml/oscbundle.csd.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
</example>
</para>
</refsect1>
<refsect1>
<title>See Also</title>
<para>
<link linkend="OSClisten"><citetitle>OSClisten</citetitle></link>,
<link linkend="OSCinit"><citetitle>OSCinit</citetitle></link>
</para>
</refsect1>
<refsect1>
<title>Credits</title>
<para>
<simplelist>
<member>Author: &namevictor;</member>
<member>2018</member>
</simplelist>
</para>
</refsect1>
</refentry>