hi,
i was trying out my rather old osc client object for mxj with pd's pdj. which wasn't working, and hence led to a new polished version that works fine in pdj:
http://github.com/Sciss/PDOSCClient
there is a compiled binary also in the downloads section. please see the README.textile for installation infos.
why? in order to have bidirectional OSC communication from one object, that is sending and receiving is done from the same socket (port). this is required for instance to talk to SuperCollider as there is no way to receive client notifications with disparate [sendOSC] and [dumpOSC] objects.
have fun! best, -sciss-
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 09/04/2010 04:51 PM, Sciss wrote:
hi,
i was trying out my rather old osc client object for mxj with pd's pdj. which wasn't working, and hence led to a new polished version that works fine in pdj:
http://github.com/Sciss/PDOSCClient
there is a compiled binary also in the downloads section. please see the README.textile for installation infos.
why? in order to have bidirectional OSC communication from one object, that is sending and receiving is done from the same socket (port). this is required for instance to talk to SuperCollider as there is no way to receive client notifications with disparate [sendOSC] and [dumpOSC] objects.
hi sciss.
please note that [sendOSC] and [dumpOSC] are outdated, unmaintained and broken objects which i do net get tired of pointing out that they are deprecated. PLEASE DO NOT USE THEM.
the suggested method is to use mrpeach's osc-objects ([packOSC] and [unpackOSC] in conjunctions with one of the available transport objects, like [udpsend] or [udpreceive]. if you need bidirectional communication, you could try [udpclient] and [udpserver] (both in iemnet); the latter is still quite experimental.
fgmadsr IOhannes
have fun! best, -sciss-
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list