Help for Touch OSC layouts

[DNT]

I have been extending my Nomad system with various gadgets recently, and the latest one is Touch OSC control from an Android tablet. I have downloaded the TouchOSC layout from GitHub and while it works very well, I have some issues with it. I had been using it for a day before I realised there are four pages of screens. The tabs at the top are not displaying their headings or changing colour as they seem to be programmed to do. Also, the command line is not being populated as I type even though it appears to be programmed to do. I downloaded the editor and began experimenting by creating new pages and objects and uploading the new file to the tablet. Some of the changes worked but other didn't. does anyone know where I can get help with any of the above, and also, once I do get that far, how do you map the buttons to the relevant console commands.

Denis

 

[gyro_gearloose]

One step at a time! From what I understand from your post you’ve got TouchOSC to talk to Nomad, but the command line on TouchOSC doesn’t display anything? That sounds like you have an addressing problem.

 

Both Nomad and TouchOSC need to know the IP address and port number of each other. From you’ve written it sounds like TouchOSC knows the IP address/port number of Nomad, but Nomad knows nothing about TouchOSC. This is why Nomad responds to commands from TouchOSC, but TouchOSC doesn’t display the correct command line, tab headings, etc.

 

Here’s a quick guide that I wrote a few years ago when I made a TouchOSC overlay for our Element. It was originally written to help someone connect TouchOSC to the offline EOS software, but the steps should be the same for Nomad and actual consoles as well. The important bit for you is in the last paragraph, but I thought I’d post the whole thing in case anyone else has problems setting up TouchOSC/EOS.

 

First of all you'll need to enable OSC control on the EOS software. To do this, run the EOS family welcome screen and then select 'settings' then 'Network'. Network should be enabled already so we can leave that. Just scroll down the network settings until you get to 'UDP strings and OSC', and tick this option. Leave the OSC format as 1.0 and click 'Accept'.

 

Next, start the offline software and press the 'About' button. Look for the IP setting (this should read something like 192.168.1.67). Now run the TouchOSC software on your tablet. Select 'OSC" under the connections heading to set up the connection between tablet and PC. Make sure 'Enabled' is selected. The IP address from the EOS software should be entered under the 'Host' setting. Leave the outgoing and incoming ports as 8000 and 9000 respectively, and make a note of the 'Local IP address' setting.

 

Go back to the EOS software and select 'Displays' -> 'Setup' -> 'Show settings' -> 'Show control'. Make sure 'String RX' and 'String and OSC TX' are both enabled. Set the 'OSC TX IP Address' to match the 'Local IP address' setting from TouchOSC, the 'OSC TX Port Number' to match the 'Port (incoming)' setting, and the 'OSC RX Port Number' to match the 'Port (outgoing)' setting. Make a note of these particular steps as you'll need to do them for every show that you want to control via OSC. I'm not sure why ETC did not put these options in the 'Network' settings.

[DNT]

Thanks a million for taking the time to reply and for your help. It has worked. I had the ports sorted already but not the osc udp tx address. Once I did that, it worked as you suggested.

Problem number one sorted now, thanks.

 

The header tabs are still not changing colour and the text can’t be seen even though I can see them in the editor. Any further suggestions would be really welcome.

 

Then I move to the advanced level question about how to map objects to the nomad commands.

 

Denis

[DNT]

Thanks a million for taking the time to reply and for your help. It has worked. I had the ports sorted already but not the osc udp tx address. Once I did that, it worked as you suggested.

Problem number one sorted now, thanks.

 

The header tabs are still not changing colour and the text can't be seen even though I can see them in the editor. Any further suggestions would be really welcome.

 

Then I move to the advanced level question about how to map objects to the nomad commands.

 

Denis

 

 

I have made some progress on all of the issues so I thought it might help to post them here in case anyone else has similar issues.

 

The header tabs issue was resolved by just removing the text labels and creating labels within the definition of the tab itself. The tabs don't change colour as they are selected but at least they all show. I get the sense that if I began a layout from scratch and reset the screen size in pixels to match the tablet, I would have more success, but the layout file scaled well using the ipad screen size option, so I went with that.

 

In relation to the mapping, someone on the GitHub site gave me the link to the ETC page listing all OSC commands, so I have been working through those. This is the link

 

Not all of the commands are obvious. I am currently building a playback section on Touch OSC so I need a load button as well as the go and stop buttons and two faders. The syntax for the load button is /eos/key/fader/_ab

 

I am currently working to get the two master faders to work.

 

Denis

[DNT]

Update as of 1 June2020

 

 

 

Given all the extratime I have at the moment, I have continued to experiment with this issue and Iam now happy that I have resolved most of the problems. I am posting this incase anyone else has similar issues. As well as the excellent help I got hereand also on GitHub, I found that two links are very useful:

 

https://github.com/E...%20Commands.pdf

 

 

 

A document from theETC site on the topic of "Eos Integration via OSC", which I havedownloaded as a PDF, but unfortunately, I cannot find the link any more.

 

 

 

The latest version isnow available on github at

 

https://github.com/E...youts/issues/36

 

It includes a page with all of the EOS buttons laid out as perthe console, a page with encoders (yet to be completed), a page of groups andpalettes (more or less as originally set out), a page of faders (also more or lessoriginal) and a Playback page complete with master faders, grand master andload button etc.

 

There are a few things specific to the showfile which itoperates but most of it will work on any showfile.

 

I will continue to work to improve the file and may post a laterversion over time.

 

 

 

 

Denis