ETC Element - Page 506

494 Eos Family v2.9.0 Operations Manual
OSC Gel
Gels will be represented as strings in the following format:
<Gel Manufacturer Abbreviation><Gel Number>
Example:
“AP1150” (Apollo 1150)
“G101” (Gam 101)
“L2” (Lee 2)
“R80” (Rosco 80)
“SG1” (Rosco Super Gel 1)
“E194” (Rosco E Color 194)
“T12” (TokyoBS Poly Color 12)
Integrating Your App with Eos
There are four steps to integrating an OSCApp with Eos.
Those steps are covered in the following topics:
•
Integrating Your App with Eos: Step 1 – Request Eos Software Version (below)
•
Integrating Your App with Eos: Step 2 - Synchronize (below)
•
Integrating Your App with Eos: Step 3 – Staying in Sync (on page496)
•
Integrating Your App with Eos: Step 4 – Modifying Eos Show Data (on page498)
Integrating Your App with Eos: Step 1 – Request Eos Software
Version
Request the version number of the Eos by sending the following command: /eos/get/version.
Eos will reply with:
/eos/out/get/version = <string: X.X.X.X.X.X>
Example:
•
<string: 2.3.0.1.0.111>
Note: This is useful if future versions of Eos software change the way OSC integration
commands are handled.
Integrating Your App with Eos: Step 2 - Synchronize
Request the number of items of a specific type of data you are interested with one of the
following commands:
•
/eos/get/patch/count
•
/eos/get/cuelist/count
•
/eos/get/cue/<cue list number>/count
•
/eos/get/group/count
•
/eos/get/group/displayed/count
•
/eos/get/macro/count
•
/eos/get/sub/count
•
/eos/get/preset/count