I have followed all the steps you described. Message display the right connection in green. But it doesn't work.
I use the last version of TouchOSC for iPhone (1.9.1), The last version of LXConsole (3.2.0), The last version of Mountain Lion (10.8.5) and the last iOS (7). I was on iOs 6 before with the same (bad) result. I have a MacBook Pro 15" 2012 and had the exact same problem with a MacBook Pro 2008.
TouchOSC LXConsoleRemote not working
I'm not sure how those 10.n.n.n IP addresses are being assigned in your setup. However, I manually assigned them both using a computer-to-computer wifi connection and with a wireless router on my MacBook Pro and iPhone. After having configured from the computer-to-computer network and then switching the network settings on both devices to manual IP addresses using the router, I did need to turn off OSC in LXConsole and turn it back on. When I do so, "LX_OSC" disappears in TouchOSC's found hosts and then reappears when I switched OSC back on. I tapped "Touch_OSC" and although TouchOSC's displayed network settings did not change, I was then able to send messages to LXConsole. That's a lot of configuring network settings for not much new information because TouchOSC to LXConsole works pretty consistently for me.
Have you tried sending an OSC message to LXConsole from QLab?
Have you tried connecting the iPhone/iPad Mini using a computer-to-computer wifi network rather than going through the AirPort?
Have you tried sending an OSC message to LXConsole from QLab?
Have you tried connecting the iPhone/iPad Mini using a computer-to-computer wifi network rather than going through the AirPort?
OSC
@ spadrille
I did Claudes set up and it worked here. I create my own network with a airport with NO Internet connection. I get the IP from Qlabs OSC settings screen and make sure that is selected in LX Consoles OSC preferences.
I would be glad to Skype with you and if I can see your screen, it would really help.
I did Claudes set up and it worked here. I create my own network with a airport with NO Internet connection. I get the IP from Qlabs OSC settings screen and make sure that is selected in LX Consoles OSC preferences.
I would be glad to Skype with you and if I can see your screen, it would really help.
Mark Nizer
mark@nizer.com
mark@nizer.com
I tried to connect QLab to LXConsole thru OSC and it works. Of course it doesn't use the wifi network but it works.
I'm not sure what you meant by a computer to computer wifi network". Is that an ad hoc network? Anyway, if that's what it is, it tried it with no more luck.
I should add that i use TouchOSC on iPhone to communicate with Luminair on iPad with the same airport Express and it works very consistently. So Airport express or TouchOSC doesn't seem to be the problem.
I have the feeling that i forget something really simple and that the problem is the writing communication. So, i've made a video which show you exactly what i do. Perhaps it will help you to understand what i do wrong or be sure that i do nothing wrong but that something wrong is happening.
Here it is :
http://www.youtube.com/watch?v=jUEoUn-M ... e=youtu.be
If that doesn't help, Nizer, i will be more than happy to accept you Skype proposition.
I'm not sure what you meant by a computer to computer wifi network". Is that an ad hoc network? Anyway, if that's what it is, it tried it with no more luck.
I should add that i use TouchOSC on iPhone to communicate with Luminair on iPad with the same airport Express and it works very consistently. So Airport express or TouchOSC doesn't seem to be the problem.
I have the feeling that i forget something really simple and that the problem is the writing communication. So, i've made a video which show you exactly what i do. Perhaps it will help you to understand what i do wrong or be sure that i do nothing wrong but that something wrong is happening.
Here it is :
http://www.youtube.com/watch?v=jUEoUn-M ... e=youtu.be
If that doesn't help, Nizer, i will be more than happy to accept you Skype proposition.
Everything in the video looks normal and should work. I'm suspicious of the 10.n.n.n IP addresses and the fact that there is an active ethernet and ArtNet connection as well as the WiFi. Am I correct that the 10.n.n.n IP addresses have been manually assigned, not provided by DHCP from the airport? If so, the simple thing may be that there is a duplicate IP address in one of the interfaces. There's nothing to enforce this if you are manually assigning static IPs. You'd need a separate IP address for ethernet, Art-Net, wireless and for the iPad Mini and these should not be duplicated anywhere on the AirPort network. You might try the Mac and the iPad WiFi settings as DHCP and see if that makes a difference. Also, you might want to disconnect the ethernet and Art-Net to see if that makes a difference. When I get a chance I'll try to duplicate the setup with Art-Net and static 10.n.n.n addresses on a Mac and an iPad and see if I can find a problem.
The fact that bonjour shows "LX_OSC" is not necessarily an indication of a clear network path between the two devices. For instance, I can deliberately set the Mac firewall to block connections to LXConsole. But, the bonjour advertisement of a connection still appears. So, I would check the Firewall on the Mac to be sure that perhaps QLab is allowed while LXConsole is not. If you have answered "Deny" at some point when asked if you want to allow LXConsole to receive incoming connections, it will be blocked in the firewall.
The fact that bonjour shows "LX_OSC" is not necessarily an indication of a clear network path between the two devices. For instance, I can deliberately set the Mac firewall to block connections to LXConsole. But, the bonjour advertisement of a connection still appears. So, I would check the Firewall on the Mac to be sure that perhaps QLab is allowed while LXConsole is not. If you have answered "Deny" at some point when asked if you want to allow LXConsole to receive incoming connections, it will be blocked in the firewall.
That's a good thing for my ego that i'm at least not doing it completely wrong. 
I had already tried to deactivate ethernet and Art net and that doesn't help. Also my firewall is off so that's not the issue. And about the 10.n.n.n addresses, i'm sorry but yes they are assigned by HDCP from the airport and they are not the same on the Mac and on the iPad.
I'm sorry that i don't give you more cheerful news.
I had already tried to deactivate ethernet and Art net and that doesn't help. Also my firewall is off so that's not the issue. And about the 10.n.n.n addresses, i'm sorry but yes they are assigned by HDCP from the airport and they are not the same on the Mac and on the iPad. I'm sorry that i don't give you more cheerful news.
I'm just about out of suggestions. There's a new latest build version 3.2.2 that has some OSC and network enhancements. There's a slight chance that that may make a difference or report an error that will help track down your issue.
With TouchOSC 1.9.2 there are still times where I tap "LX_OSC" and go back and have no connection. Then, I go through the process, open the settings, tap "LX_OSC" and the connection is established. I noticed that TouchOSC did not update the local IP address the last time this happened. When I opened the settings again, the local IP address updated and the connection then worked. Perhaps I'm impatient and if I just waited, TouchOSC would have updated the network on its own. So, I can't really tell if re-doing the settings process made a difference or not. However, I did verify with Wireshark that TouchOSC was not sending packets when the lack of connection happened. So that particular issue is not on the Mac end.
With TouchOSC 1.9.2 there are still times where I tap "LX_OSC" and go back and have no connection. Then, I go through the process, open the settings, tap "LX_OSC" and the connection is established. I noticed that TouchOSC did not update the local IP address the last time this happened. When I opened the settings again, the local IP address updated and the connection then worked. Perhaps I'm impatient and if I just waited, TouchOSC would have updated the network on its own. So, I can't really tell if re-doing the settings process made a difference or not. However, I did verify with Wireshark that TouchOSC was not sending packets when the lack of connection happened. So that particular issue is not on the Mac end.
The latest build is the first of the links listed as "Other Downloads" on the download page.
I did a lot of work in the theatre yesterday and used my iPhone with TouchOSC as a remote to LXConsole a lot. It seems when I put the phone in my pocket and tried to use the remote, I would have to go through the sequence of settings->OSC-> tap "LX_OSC" go back and forth until the local address changed from 127.0.0.1 to 169.x.x.x. Once I did that, I could send to LXConsole. (And receive command line feedback as well.) LXConsole sat at the back of the room all day and I didn't hardly touch it except to patch a few channels. But it there was a delay every time I tried to connect with TouchOSC. It always worked eventually. And, with this new version of TouchOSC, I did not need to randomly try until it worked. I could see the local IP setting change and knew it would be connected after that.
Update:
This slow to connect behavior was on a computer to computer network. Testing on my home wireless network, the connection between LXConsole and my phone stays alive, even when the phone has been off for a few minutes. So, the delay may not be due to TouchOSC but to some other underlying networking issue.
I did a lot of work in the theatre yesterday and used my iPhone with TouchOSC as a remote to LXConsole a lot. It seems when I put the phone in my pocket and tried to use the remote, I would have to go through the sequence of settings->OSC-> tap "LX_OSC" go back and forth until the local address changed from 127.0.0.1 to 169.x.x.x. Once I did that, I could send to LXConsole. (And receive command line feedback as well.) LXConsole sat at the back of the room all day and I didn't hardly touch it except to patch a few channels. But it there was a delay every time I tried to connect with TouchOSC. It always worked eventually. And, with this new version of TouchOSC, I did not need to randomly try until it worked. I could see the local IP setting change and knew it would be connected after that.
Update:
This slow to connect behavior was on a computer to computer network. Testing on my home wireless network, the connection between LXConsole and my phone stays alive, even when the phone has been off for a few minutes. So, the delay may not be due to TouchOSC but to some other underlying networking issue.
It seems like there is some routing issue on your Airport network and given that it takes some tries to get TouchOSC to connect on a computer to computer network, it may be that the test of that was not conclusive. I would simplify the problem as much as possible to try to track it down.
I would start by disconnecting the ethernet from the computer so that the only active network connection is the WiFi. Then, I would create a device to device network. On the Mac if you look in the Network system preferences, you will see that this connection probably does not have an IP address right away.
Next, use the settings app on the iPad/iPhone to connect to your computer's network. You may have to close the WiFi settings and reopen them before you will be able to see the IP address of the device. It should be of the form 169.n.n.n with a subnet mask of 255.255.0.0.
Next, open LXConsole and look in its OSC preferences. You should be able to select a network connection with a 169.n.n.n address. If not, refresh the list. Once you have selected the 169.n.n.n connection, use the toolbar button or File-External to enable OSC In.
Back to the device, open TouchOSC. Tap settings. Tap the OSC settings. On the latest 1.9.2 version of TouchOSC, you can see when the local network settings change. Which seems to be an indication that a connection has been established. You should see "LX_OSC", tap that. And, you should see the 169.n.n.n IP address of the computer appear. You should also see the 169.n.n.n address of the device listed as the local IP address. (For me, the connection won't work if the local IP address is 127.0.0.1 or whatever the previous address was.)
Once you see both in and out addresses are correct in TouchOSC's settings, test the OSC connection to LXConsole. That's about as simple as it gets. With only a single network connection, which you know has been established by seeing DHCP addresses at each end and with the Mac firewall turned off, there's no reason that I can tell why the TouchOSC/LXConsole connection wouldn't work. There is a delay in establishing the DHCP addresses when you connect the device to the Mac and it is possible that in the previous test, that was the problem with the connection not working.
It appears to me after experimenting that the delay in re-establishing an OSC connection is not TouchOSC but rather the device waiting for DHCP after it wakes up. This appears to happen even when the DHCP address returned remains the same as the last time the device was awake. Instead of waiting and messing around with TouchOSC's settings, I waited until I saw the DHCP return an IP address in the System Settings app and then switched to TouchOSC and could use it right away. Further, I statically assigned the device the same 169.n.n.n IP address as was assigned by DHCP. After that I am able to simply open TouchOSC's settings and close them and the connection re-establishes after the phone has been asleep. This is MUCH faster than waiting for the DHCP to kick in each time you want to turn on and off a light.
I would start by disconnecting the ethernet from the computer so that the only active network connection is the WiFi. Then, I would create a device to device network. On the Mac if you look in the Network system preferences, you will see that this connection probably does not have an IP address right away.
Next, use the settings app on the iPad/iPhone to connect to your computer's network. You may have to close the WiFi settings and reopen them before you will be able to see the IP address of the device. It should be of the form 169.n.n.n with a subnet mask of 255.255.0.0.
Next, open LXConsole and look in its OSC preferences. You should be able to select a network connection with a 169.n.n.n address. If not, refresh the list. Once you have selected the 169.n.n.n connection, use the toolbar button or File-External to enable OSC In.
Back to the device, open TouchOSC. Tap settings. Tap the OSC settings. On the latest 1.9.2 version of TouchOSC, you can see when the local network settings change. Which seems to be an indication that a connection has been established. You should see "LX_OSC", tap that. And, you should see the 169.n.n.n IP address of the computer appear. You should also see the 169.n.n.n address of the device listed as the local IP address. (For me, the connection won't work if the local IP address is 127.0.0.1 or whatever the previous address was.)
Once you see both in and out addresses are correct in TouchOSC's settings, test the OSC connection to LXConsole. That's about as simple as it gets. With only a single network connection, which you know has been established by seeing DHCP addresses at each end and with the Mac firewall turned off, there's no reason that I can tell why the TouchOSC/LXConsole connection wouldn't work. There is a delay in establishing the DHCP addresses when you connect the device to the Mac and it is possible that in the previous test, that was the problem with the connection not working.
It appears to me after experimenting that the delay in re-establishing an OSC connection is not TouchOSC but rather the device waiting for DHCP after it wakes up. This appears to happen even when the DHCP address returned remains the same as the last time the device was awake. Instead of waiting and messing around with TouchOSC's settings, I waited until I saw the DHCP return an IP address in the System Settings app and then switched to TouchOSC and could use it right away. Further, I statically assigned the device the same 169.n.n.n IP address as was assigned by DHCP. After that I am able to simply open TouchOSC's settings and close them and the connection re-establishes after the phone has been asleep. This is MUCH faster than waiting for the DHCP to kick in each time you want to turn on and off a light.
One more important thing. In carefully going back over your video (for about the 6th time) it appears that you have LXConsole listening on port 53000. This is the same port as QLab. Have you tried a different port, say 53010 or 52000?
In a quick test, having QLab and LXConsole open at the same time, LXConsole blocks QLab from receiving OSC when they are both set to port 53000. But, that does not mean that the reverse might happen on your system. If the kernel has a choice of locations to route a packet, it may not be predictable which it will pick.
In a quick test, having QLab and LXConsole open at the same time, LXConsole blocks QLab from receiving OSC when they are both set to port 53000. But, that does not mean that the reverse might happen on your system. If the kernel has a choice of locations to route a packet, it may not be predictable which it will pick.