While designing my last show I noticed the Go key on my TouchOSC layouts wasn't working. I assumed there must have been a change in the OSC to key mappings, but the listing at the rear of the manuals hasn't changed.
I've confirmed the nomad software is receiving the correct OSC command, and neither /eos/key/go nor /eos/key/go_0 works. /eos/key/stop or /eos/key/stopback both work correctly (with equivalent function), as do all other keys and inputs tested.
I've since had a couple of other users of my layouts (available on ETCLabs/OSCLayouts) complain of the same issue. Is the cause known/being addressed?
I just noticed that when changing parameters between go and go_0, TouchOSC actually had a different layout selected to the one I was changing. In actual fact, go_0 does work (and go doesn't). Thanks for…
I found a bug for this that appears to have been resolved in v2.6.0, but no current reports previous to yours. We will take a look.Just to confirm, you can hit go on the console itself and it works? Are the console and the OSCLayout the same user number?
I’ve only tested on nomad, not consoles (don’t have access to one). Pressing the go playback button in the drop-down face panel works correctly, and I’ve double checked that cuelist 1 is loaded normally onto the fader pair and the fader button config is normal.
the OSC must be the same user as I understand it as the command line is shared.
Thank you. This helps. I will get this tested and let you know if we can duplicate the issue and if we find a workaround for you.
Hi Sophie:I was able to hit go just fine using the layout found here: https://github.com/ETCLabs/OSCLayouts/blob/master/Eos_TouchOSC.touchosc and have it fire a cue list on my Element v2.9.0 without issue. Would you be able to send a screenshot of the Diagnostics window with Log Incoming OSC turned on after hitting GO on your app?
Here is the diagnostics window showing receipt of the go command (which didn't work) and stop/back (which did)
Thank you, Sophie! Any chance that you can share your OSC layout so I can test with that as well, since we are having trouble reproducing the issue? You can direct message it to me or email to sasha (at)etcconnect.com
I just noticed that when changing parameters between go and go_0, TouchOSC actually had a different layout selected to the one I was changing. In actual fact, go_0 does work (and go doesn't). Thanks for your help.