Hi pders, just a simple question :
what's the real difference for you between netsend/netreceive/netserver & OSC objects?
I don't see real difference between both of it in term of transmitting a tcp/udp message through network...
Maybe I missed something amazing somewhere...
thanx
juto
If I'm correct, OSC sends only UDP, which doesn't have any packet verification. I don't really know what that means or how it works but I remember reading that somewhere.
If another program is OSC-capable it sort of streamlines the message process. I often use OSC between Processing and Pd and it's super easy.
Kevin
On 2/4/07, juto aviten periclite@free.fr wrote:
Hi pders, just a simple question :
what's the real difference for you between netsend/netreceive/netserver & OSC objects?
I don't see real difference between both of it in term of transmitting a tcp/udp message through network...
Maybe I missed something amazing somewhere...
thanx
juto
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
hi
On Sun, 2007-02-04 at 10:21 -0600, Kevin McCoy wrote:
If I'm correct, OSC sends only UDP, which doesn't have any packet verification. I don't really know what that means or how it works but I remember reading that somewhere.
osc is not really bound to udp, although (unfortunately) most implementation just use udp.
pd's netsend/netreceive protocol is sending data in plain text, while osc adds some type information and can join several messages into bundles, which are processed at once ...
hth ... tim
-- tim@klingt.org ICQ: 96771783 http://www.mokabar.tk
Every word is like an unnecessary stain on silence and nothingness Samuel Beckett
do you mean OSC could some headers in the bundles for exemple? or multiple messages could be send in the same bundles? ... otherwise from what Kevin wrote a difference could that OSC could be used in different softwre to communicate with each others and netsend/receive is only for PD... right?
cheers
juto
osc is not really bound to udp, although (unfortunately) most implementation just use udp.
pd's netsend/netreceive protocol is sending data in plain text, while osc adds some type information and can join several messages into bundles, which are processed at once ...
hth ... tim
-- tim@klingt.org ICQ: 96771783 http://www.mokabar.tk
Every word is like an unnecessary stain on silence and nothingness Samuel Beckett
Hi Juto,
juto aviten wrote:
do you mean OSC could some headers in the bundles for exemple?
Not exactly headers, but you can construct hierarchical message with OSC:
/192.168.123.45:4455/elm_street/crossing_vine_street/second_house_on_the left/upstairs/third_room/top_dresser_drawer/<some variable>
or something like that.
or multiple messages could be send in the same bundles? ...
Yes.
otherwise from what Kevin wrote a difference could that OSC could be used in different softwre to communicate with each others and netsend/receive is only for PD... right?
Correct. Check more here:
http://opensoundcontrol.org/cnmat
best, d.
do you mean OSC could some headers in the bundles for exemple?
exactly ... osc adds information and can transport various different data types (see http://opensoundcontrol.org/spec-1_0 for details)
or multiple messages could be send in the same bundles? ...
exactly ... if you need tight triggering of messages, this is crucial ...
otherwise from what Kevin wrote a difference could that OSC could be used in different softwre to communicate with each others and netsend/receive is only for PD... right?
you can use netsend/receives with every other software, that can open a network socket (like netcat) ... osc is far more powerful, though ...
cheers ... tim
-- tim@klingt.org ICQ: 96771783 http://www.mokabar.tk
The price an artist pays for doing what he wants is that he has to do it. William S. Burroughs
juto aviten wrote:
Hi pders, just a simple question :
what's the real difference for you between netsend/netreceive/netserver & OSC objects?
The netsend group pass pd messages terminated with a semicolon, while the OSC group use the Open Sound Control protocol (http://www.cnmat.berkeley.edu/OpenSoundControl/OSC-spec.html) to pass floats, integers or strings, with a path-like address.
I don't see real difference between both of it in term of transmitting a tcp/udp message through network...
The OSC objects only use UDP, butI made an alternate set (at http://pure-data.cvs.sourceforge.net/pure-data/externals/mrpeach/net and http://pure-data.cvs.sourceforge.net/pure-data/externals/mrpeach/osc) that let you use either UDP or TCP. Also my net objects take lists of bytes (really floats because pd doesn't have bytes) so any kind of message can be sent/received. Netsend is the easiest to use if you want to communicate between pd and pd, or max. Most audio synthesis applications (csound, supercollider, etc.) can only handle OSC over UDP.
Martin
-
Derek Holzer -
juto aviten -
Kevin McCoy -
Martin Peach -
Tim Blechmann