On Thu, Mar 16, 2006 at 07:43:21PM +0100, pd-list-request@iem.at wrote:
Message: 7 Date: Thu, 16 Mar 2006 11:55:41 -0500 From: Martin Peach martinrp@vax2.concordia.ca Subject: Re: [PD] Re: [PD-dev] We've got to undo the MIDI revolution!
- Where isOSC?!
To: geiger geiger@xdv.org Cc: Mathieu Bouchard matju@artengine.ca, pd-list@iem.at, Frank Barknecht fbar@footils.org Message-ID: 4419988D.8080403@vax2.concordia.ca Content-Type: text/plain; format=flowed; charset=ISO-8859-1
geiger wrote:
On Wed, 15 Mar 2006, Mathieu Bouchard wrote:
FUDI wasn't designed to "undo" the MIDI revolution.
Is there OSC over RS232 ?
OSC doesn't specify the transport layer AFAIK, so yes, there is. If your question is if there is an implementation, then I would say I don't think so. You will see more implementations of the MIDI protocol over RS232 (MIDI hardware != RS232) because MIDI is easier to implement.
Complicated compared to what? As far as PD goes, it would be nice to have the OSC objects use the same code as netsend and netreceive, that way TCP could be used as well as
As far as I can tell, all that would be needed to acheive this is an object called [stol] (symbol to list) in Pd canonical. This object is like Perl's "split" function and it would take a character (such as "/") as it's first argument. Then you could just go:
[netrecieve myport 1] | [list split 1] | | [stol /] | | | | | | [...list split or route value bits here...] | [...list split or route path bits here...]
Sending OSC udp packets to myport. N'est pas?
I'm sure someone must have coded something like [stol] already. Let's push to get it into Pd and then we can have OSC without the extra overhead of external libraries etc.
Best,
Chris.
chris@mccormick.cx http://mccormick.cx
As far as I can tell, all that would be needed to acheive this is an object called [stol] (symbol to list) in Pd canonical. This object is like Perl's "split" function and it would take a character (such as "/") as it's first argument. Then you could just go:
[netrecieve myport 1] | [list split 1] | | [stol /] | | | | | | [...list split or route value bits here...] | [...list split or route path bits here...]
Sending OSC udp packets to myport. N'est pas?
i dont think that will work..OSC is encoded a specific way, using a typetag and combinations of various kinds of big endian numbers and ASCII text, zero padding to byte boundaries to delimit messages/message-components (the typetags and path are treated as a string). netsend uses ASCII text for everything and uses ";" to delimit..
see http://www.cnmat.berkeley.edu/OpenSoundControl/OSC-spec-examples.html
its simple to implement, but impossible to implement in PD, as a patch...since you cant stream 'bytes' around the way you can floats or symbols or lists...
On Friday 17 Mar 2006 02:17, Chris McCormick wrote:
As far as I can tell, all that would be needed to acheive this is an object called [stol] (symbol to list) in Pd canonical. This object is like Perl's "split" function and it would take a character (such as "/") as it's first argument. Then you could just go:
[netrecieve myport 1]
[list split 1]
[stol /] |
| [...list split or route value bits here...]
[...list split or route path bits here...]
Sending OSC udp packets to myport. N'est pas?
You're forgetting that you'd want to be able to communicate with non-pd osc apps over UDP. With this approach, the data would go (from pd to pd), but it would be wrapped in pd's udp format.
robert.
-
cdr -
Chris McCormick -
Robert Scott