unknown
1970-01-01 00:00:00 UTC
<div><br></div><div>In any case, if we need clients to get ack replies on w=
hether their control change has reached the target, we should use TCP/IP an=
d not try to reinvent the transport layer. But this can be decided later on=
ce we have real world use cases with dropped messages.</div>
<div><br></div><div>Distinction between "control" and "data&=
quot;</div><div>-----------------</div><div><br></div><div>As I said, the d=
istinction between control and data is quite easy: "control" refe=
rs to anything that we could change from a GUI and has a "current valu=
e" (state).</div>
<div><br></div><div>Here is an example with 3 devices (1 captor, 2 processo=
rs):</div> <div><br></div><div>[captor] ----X: data (matrix) ---> [feature extracti=
on] --- y: control cutoff (float) ---> [sound synthesis]</div><div><br><=
/div><div>Obviously, we can change "cutoff" value from a GUI so &=
quot;y" is a control signal. We could not simulate the captor values w=
ith a widget so "X" is "data".</div>
<div><br></div><div><div>Internal calls</div><div>------------------</div><=
/div><div><br></div><div>The setup above with 3 devices could as well be mo=
deled with 3 objects in a single device with message sending happening in s=
hared memory.
hether their control change has reached the target, we should use TCP/IP an=
d not try to reinvent the transport layer. But this can be decided later on=
ce we have real world use cases with dropped messages.</div>
<div><br></div><div>Distinction between "control" and "data&=
quot;</div><div>-----------------</div><div><br></div><div>As I said, the d=
istinction between control and data is quite easy: "control" refe=
rs to anything that we could change from a GUI and has a "current valu=
e" (state).</div>
<div><br></div><div>Here is an example with 3 devices (1 captor, 2 processo=
rs):</div> <div><br></div><div>[captor] ----X: data (matrix) ---> [feature extracti=
on] --- y: control cutoff (float) ---> [sound synthesis]</div><div><br><=
/div><div>Obviously, we can change "cutoff" value from a GUI so &=
quot;y" is a control signal. We could not simulate the captor values w=
ith a widget so "X" is "data".</div>
<div><br></div><div><div>Internal calls</div><div>------------------</div><=
/div><div><br></div><div>The setup above with 3 devices could as well be mo=
deled with 3 objects in a single device with message sending happening in s=
hared memory.