Syntien for Android

App crashes as soon as I set the correct IP and port for the OSC receiving application to communicate. Then when it restarts the details are reset to default. Can’t use the app if it crashes when connecting. Can’t save if it crashes when setting addresses.

I use the OSC sending/receiving constantly for controlling vastly different tasks in TouchDesigner on my workstation. Sliders for my audio processing pipeline, 2D sliders for PiP coordinates control and even more sliders for the scale control. Index selectors for the PiP channels, using the multibar sliders as a real-time volume monitor for pre and post mix levels, using the labels to show render FPS, interaction counts, etc. I do wish working with OSC on this app was a bit cleaner and more consistent. My Mobile has a bad habit of not reopening ports that were either previously used in a prior session, or relaunching from a crash. I’ll usually have to swap to new ports on both the client(Mobile) and server(TD) ends. That’s also probably just a quirk of OSC. But about the mentioned crash, if you receive an OSC message in a format it doesn’t like or you malformed some bytes, it’ll hard crash the app instantly. I’d hope for error handling there. Lastly, a pipe dream of mine, would be some form of way to have an optional response callback when receiving a message to a specific control address. Say my server sends a message to a slider to set itself to a value such as 0, it would also send a 0 back to the server from that controller’s address as if the operator themselves set the value. As it works right now, if a slider was set to 0.5 by the operator and the app received a message to set the slider to 0, it only visually adjusts the slider in the client to 0. In my Server environment the slider value will still be 0.5 from my OSC listener. Maybe even the ability to update multiple controls with a single OSC bundle would be neat. Otherwise a great product!