B. Bogart wrote:

Hey all,

Has anyone took a crack of making OSCx settable via message? Any quick experiment is fine for now.

What do you mean?

I'm working on splitting the OSC from the transport right now. I now have a udpsend, udpreceive, tcpsend and tcpreceive objects that use lists of bytes (in pd they are floats on [0..255]) instead of pd messages. I also did the packOSC object that constructs an OSC packet from a pd list, but it's still tied up with LIBOSC. The unpackOSC is still not started...

Martin

otherwise I'll have to drop OSC for my multi-screen syncing.

Thanks, .b.

---

PD-dev mailing list PD-dev@iem.at http://lists.puredata.info/listinfo/pd-dev

#N canvas 533 40 444 550 12; #X obj 171 184 udpsend; #X msg 177 158 disconnect; #X msg 171 96 connect 127.0.0.1 9997; #X obj 54 494 print; #X obj 71 96 packOSC; #X msg 71 65 send /test/ 1 2 3; #X obj 71 128 prepend send; #X obj 54 470 udpreceive 9997; #X obj 169 494 unpack 0 0 0 0; #X floatatom 169 517 3 0 0 0 - - -; #X floatatom 204 517 3 0 0 0 - - -; #X floatatom 240 517 3 0 0 0 - - -; #X floatatom 276 517 3 0 0 0 - - -; #X text 126 516 from; #X text 6 431 right output is sender's ip address as list of floats ; #X obj 171 207 tgl 15 0 empty empty empty 0 -6 0 8 -262144 -1 -1 1 1; #X text 25 259 (i.e. bytes).; #X text 4 312 The output is 1 when connected , else 0; #X text 4 226 udpsend takes three messages: 1> send followed by one or more floats on [0..255]; #X text 4 274 2> connect followed by an ip address and a port number ; #X text 4 293 3> disconnect; #X text 6 395 udpreceive takes a port number as argument; #X text 6 413 left output is received udp packet as list of floats ; #X connect 0 0 15 0; #X connect 1 0 0 0; #X connect 2 0 0 0; #X connect 4 0 6 0; #X connect 5 0 4 0; #X connect 6 0 0 0; #X connect 7 0 3 0; #X connect 7 1 8 0; #X connect 8 0 9 0; #X connect 8 1 10 0; #X connect 8 2 11 0; #X connect 8 3 12 0;