Hi
topic title says it all; no need to post details of my problem until someone chimes in.

Brendan

Hi
I'm using an Android tablet and OSX Sierra. I'm trying to control a PD patch running on my laptop, from my MMB GUI. Instead of using the PDwrapper, I've built my own little OSC coms patch (which shares the name of my .mmb file) and put them both on the tablet. As I understand it the GUI sends on port 54300 (and receives on 54310), the PD patch (which handles the OSC parsing) sends on 54322 and receives on 54321. These settings are reflected in the MMB/Network settings. I'm afraid that I'm a little in the dark as to 'how' MMB GUI and associated PD patches communicate, and no matter which port numbers I use and change I cannot get the MMB GUI to communicate with my PC PD patch.
It would be helpful if you could describe your setup for me. Here's a very short 1 minute demo of myset up (running fine on my PC.

@brendanmac In the patch on the tablet you are connecting [netsend] to localhost 12345
That is fine when running the emulator on the same PC as Pd, but when it is running on the Android "localhost" is translated as the IP of the "host"....... so you are connecting to the Android.

You need [connect "IP address of the PC" 12345(
Something like [connect 192.168.1.23 12345( ....... although the Android might also be able to resolve [connect "NameOfPC" 12345( which will be useful if you are joining other networks and using dhcp.
David.

Yes, I have explicitly used unicast to my PC's IP address, no success. I modified the patch (for MMB) to use the 'default' ports, still no joy. I'm really struggling with this. It should be possible to use MMB on tablet --> PD on PC? Right?

Basically, my pd patch on the Android is using port 54300 (from MMB GUI), translating from then back to OSC, and out to 54322. The patch on my PC is set to listen on 54322. Nothing. Connected [print] to [netreceive] and nothing is happening.

The biggest frustration is that the networking example GUI works fine, sending values to my PC (if I look for /valueToNetwork).

Any and all solutions very much welcomed.

I have saved and renamed the Networking example .mmp and .pd files, gonna check they still work, then adapt them to suit my needs (multiple sliders, toggles and buttons). I'll report back as and when etc.

TL;DR: Use PdWrapper.pd. It exists for a reason.

If you don't use PdWrapper, a patch that works on your computer is not going to work (neither GUI message sending nor networking) on your mobile device. MobMuPlat 1) does not use network messages to communicate between the UI and the patch (they are the same app, so there's no need), and 2) handles networking at the app layer, not in pd objects. The point of PdWrapper is to simulate that interaction for you, so that the patch on your computer works on mobile.

So in both cases, your mobile patch should not have any netreceive/netsend objects. Look at the example patches. The networking example patch, has the simplest example that covers both these issues. It receives GUI interaction via [fromGUI] and it sends/receives network data via [receive fromNetwork] and [send toNetwork]. Go to the MobMuPlat networking options to specify the IP address and port numbers.

Thanks for the contributions everyone, I think I now have a much clearer understanding of what's going on with MMP and OSC. Like I said, I'll put something together and post it here as a 'solution'.

Brendan

search: YT "casim mobmuplat"
This is a summary description of our solution. Full disclosure, this is not for anyone running MMP as a tablet standalone, it's a specific use case scenario, i.e. MMP on tablet, PD synthesis engine on PC, communication via networked OSC. HTH