Hi guys, just wondering whether you are planning to release OSC support for commands like Staging Mode, XYZ Focus Enable/Disable or fixture position in the nearby future?
Loving the new EOS, good job everyone
Luis
Hi guys, just wondering whether you are planning to release OSC support for commands like Staging Mode, XYZ Focus Enable/Disable or fixture position in the nearby future?
Loving the new EOS, good job everyone
Luis
/eos/key/staging_mode or /eos/key/Staging_mode work. Send it twice to Clear Staging Mode
/eos/xyz 1.0, 0.0, 0.0 will set the currently-selected channel to position X=1.0, Y=0.0, Z=0.0
/eos/chan/1/xyz 3.0, 2.0, 1.0 will set Chan 1 to position X=3, Y=2, Z=1
>>Note: this position is *always* in Meters, for consistency.
/eos/cmd=Chan 1 XYZ_Format Disable# or /eos/cmd="Chan 1 XYZ_Format Enable#" should change that setting. Note that it does need to be terminated, with the #.
The manual should updated for v3.1, there are also some other items (e.g. filter) which are missing.
Hi sstaub could you be more specific about items that are missing in the manual? For instance, I see Filter in the manual, but maybe I'm not thinking of the same one?
I mean the OSC cmd "/eos/filter/add", also the new commands for 'xyz' and key names for 'staging', described in this post.
The rules for parameter names and key names should better explained, like you did in another post:
- the names are not case sensitive
- you can use a space instead an underline
- use '\' (backslash) instead of '/' (slash) when using parameter names in the OSC address
- e.g. for Softkey 1 following is allowed
- "Softkey_1"
- "SOFTKEY_1"
- "SOFTKEY 1"
- "softkey_1"
- "softkey 1"
I mean the OSC cmd "/eos/filter/add", also the new commands for 'xyz' and key names for 'staging', described in this post.
The rules for parameter names and key names should better explained, like you did in another post:
- the names are not case sensitive
- you can use a space instead an underline
- use '\' (backslash) instead of '/' (slash) when using parameter names in the OSC address
- e.g. for Softkey 1 following is allowed
- "Softkey_1"
- "SOFTKEY_1"
- "SOFTKEY 1"
- "softkey_1"
- "softkey 1"
Ah, I understand now. Thank you for clarifying, and I see this is a request you've made in the past too.
For the time-being, the most-up-to-date reference is a combination of the v3.0 manual (online here: Open Sound Control (OSC) ) and the GitHub page here: ETCLabs/EosSyncLib: UNOFFICIAL - C++ library for accessing Eos show data in real time "Supported OSC Commands"
We agree there needs to be comprehensive documentation around using OSC in Eos. In the meantime, you are always welcome to post in this forum looking for up-to-date information.
www.etcconnect.com