If you're using Pd 0.4.6+, look at the help for [oscformat] which you can use in place of mrpeach packOSC. Basically:
[1.23 < <-- message or list to send | [oscformat /osc/address] <- set address and format incoming data | [list prepend send] | [list trim] | [netsend -u -b]
From: "Peter P." peterparker@fastmail.com
To: "pd-list@iem.at" pd-list@iem.at Cc: Date: Thu, 12 Mar 2015 17:09:40 +0100 Subject: [PD] OSC over netsend -u -b Hi list,
I am trying to send OSC messages over [netsend -u -b] which I formatted using [packOSC] from mrpeach net library without any further modification (as I would do using [udpsend]).
I get on the console: netsend: no method for 'float' supposedly because [netsend] expects the keyword "send" followed by a list of numbers to send.
Since OSC messages formatted by packOSC vary in length, how could I send data over [netsend -u -b]?
Thanks for any ideas! P
Hi Dan, list,
- Dan Wilcox danomatika@gmail.com [2015-03-12 17:31]:
If you're using Pd 0.4.6+, look at the help for [oscformat] which you can use in place of mrpeach packOSC.
Oh yes, thank you for pointing this new one out to me. It works nicely. Although:
Basically:
[1.23 < <-- message or list to send | [oscformat /osc/address] <- set address and format incoming data
I wonder if there is a way to set the address and payload using one message rather than the object arguments? Like in
[/foo/bar/one 1 < | [oscformat]
but this seems not to work. But nice that the object argumets can be divided by slashes as well as by spaces, which is not mentioned in the help file (yet).
cheers, P
Split the list and convert the first element into a set message. Then pipe the rest of the list (2nd outlet of [list split 1] into [oscformat).
[list split 1] | [set $1 < | [oscformat]
On Thu, Mar 12, 2015 at 12:49 PM, Peter P. peterparker@fastmail.com wrote:
Hi Dan, list,
- Dan Wilcox danomatika@gmail.com [2015-03-12 17:31]:
If you're using Pd 0.4.6+, look at the help for [oscformat] which you can use in place of mrpeach packOSC.
Oh yes, thank you for pointing this new one out to me. It works nicely. Although:
Basically:
[1.23 < <-- message or list to send | [oscformat /osc/address] <- set address and format incoming data
I wonder if there is a way to set the address and payload using one message rather than the object arguments? Like in
[/foo/bar/one 1 < | [oscformat]
but this seems not to work. But nice that the object argumets can be divided by slashes as well as by spaces, which is not mentioned in the help file (yet).
cheers, P
Dear Dan, list,
- Dan Wilcox danomatika@gmail.com [2015-03-12 17:53]:
Split the list and convert the first element into a set message. Then pipe the rest of the list (2nd outlet of [list split 1] into [oscformat).
[list split 1] | [set $1 < | [oscformat]
Thank you! That would be an option.
I am now wondering how to route OSC messages I get from oscparse. I would love a behavior similar to routeOSC but would like to stay within vanilla Pd.
The internal [route] object itself does not allow to parse more than one layer of OSC address space when receiving messages from oscparse and seems to have problem with numbers in the address.
Any ideas are very welcome! Thank you! P
I am now wondering how to route OSC messages I get from oscparse. I would love a behavior similar to routeOSC but would like to stay within vanilla Pd.
The internal [route] object itself does not allow to parse more than one layer of OSC address space when receiving messages from
So you use more than one ….
[oscparse] | [route part1] | [route part2]
oscparse and seems to have problem with numbers in the address.
There was a discussion earlier on the list about it not handling numbers in the address.
Dan Wilcox @danomatika danomatika.com http://danomatika.com/ robotcowboy.com http://robotcowboy.com/
Also, of interest, is a little tutorial patch I wrote when I was learning the new osc objects:
Dan Wilcox @danomatika danomatika.com http://danomatika.com/ robotcowboy.com http://robotcowboy.com/
On Mar 12, 2015, at 2:19 PM, Dan Wilcox danomatika@gmail.com wrote:
I am now wondering how to route OSC messages I get from oscparse. I would love a behavior similar to routeOSC but would like to stay within vanilla Pd.
The internal [route] object itself does not allow to parse more than one layer of OSC address space when receiving messages from
So you use more than one ….
[oscparse] | [route part1] | [route part2]
oscparse and seems to have problem with numbers in the address.
There was a discussion earlier on the list about it not handling numbers in the address.
Dan Wilcox @danomatika danomatika.com http://danomatika.com/ robotcowboy.com http://robotcowboy.com/
On 03/12/2015 05:52 PM, Dan Wilcox wrote:
Split the list and convert the first element into a set message. Then pipe the rest of the list (2nd outlet of [list split 1] into [oscformat).
just make sure that the "set" message arrives at the [oscformat] object before the remainder of the list...
gfadsr IOhannes
-
Dan Wilcox -
IOhannes m zmölnig -
Peter P.