unknown
1970-01-01 00:00:00 UTC
<div><br></div><div>For sure this is of interest, and I'll keep my mind=
opened to this topic next time we use OSC around here (probably next week)=
.</div><div><br></div><div>Best,</div><div>Pedro<br><br><div class=3D"gmail=
_quote">
On Fri, Dec 23, 2011 at 5:37 PM, Adrian Freed <span dir=3D"ltr"><<a href=
=3D"mailto:***@cnmat.berkeley.edu">***@cnmat.berkeley.edu</a>></sp=
an> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex">
<div class=3D"im"><br>
On Dec 23, 2011, at 6:21 AM, Th=E9o de la Hogue wrote:<br>
<br>
> Hi everybody,<br>
> I'm involved into the Jamoma project which proposed, among other t=
hings, a syntax to structure a Max patchers into sharable modules.<br>
> Any jamoma parameter is registered into a tree structure following the=
OSC address pattern style.<br>
> So, even if it's still not possible in the 0.5 version, we plan to=
be able to handle the '*' and the "{foo, bar}" to addres=
s all or a set of parameter instances.<br>
><br>
> For example those features are expected for spatialisation parameters =
control where many sources and speakers have to be handled. It could provid=
ed an easier way deal with multiple instances by sending some messages like=
/source.*/position 0. 0. 0. for an initialisation process or /speaker.{1, =
3, 5}/gain 0.3 to control in one message the left side of a surround system=
(as you can notice, the '.' is used to precise the instance part w=
hich is not very OSC compliant but very usefull for parsing !)<br>
</div>Thanks Theo.<br>
The use of "." in Jamoma is not inconsistent with OSC goals in ge=
neral. The idea of the address space is that is designed for the applicatio=
n by the users and it isn't necessary<br>
to use a hierarchical name space as implied but not required by the "/=
" symbol. It is easy to design a name space that is like the named att=
ributes of databases and HTTP GET requests, for example.<br>
As we clarify and "modernise" the 1.0 specification we will try t=
o emphasize these diverse uses of OSC names which were designed and documen=
ted in an the era of hierarchical file systems by us folk also familiar wit=
h more general models, e.g. Lisp property lists.<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
<br>
_______________________________________________<br>
OSC_dev mailing list<br>
<a href=3D"mailto:***@create.ucsb.edu">***@create.ucsb.edu</a><br>
<a href=3D"http://lists.create.ucsb.edu/mailman/listinfo/osc_dev" target=3D=
"_blank">http://lists.create.ucsb.edu/mailman/listinfo/osc_dev</a><br>
</div></div></blockquote></div><br><br clear=3D"all"><div><br></div>-- <br>=
Pedro Lopes (HCI Researcher / MSc)<br>contact: <a href=3D"mailto:pedro.lope=
***@ist.utl.pt" target=3D"_blank">***@ist.utl.pt</a><br>website:=A0<a=
href=3D"http://web.ist.utl.pt/pedro.lopes/" target=3D"_blank">http://web.i=
st.utl.pt/pedro.lopes</a>=A0/=A0<a href=3D"http://pedrolopesresearch.wordpr=
ess.com/" target=3D"_blank">http://pedrolopesresearch.wordpress.com/</a>=A0=
|=A0<a href=3D"http://twitter.com/plopesresearch" target=3D"_blank">http://=
twitter.com/plopesresearch</a><br>
</div>
--20cf303a2c19c76a1c04b4c651d0--
opened to this topic next time we use OSC around here (probably next week)=
.</div><div><br></div><div>Best,</div><div>Pedro<br><br><div class=3D"gmail=
_quote">
On Fri, Dec 23, 2011 at 5:37 PM, Adrian Freed <span dir=3D"ltr"><<a href=
=3D"mailto:***@cnmat.berkeley.edu">***@cnmat.berkeley.edu</a>></sp=
an> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex">
<div class=3D"im"><br>
On Dec 23, 2011, at 6:21 AM, Th=E9o de la Hogue wrote:<br>
<br>
> Hi everybody,<br>
> I'm involved into the Jamoma project which proposed, among other t=
hings, a syntax to structure a Max patchers into sharable modules.<br>
> Any jamoma parameter is registered into a tree structure following the=
OSC address pattern style.<br>
> So, even if it's still not possible in the 0.5 version, we plan to=
be able to handle the '*' and the "{foo, bar}" to addres=
s all or a set of parameter instances.<br>
><br>
> For example those features are expected for spatialisation parameters =
control where many sources and speakers have to be handled. It could provid=
ed an easier way deal with multiple instances by sending some messages like=
/source.*/position 0. 0. 0. for an initialisation process or /speaker.{1, =
3, 5}/gain 0.3 to control in one message the left side of a surround system=
(as you can notice, the '.' is used to precise the instance part w=
hich is not very OSC compliant but very usefull for parsing !)<br>
</div>Thanks Theo.<br>
The use of "." in Jamoma is not inconsistent with OSC goals in ge=
neral. The idea of the address space is that is designed for the applicatio=
n by the users and it isn't necessary<br>
to use a hierarchical name space as implied but not required by the "/=
" symbol. It is easy to design a name space that is like the named att=
ributes of databases and HTTP GET requests, for example.<br>
As we clarify and "modernise" the 1.0 specification we will try t=
o emphasize these diverse uses of OSC names which were designed and documen=
ted in an the era of hierarchical file systems by us folk also familiar wit=
h more general models, e.g. Lisp property lists.<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
<br>
_______________________________________________<br>
OSC_dev mailing list<br>
<a href=3D"mailto:***@create.ucsb.edu">***@create.ucsb.edu</a><br>
<a href=3D"http://lists.create.ucsb.edu/mailman/listinfo/osc_dev" target=3D=
"_blank">http://lists.create.ucsb.edu/mailman/listinfo/osc_dev</a><br>
</div></div></blockquote></div><br><br clear=3D"all"><div><br></div>-- <br>=
Pedro Lopes (HCI Researcher / MSc)<br>contact: <a href=3D"mailto:pedro.lope=
***@ist.utl.pt" target=3D"_blank">***@ist.utl.pt</a><br>website:=A0<a=
href=3D"http://web.ist.utl.pt/pedro.lopes/" target=3D"_blank">http://web.i=
st.utl.pt/pedro.lopes</a>=A0/=A0<a href=3D"http://pedrolopesresearch.wordpr=
ess.com/" target=3D"_blank">http://pedrolopesresearch.wordpress.com/</a>=A0=
|=A0<a href=3D"http://twitter.com/plopesresearch" target=3D"_blank">http://=
twitter.com/plopesresearch</a><br>
</div>
--20cf303a2c19c76a1c04b4c651d0--