I’m trying to set up a very simple OSC workflow between TouchOSC (new / Mk2 version) and EOS Nomad, and I’m running into what seems to be an interface or documentation mismatch.
Context
-
EOS Nomad on macOS
-
TouchOSC new version (not the legacy TouchOSC + Editor)
-
OSC RX is enabled in EOS
-
UDP RX port is set to 8000
-
TouchOSC is correctly sending to that IP/port
-
I can confirm network communication is working
Goal (very simple use case)
This is not for show use, only for focusing from the stage.
I want a TouchOSC button to send plain EOS command-line text, for example:
-
Chan 1 Enter -
@ Full -
@ 0 -
Clear Clear
In other words, the equivalent of typing text into the EOS command line via:
/eos/cmd "Chan 1 Enter"Where it breaks
In the new TouchOSC UI:
-
I can set the OSC Address to
/eos/cmd -
However, I cannot find a reliable way to enter a free text string argument
-
The “Arguments +” menu only exposes control properties (Color, Name, Tag, etc.), not a literal string
-
The “Value” field shown in the OSC message panel is not editable
-
This makes it unclear how to send raw command-line text to EOS without scripting
Question
What is the correct and supported way in the current TouchOSC version to send a plain text OSC command to EOS?
Specifically:
-
Is there a proper way to send a string argument to
/eos/cmdwithout using Lua scripting? -
Or is scripting now the expected/recommended method for this use case?
Any clarification or example would be greatly appreciated.
Thank you very much — and thanks for continuing to make EOS such a solid platform.
www.dropbox.com/.../Capture-d-cran-le-2026-02-12-19.03.31.png
Best regards,
Pascal