Max/msp not receiving from TouchOSC

Philippe Trovão's icon

Hi all!

I want to use TouchOSC to control my patches but I can't make it work both ways.
I can use updsend to control the app on my phone but the updreceive doesn't do anything.
I've seen that I'm not the only person with that problem...I looked, changed ips, I'm in the same network otherwise the udpsend also wouldn't work. Can anyone help? Using a MacBook Pro 13 2017, BigSur and a Nokia 4.2 android

Jean-Francois Charles's icon

Are you using two different ports, one for sending, another for receiving?
Did you try the basic example on this page?
https://hexler.net/touchosc-mk1/manual/setup-other

Philippe Trovão's icon

I did.
For some reason I can control stuff on my phone with MacBook but not the other way around...
I can use touch OSC bridge but the accelerometer only works with OSC messages...

Andy Maskell's icon

This is how I solved a similar problem using the Sadam and O.Dot libraries running Max in Windows 10. The SprintF command is also useful for formulating OSC commands from text strings with parameter wildcards to pass to UDPSend. As you can see from the screenshot, Sadam.UDPClient can be configured to send and receive on the same UDP port, a problem that faces anybody trying to interface to a Behringer product such as their X-Air mixers (XR18/X32) but you can use separate ports for most applications. The flow here is that you send using UDPSend which then passes the command internally (via the LocalHost address - 127.0.0.1) to Sadam.UDPClient. Sadam handles the communication to/from the network device using the configured IP address and UDP ports. Max then uses UDPReceive to listen to the client via another internal link to Sadam. Note that the UDP ports and IP address can all be configured separately to suit your purposes. I then use stacked o.route objects to work my way down the hierarchy of returned OSC message addresses.

Hope this helps - it was certainly plaguing me for months before I worked this out!