Hi all!

I'm having problems with a very simple patch. When trying to unpack OSC using mrpeach the console prints "gatom: no method for /whatever message I try to send". The patch looks like this:

[import mrpeach]

[udpreceive 9000]
|
[unpackOSC]
|
[number]

If I understand this right gatom is the number-box and it can't interpret the massage. If I attach a [print], the console nicely prints the parameter and a float. That's exactly what the number-box is supposed to receive, right?

To make this even more strange it has been working perfectly the last few days. Have been reading some old mailing-lists talking about symbols and such related to OSC and mrpeach which I didn't undersand. Could this have something to do with it?

Using a MacBook '09 and sending OSC from OSCulator. Have tried to redownload and reinstall PD.

Any ideas?

Thanks,
Anderas

Hi Kamikaze,

Try having a look at this: http://en.flossmanuals.net/pure-data/ch065_osc/
If you have some specific question, feel free to post it in this forum.

Take care,
Gilberto

Also, I created this little file for myself when I was studying how OSC works with pd, and it may be helpful to you: OSC-examples.pd

Good luck!
Gilberto

Also, this guy is great:

Just starting out myself and he has been VERY helpful.

/Andreas

Absolutely, his videos are among the best introduction tutorials that we have for Pd. Thanks for sharing the link for the OSC tutorial here.

ok after watching the videos a couple of dozen times, i FINALLY managed to get a patch to pretty much work except for some minor quirks

1. The disconnect doesn't work, and the only way to close the ports is to completely reboot, otherwise for some reason if i have to load the patch a second time, it tries to open the port a second time i am guessing

2; The volume sliders go directly from 1 to 100. I am guessing this is because a floating point number is generated, and the program needs a whole number between 1 and 100

Also I was wondering just for my own curiosity, if there was a more efficient way to do what i wrote

thanks in advance

-James
startrecieve2.pd
mk3test.touchosc

Hi,

I tried to add a message [disconnect( to your patch and it did work on my computer. Try this: after clicking disconnect, if you send anything to [udpsend], you should get the following error message: udpsend: not connected

Also, note that disconnect does not mean closing the port. You are simply telling [udpsend] to stop listening to that port, but you may very well have information flowing through it. In Linux, I use a program named gufw (a firewall configuration tool) to control which ports are opened. I usually leave 9001-9004 opened for Pd, but if for whatever reason I want to close them, I can do it without rebooting via gufw.

As for the slider problem, I don't use TouchOSC so I have no idea what is causing it. But try to connect a [print] after routing the messages, and see for yourself what Pd is receiving.

Take care and good luck,
Gilberto

thanks for replying. Do you know if float numbers normally have the two decimal places? I was thinking that I could change the slider value from 1 to 100 to between 0 and 1 and then multiply by 100. If that was the case, would I have to use a number box, or could i just multiply the $1 variable by 100?

thanks

-James

Hi,

To map an input between 0 and 1 into 1-100, you can use a slider ranging 0-1 and then use:

slider between 0-1
|
[+ 1]
|
[* 50]
|
result between 1-100

As for decimal places, you have to know that Pd treats every number as a float. So basically there is no distinction between 100. and 100.

Take care,
Gilberto

@AndreasA

I'm not an expert ... but I guess I can help with this one.

You need to know the message sent by your device and need to "route" it. The example follows.

[import mrpeach]

[udpreceive 9000]
|
[unpackOSC]
|
[routeOSC /msg]

where "msg" is the message sent by the OSC.

You might try this simple android app. andOSC

The messages sent from there are: acc, touch and ori

acc and ori are for the accelerometer and orientation. Both comes with three packed values so the route would be:

[routeOSC /acc] or "ori" in the case of wanting orientation
|
[unpack f f f]

touch comes with two coordinates, so the example is:

[routeOSC /touch] or "ori" in the case of wanting orientation
|
[unpack f f]

Then you get the numbers at each of the unpack outlets.

Good luck,

Gaspar