OSC parsing data problem in pd

Reply to OSC parsing data problem in pd on Sat, 14 Dec 2013 19:37:35 GMT

Architek1 — Sat, 14 Dec 2013 19:37:35 GMT

As with most things that you learn the curve in the beginning is a little overwhelming and the simplest things can be missed. After much ado (2 days of internet searches) I must humbly ask for assistance. I am building a processing sketch that uses position to determine frequencies to send to pd. These are passed along as the (float freq) variable in the function. Everything is good going leaving processing and into pd but I can't seem to parse the pdOscMessage correctly once it gets to pd. What am I missing?

NetAddress puredata;

oscP5 = new OscP5(this, 9000);
puredata = new NetAddress("127.0.0.1",9000);

Processing Osc Function

void pdMessage(float freq) {

//Osc Bundle creation
OscBundle myBundle = new OscBundle();

//New OSC Message creation
OscMessage pdOscMessage = new OscMessage("/ " + freq);

//Filter freq and Add an integer (midi) to the message to Pure Data NetAddress

if (freq == 417) {
oscP5.send(pdOscMessage.add(freq), puredata);

}
if (freq == 528) {
oscP5.send(pdOscMessage.add(freq), puredata);

}
if (freq == 639) {
oscP5.send(pdOscMessage.add(freq), puredata);

}
if (freq == 741) {
oscP5.send(pdOscMessage.add(freq), puredata);

}

println("pdMessage: ", pdOscMessage);

//Add message to the bundle
myBundle.add(pdOscMessage);

//Clearing message
pdOscMessage.clear();
}

}

Pd Canvas

import mrpeach

[udpreceive 9000]
|
|
[upackOSC]
|
|
[routeOSC /s /f ]
\
\
[t b]
|
|
[0\
|
|
[osc~]
|
|
[*~.1]
|
|
[dac~]

Thanks.

Reply to OSC parsing data problem in pd on Sat, 14 Dec 2013 21:05:28 GMT

baptiste_c — Sat, 14 Dec 2013 21:05:28 GMT

could you put a [print] right after [unpackOSC] and tell us what you get ?

Reply to OSC parsing data problem in pd on Sat, 14 Dec 2013 21:09:43 GMT

Architek1 — Sat, 14 Dec 2013 21:09:43 GMT

Sure thing. It's

/ 417.0 417

or whatever float is passed in the pdOscMessage

Reply to OSC parsing data problem in pd on Mon, 16 Dec 2013 04:44:28 GMT

Architek1 — Mon, 16 Dec 2013 04:44:28 GMT

I have switched my OSC messages to come from Iannix now for sake of speed instead of building a processing sketch every time.

Pd Canvas

[import mrpeach]

Anyone with any ideas on how to parse this? I know this has got to be easier than it seems

Reply to OSC parsing data problem in pd on Mon, 16 Dec 2013 06:53:27 GMT

mod — Mon, 16 Dec 2013 06:53:27 GMT

if your output of [routeOSC /cursor ] is 12 0.293095 0.851835 0.5 -2.75861 2.75459 0, then you no longer need to use the routeOSC object, as these are all just floats.

just use [unpack f f f f f f] , which will spit out those 6 float values to 6 outlets.

..edit: and to debug this yourself in future, just put the [print] object at various sections of the chain to see what comes out.

If you get something like /cursor/6.8956778 then that is an OSC message, and will need to be parsed with routeOSC. But if you just get 'normal' symbols or floats (ie, without the /***/**** form), then you can just split them up with a normal [route] object.

..edit #2: also, this kinda worries me:

[t b]
|
|
[0\
|
|
[osc~]

you're triggering a float of zero, going into an oscillator's pitch input? you do realize that the oscillator will have a frequency of zero, yeah??? ie, no sound.