Greetings team,

All I'm currently trying to do is set up PdParty on an Iphone to control Pd on another computer via Wifi, not exactly rocket science I know, but I'm willing to admit that it's beyond me right now...

I have spent the last hour or two looking through the PdParty test libraries as the documentation mentions a basic test send/recieve patch that can be used, but I can't seem to find it at all.

Can anyone attached the basic pair here so I can figure out how it works?

And because I'm continuing my ongoing understanding of networking, does OSC use specific IP address for communication like netsend/netrecieve, or is it a different beast based upon just using a port and then an associated name and value, with the name being used later to filter the value back out at the other end?

@toddak http://danomatika.com/code/pdparty/guide#osc-server-settings mentions setup of an osc server, but as you say there is no doc and it suggests that it only sends the phone sensor data..... but I am unsure.
It says it is inspired by TouchOSC, and the Hexler site had test patches. They used MrPeach (extended) objects though, and they will not work I think with PdParty.
It has not been updated...... https://hexler.net/docs/touchosc-getting-started-osc?android

It does mention [netsend] and [netreceive] further down, but you will have to use the vanilla methods and not the older MrPeach objects.
That can be a little more difficult.
Try this..... vanilla_bug_oscparse_solution.pd
It can cope with addresses that contain a float.
That is unlikely to be your problem though, but it will test the connection.
Chop the patch in half and test PdParty with the correct IP addresses.
David.

@whale-av thanks for that, will give it a test once I return to the studio.

There is actually no specific need to use PdParty, as all I actually need in this instance is a wireless controller. I assume that I'll have the same issues with TouchOSC if they use MrPeach objects too?

To be blunt, this is almost the straw that breaks the camels back... I've been struggling with issues like this and PD Vanilla for awhile, and I'm close to just giving up and trying to save for something to run Max/MSP on instead as I have less issues and faster workflow when using that (like running it on a Latte Panda for instance).

Is there any easy way to communicate wirelessly through IOS with PD Vanilla? Maybe I should look at a basic wireless / bluetooth Midi Controller instead? Very open to suggestions here before turning into a version of the Incredible Hulk....

@toddak I use TouchOSC for Android for a monitor control system I built 6 years ago.
Originally it controlled Pd Extended using MrPeach objects.
I have nearly completed an update for Vanilla. My problems left to solve are not with the comms..... TouchOSC is working fine with Pd Vanilla, and is probably still the best app for OSC and midi control.
Pd updates the TouchOSC interface too, changing fader names and colours for example.
I can certainly help you with that.

Here are some objects I built...... MrPeach Vanilla.zip..... that can directly replace (apart from [routeOSC]...... see the note inside) some of the Extended MrPeach objects. They have the same names as the MrPeach OSC objects and the contents of the zip can be tipped into the same folder as an old Extended patch to make it work in Vanilla...... apart from [routeOSC] where you will have to add a [route] after its output.

I originally used [dumpOSC] to receive from TouchOSC (it was in the old TouchOSC help file) and so that is the object that I replaced.
Obviously it needs an argument so...... [dumpOSC 8000] I think matches TouchOSC as it is download "out of the box".......... pretty sure it sends to port 8000.

This is the setup for one of my tablets....

Anyway.....
Host is the IP of the computer TouchOSC will be talking to (the one running Pd).
Port (outgoing) is the port for sending to Pd..... in this screenshot you would use [dumpOSC 8099] in Pd.
Port (incoming) is the port you would send to for updating TouchOSC.... so from Pd to 192.168.1.199 port 9000.
Local IP Address is filled automatically (it is grabbed from what you set in the ios) .... and also ZeroConf name (I think).
The zeroconf name is the broadcast name for finding devices by name rather than IP..... like DNS on the web..... but it can be ignored and it is better to fix your IP addresses inside your private network as you will not be relying on any "lookup" service that might not be running or could have a corrupted cache..
Then just make a patch like this and you will see the messages arriving in Pd terminal....

David.

Hi folks!
I reached this thread because I had the same problem: there were no way to receive OSC messages in PDparty. I was sending a simple bang from Isadora, just for test purposes, and it works fine on PD on my Mac (sending to locahost), but does not work sending to my Iphone IP. I was sure that the OSC were issued corrected, cause I can see them on Isadora OSC monitor.
Finally I found the problem was a conflict between the OSC incoming port in PDparty (Iphone) and de OSC port that the patch is lisent to (specified in a message to netreceive). If this one (in netreceive) is the same that the one in Port incoming (PDparty), you get in the console this error "error: blind: Address already in use (48), and the patch in PDparty do not receive OSC messages. I changed the OSC incoming port in PD settings, and the patch is receiving OSC messages to the port specified in [lisent] and [netreceive].
I attach my test patch (just play the sound file "cascabel" from the bang button or from OSC (send "/toggle1 1" to port 4321 to the IP where PDparty is running).
Hope it is useful for somebody. I was stuck for hours finding the reason for no receiving OSC
Regards
Daniel
TEST_PDparty.pd cascabel.wav