| From | Sent On | Attachments |
|---|---|---|
| Miller Puckette | Feb 4, 2009 7:32 pm | |
| mbutubuntu | Feb 5, 2009 5:00 am | |
| Roman Haefeli | Feb 5, 2009 5:15 am | |
| mbutubuntu | Feb 5, 2009 6:18 am | |
| Jack | Feb 5, 2009 6:57 am | |
| mbutubuntu | Feb 5, 2009 7:11 am | |
| Jack | Feb 5, 2009 7:18 am | |
| mbutubuntu | Feb 5, 2009 7:23 am | |
| Jack | Feb 5, 2009 7:32 am | |
| IOhannes m zmoelnig | Feb 5, 2009 7:33 am | |
| mbutubuntu | Feb 5, 2009 7:41 am | |
| Roman Haefeli | Feb 5, 2009 8:34 am | |
| Jack | Feb 5, 2009 9:12 am | |
| Roman Haefeli | Feb 5, 2009 10:19 am |
| Subject: | Re: [PD] Very Strange Behaviour of dumpOSC on Pd | |
|---|---|---|
| From: | Roman Haefeli (redu...@yahoo.de) | |
| Date: | Feb 5, 2009 10:19:43 am | |
| List: | at.iem.pd-list | |
On Thu, 2009-02-05 at 18:12 +0100, Jack wrote:
Thanx Roman for the clarification. I thought that [tcpsend]/ [tcpreceive] worked with OSC. I think it must be specify somewhere in the help patch (with [packOSC]/[unpackOSC] or/and [tcpsend]/[tcpreceive] ?). I just download abstractions from : http://romanhaefeli.net/software/pd/OSCstream.tar.gz
this archive only contains [packOSCstream] and [unpackOSCstream], the other abstractions are missing. however, everything is in svn (externals/mrpeach), so please use those, since mrpeach accepted to include them and those are going to be kept up-to-date by me.
roman
Le 5 févr. 09 à 17:35, Roman Haefeli a écrit :
--- Jack <ja...@rybn.org> schrieb am Do, 5.2.2009:
Yep, as Roman says try [udpreceive] with [unpackOSC] (OSC comme often 'on' UDP) or [tcpreceive] with [unpackOSC], if you want a service with connection. The choice depends if you absolutely need to receive your data. AFAIK, OSCx accepts only UDP protocol.
you cannot use [tcpsend]/[tcpreceive] use together with [packOSC]/ [unpackOSC], since there is a special OSC specification for stream oriented transport layers such as TCP. OSC assumes that either the transport layer takes care of the corrent handling of packets (which is the case for udp) and specifies a special header for OSC packets, when it is transported over a stream oriented protocol (TCP).
this makes the use of OSC over TCP much more complex. i made some abstractions for mrpeach to handle this correctly. here a little description about using them as intended:
OSC OVER TCP
- for unidirectional TCP connections, use:
[packOSCstream] and [tcpsend] for the sender side and
[tcpreceive] and [unpackOSCstream] on the receiver side
- for bidirectional TCP connections, use:
-on the server side: [tcpsocketserver OSC <port>] with [unpackOSC] for receiving and [packOSCstream] for sending
-on the client side: [tcpclient] with [unpackOSCstream] for receiving and [packOSCstream] for sending
(for the sake of completeness:)
OSC OVER UDP
- for sending: [packOSC] with [udpsend]
- for receiving: [unpackOSC] with [udpreceive]
i know, this sounds all complicated. actually i made those abstractions to get at least raw functionality, so that transporting OSC over TCP is possible at all. in order to make things less confusing and more obvious, i guess, i should add more high level abstractions, that contain the networking and un/packing stuff in once class.
roman
_______________________________________________
Pd-l...@iem.at mailing list
UNSUBSCRIBE and account-management ->
http://lists.puredata.info/listinfo/pd-list
___________________________________________________________ Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de
_______________________________________________
Pd-l...@iem.at mailing list
UNSUBSCRIBE and account-management ->
http://lists.puredata.info/listinfo/pd-list





