thomasabarnes
There's something I'd like to point out: In your instructions you write to "Put the Host you see into TouchOSC configuration." Well, on the AZCtrl Options Tab, when I press "Configure" in the "OSC" section, the AZCtrl shows near the bottom:
Host (guessing)
169.254.113.9
169.254.174.220
192.168.19.2
Thank you for giving it a try and reporting about the result. Negative result is also a result. I am working is science, many people do not know that there are more publications which "close" something (prove something is not observed) then "open" something (prove something is really exists). But programs are simpler then nature, it is almost always possible to get positive result
The list of IP addresses means you have Bonjour (169.254.x.x) and some router (192.168.x.x) in your local network. Probably you have more then one adapter configured (2 129.254. addresses). Also your router give no names to devices (so you see 192.168. and not the name). Also AZCtrl probably shows only the first 3, there can be more! To see the whole list:
* open "command line" in Windows (Win+R key combination, type "cmd" then enter, otherwise find "cmd" or "cmd32" in your programs menu)
* type "ipconfig /all"
* find all lines mentioning "IPv4-Address", or simply all lines with numbers in format X.X.X.X
If some of these addresses you have not tried yet, try them.
To make OSC work, TouchOSC should be able send packets to your PC. If you have configured ports correctly, after the first packet reach AZCtrl, you will see "1 client". And that does not happened.
1) your phone should be able to communicate with your PC. That should be over wlan (not mobile internet). You can see real IP in Settings (exact place is Android incarnation dependent), TouchOSC not always show it correctly. That IP should be similar to something in the PC list.
2) check that TouchOSC can communicated with your PC in general. You can use TouchOSC Editor for Windows, following all instructions and Google to make it work.
3) check your Windows Firewall settings. During OSC activation you had to get a question from the system to allow Sonar be a network server. May be you had that question before (with some other plug-in). In case you have forbidden Sonar to be a server, AZCtrl can not receive anything. It can be that your current network is configured as "Public" while the firewall allows to serve only in "Private" (default setting).
Finally we can organize short TeamViewer online session. The number of possible Network related problems is too long and too technical for any music related forum...
An installation video may be helpful.
There is a video:
https://www.youtube.com/watch?v=L5Gl61MvEuQ , but is shows the case when everything goes smooth.
I'm willing to test further, if you want me to.
Sure! And you can get free technical support for free program. How often that happens?
I'm waiting to receive a X-Touch and a new audio interface in a few days, so I will be doing a lot of MIDI exploring, and spending a lot of time in the SONAR forums now, and for a while to come.
I can also answer on any questions about X-Touch with Sonar. You probably will use CW MackieControl with it, not AZ Controller. But I know MackieControl source code (and a bit more...) and I have "moded" version of it (if you want control ProChannel EQ/Comp).