hi list
i'd like to use osc for controlling a rather big number of abstracts.
because the "voice numbers" are contained in the path part of the osc
messages i currently have to do something like
[OSCroute /0 /1 /2 /3 /4 /5 /6 ...]
is there a way to split off the first path part of an osc message? e.g.
[OSCfirstpathcomponent] | | <number or symbol> <rest of osc message>
like this i could clean up my patches and feed the stuff to nqpoly4
easily.
cheers lorenz
Hallo, Lorenz Schori hat gesagt: // Lorenz Schori wrote:
i'd like to use osc for controlling a rather big number of abstracts.
because the "voice numbers" are contained in the path part of the osc
messages i currently have to do something like[OSCroute /0 /1 /2 /3 /4 /5 /6 ...]
is there a way to split off the first path part of an osc message? e.g.
[OSCfirstpathcomponent] | | <number or symbol> <rest of osc message>
You can get the <rest of osc message> part using [OSCroute /*], and to get the first element, you could use [s2l /]---[$1( from zexy and maybe prepending [symbol $1( to the incoming OSC message. However all trailing arguments to the OSC message will be lost in the list, that s2l procudes.
Frank Barknecht _ ______footils.org__
_ __latest track: "scans" _ http://footils.org/cms/show/41
hallo frank
Am 28.06.2005 um 12:50 schrieb Frank Barknecht:
is there a way to split off the first path part of an osc message?
e.g.[OSCfirstpathcomponent] | | <number or symbol> <rest of osc message>
You can get the <rest of osc message> part using [OSCroute /*],
nope. pattern matching does not work this way around. only incomming
osc messages can have wildcards.
perhaps an object - i name it [OSCmatch] - would be better for my
application. arguments would be a single OSC pattern and the outlets
could be $1 the first partial match, $2 the second, ..., $n the rest
of the osc message with the arguments. much like regular expressions.
e.g
/4/pitch 33 | [OSCmatch /*] | | | /pitch 33 4
or
/table/3/8/store 34.2 | [OSCmatch /table/*/*] | | | 3 8 store 34.2
and to get the first element, you could use [s2l /]---[$1( from zexy and maybe prepending [symbol $1( to the incoming OSC message. However all trailing arguments to the OSC message will be lost in the list, that s2l procudes.
thank you, this sort of works. but the problem is the rest of the osc
message.
Hallo, Lorenz Schori hat gesagt: // Lorenz Schori wrote:
hallo frank
Am 28.06.2005 um 12:50 schrieb Frank Barknecht:
is there a way to split off the first path part of an osc message?
e.g.[OSCfirstpathcomponent] | | <number or symbol> <rest of osc message>
You can get the <rest of osc message> part using [OSCroute /*],
nope. pattern matching does not work this way around. only incomming
osc messages can have wildcards.
There is a special target called "/*" that is used to strip off the first part, as I described it. Just try it.
Frank Barknecht _ ______footils.org__
_ __latest track: "scans" _ http://footils.org/cms/show/41
Am 28.06.2005 um 16:09 schrieb Frank Barknecht:
nope. pattern matching does not work this way around. only incomming osc messages can have wildcards.
There is a special target called "/*" that is used to strip off the first part, as I described it. Just try it.
does not work for me. i worked around it using [niagara]/[glue] [s2l]/ [l2s]...
i use Pd-0.38-4-extended-RC1.app from hans on osx 10.4.1 and OSCx
"ver: 0.2, compiled: Apr 6 2005."
Hallo, Lorenz Schori hat gesagt: // Lorenz Schori wrote:
does not work for me. i worked around it using [niagara]/[glue] [s2l]/ [l2s]...
i use Pd-0.38-4-extended-RC1.app from hans on osx 10.4.1 and OSCx
"ver: 0.2, compiled: Apr 6 2005."
Hm, you're right, the current version in CVS has that feature removed. This is very bad, as dozens of my patches still rely on it. I have no idea, why it was removed, to my knowledge the corresponding Max object still has "OSCroute /*"
Frank Barknecht _ ______footils.org__
_ __latest track: "scans" _ http://footils.org/cms/show/41
Hallo, Frank Barknecht hat gesagt: // Frank Barknecht wrote:
Hm, you're right, the current version in CVS has that feature removed. This is very bad, as dozens of my patches still rely on it. I have no idea, why it was removed, to my knowledge the corresponding Max object still has "OSCroute /*"
And also it is still in the help-patch OSCroute-help.pd.
Frank Barknecht _ ______footils.org__
_ __latest track: "scans" _ http://footils.org/cms/show/41
Hallo, Lorenz Schori hat gesagt: // Lorenz Schori wrote:
does not work for me. i worked around it using [niagara]/[glue] [s2l]/ [l2s]...
i use Pd-0.38-4-extended-RC1.app from hans on osx 10.4.1 and OSCx
"ver: 0.2, compiled: Apr 6 2005."
Okay, if you follow osc_dev, you might have seen my questions regarding this. I now added the solution, Matt Wright choose for the Max objects to the Pd OSCroute.c as well, so if you - after the Sourceforge delay of about 1 day - update your CVS copy, you will get the [OSCroute /*] behaviour back, as described in the help patch.
If you don't want to wait, I attached the new source, too.
Frank Barknecht _ ______footils.org__
_ __latest track: "scans" _ http://footils.org/cms/show/41
thanks. it does the job now.
Am 28.06.2005 um 20:43 schrieb Frank Barknecht:
Hallo, Lorenz Schori hat gesagt: // Lorenz Schori wrote:
does not work for me. i worked around it using [niagara]/[glue]
[s2l]/ [l2s]...i use Pd-0.38-4-extended-RC1.app from hans on osx 10.4.1 and OSCx "ver: 0.2, compiled: Apr 6 2005."
Okay, if you follow osc_dev, you might have seen my questions regarding this. I now added the solution, Matt Wright choose for the Max objects to the Pd OSCroute.c as well, so if you - after the Sourceforge delay of about 1 day - update your CVS copy, you will get the [OSCroute /*] behaviour back, as described in the help patch.
If you don't want to wait, I attached the new source, too.
Ciao
Frank Barknecht _ ______footils.org__
_ __latest track: "scans" _ http://footils.org/cms/show/41
<OSCroute.c.gz> _______________________________________________ PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/ listinfo/pd-list