<div dir="ltr">hi,<div>a somewhat related question:</div><div>I'm trying to do something like this:</div><div>[routeOSC /*/ID]</div><div>but that doesn't seem to work</div><div>Is it at all possible to use wildcards with routeOSC?</div>
<div>help patch only mentions "[set /*( this will match any OSC message"...</div><div>thanks,</div><div>Tim</div><div><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">2013/8/8 IOhannes m zmoelnig <span dir="ltr"><<a href="mailto:zmoelnig@iem.at" target="_blank">zmoelnig@iem.at</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">-----BEGIN PGP SIGNED MESSAGE-----<br>
Hash: SHA1<br>
<div class="im"><br>
On 2013-08-07 15:12, Colet Patrice wrote:<br>
> Le 07/08/2013 08:15, <a href="mailto:puredata@11h11.com">puredata@11h11.com</a> a écrit :<br>
>> hi all,<br>
>><br>
>> i have more than 50 OSC messages to [routeOSC], i would like to<br>
>> avoid having to cut and paste & click and drag. what are my<br>
>> options here?<br>
>><br>
>> [routeOSC /knob1 /knob2 ...] | | [s $0-knob1] [s<br>
>> $0-knob2]<br>
>><br>
>> thanks<br>
><br>
> someting like this, and no need for routeOSC<br>
><br>
> [dumpOSC]-[set $1 $2, bang(--[ (<br>
<br>
</div>[dumpOSC]?<br>
is this zombi still around?<br>
<br>
><br>
> [r /knob1]<br>
><br>
<br>
this is basically the same as roman's solution, but imho both miss<br>
some points:<br>
<br>
- - by switching from [routeOSC] to you lose pattern matching.<br>
the OSC-message `/knob* 0` should set *all* knobs<br>
<br>
- - you are giving up localization. where's the $0 gone to?<br>
<br>
- - you assume a fixed format of the knob message, namely that it has<br>
exactly one argument.<br>
<br>
<br>
something like this should be better:<br>
<br>
[routOSC /knobs]<br>
|<br>
[t a a]<br>
| |<br>
| [symbol]<br>
| |<br>
| [pack s $0]<br>
| |<br>
| [symbol $2-$1(<br>
| |<br>
[list split 1] |<br>
| |<br>
[send ]<br>
<br>
<br>
which still doesn't give you pattern matching.<br>
<br>
<br>
i once did a send-based solution with pattern matching which was quite<br>
complicated.<br>
it would include a address-registration, where each [receive] would<br>
register it's name, e.g. "/foo/knob1/value", using a wrapper<br>
abstraction around [r].<br>
all these labels were filled into a central pattern-matching object<br>
(zexy's [matchbox] was made for this).<br>
the output of [unpackOSC] would be split into the address and the<br>
arguments, the address gets expanded by [matchbox] to all possible<br>
targets and the data is sent to those targets using a dynamic send.<br>
<br>
[routeOSC] should be faster though, as it can operate on a more local<br>
level. (thus having to compare against less possibilities).<br>
<br>
<br>
mfgasdr<br>
IOhannes<br>
-----BEGIN PGP SIGNATURE-----<br>
Version: GnuPG v1.4.14 (GNU/Linux)<br>
Comment: Using GnuPG with Icedove - <a href="http://www.enigmail.net/" target="_blank">http://www.enigmail.net/</a><br>
<br>
iEYEARECAAYFAlIDZjAACgkQkX2Xpv6ydvQSvACdEqlHGVTxK8yFAhT7GyeOEac0<br>
ZC0AoOsXXaSqu3/DqB5zioQqmLwNBwMA<br>
=O3d2<br>
-----END PGP SIGNATURE-----<br>
<div class="HOEnZb"><div class="h5"><br>
_______________________________________________<br>
<a href="mailto:Pd-list@iem.at">Pd-list@iem.at</a> mailing list<br>
UNSUBSCRIBE and account-management -> <a href="http://lists.puredata.info/listinfo/pd-list" target="_blank">http://lists.puredata.info/listinfo/pd-list</a><br>
</div></div></blockquote></div><br></div>