forcing a manual ip:port combination for OSC out connection

freadZdead · Post by **freadZdead** » Thu Oct 31, 2013 1:55 am

Hi Claude,

Since recently my iPad has died and is being exchanged at the moment, I thought I'd try the android version of TouchOSC. This brought me to what I believe might be an error (or just my own misunderstanding?) in the way that the OSC out settings work.

To set the scene:

I have the current version of TouchOSC running on my android. Other OSC interaction from and to the custom layout (i.e. with Quartz Composer and OSCulator) work as always. I am able to control LXConsole (though bonjour does not work, which is why I work with the manual ip address).

Here is where it seems to fall down - selecting "TouchOSC" as the service does not work (it resolves it to the dreadful 0.0.0.0 port 0 address in the messages window). I am not overly surprised, as the whole bonjour stuff does not seem to work properly in this android version of TouchOSC. No big deal, seeing that it is easy to find out the android's local ip address and use it with the other 2 softwares mentioned above.

However, and this is where it just might be a syntax error:

If I manually enter that IP address into the OSC out configuration of LXConsole ("192.168.1.107:9009"), and of course disable and re-enable the OSC Out under File>External, then it once again connects to the dreaded 0.0.0.0 port 0... and does not work. I have checked that no firewall is interfering. What could be the cause of this issue (all the wonderful benefits of the bonjour services you have added aside)?

Post by **admin** » Thu Oct 31, 2013 1:40 pm

This is fixed in the latest build 3.2.7 (6531A). Probably something got messed up with all the bonjour tweaks recently.

freadZdead · Post by **freadZdead** » Thu Oct 31, 2013 10:59 pm

cool, while it still _shows_ "connected to 0.0.0.0 port 0", at least it does work

! Thanks!

Post by **admin** » Fri Nov 01, 2013 2:23 am

The connected to 0.0.0.0 message is not really accurate anymore because the output socket is not actually bound to an address:port. Outgoing packets are sent either to the address discovered through Bonjour or to a manually specified address and port. The kernel seems to be doing a good job of routing these packets out the appropriate connection. The message will be changed to something like "OSC Socket Created".