Working with the EOS and OSC

[tlaloc]

I wanted to offer up some user actors that I made for getting triggers from cues in the EOS platform using OSC.

The actors parse out the cue number from the OSC line that comes from the console. Separating the cue number from the 

time and from the percent complete.

OSC FROM ETC EOS---CUE INFORMATION.iua: shows the cue#, Time, Percentage done.

OSC FROM ETC Cue trigger.iua: By entering the cue # that you want to trigger a cue 

with the actor watches for that number sends a trigger when that cue happens.

Please let me know if I can help clarify any of this better.

Have fun.

Tlaloc

P.s. these files where saved in the BETA version. If you need it back saved please let me know.

0d80d2-osc-from-etc-cue-trigger.iua 9bf6a2-osc-from-etc-eos-cue-information.iua

[tlaloc]

This IUA allows you to GO on cues. Go BACK on cues and has the izzy trigger integrated. 
Let me know if you have any questions.

It was written on the BETA. Let me know if you need a different version.

Tlaloc

63cc78-etc-eos-control.iua

[glennpowell1]

saved back for Izzy 2.2 would be much appreciated. Very useful!

[tlaloc]

Here you are glen. The go commands going towards eos work on their own. For the return cue information from EOS I recommend the OSC router.

Also Please see the attached image for the stream path in IZZY.

8c7fab-eos-user-actor.izz

[glennpowell1]

I will give it a try soon as I can. Thanks again!

[DusX]

I recently posted to another thread on ETC some info about osc formatting. I suggest taking a look at it.

[tlaloc]

DusX can you link to it?

[gapworks]

@dusx

i still don't manage to trigger cues from eos  ion from  isadora. any suggestions, help, examples.

be  aware that I'm truly new to the eos family!

best

[gapworks]

@tlaloc

i downloaded  all the  actors. are there any example files, screenshots available especially from the eos side setup

best

[Juriaan]

@gapworks

Hi there!

Starting on the EOS side; go sit behind your console/machine that is running ETC EOS

1. Open the menu by pressing the triangle at the bottom of your screen (the same location as where you can save/load new files)
2. Press Setup > System Settings
3. Go to Show Control
4. Go to the Tab OSC
5. Enable OSC RX (Receiving) and OSC TX (Transmitting)
6. Set the correct ports, let's say that our Input port is going to be 4567 and our output port is going to be 1234 (Isadora Standard port, this should match your default OSC receiving port of Isadora)
7. In the OSC TX Address fill in the IP Address that you can find in the Isadora Preference menu (bottom of the Preference window)
8. All other fields should be left alone.
9. Go back into Live mode (Press Live if you are behind a Console or press Blind at the top of your screen to return to the normal mode)
10. Make sure that you can advance through your Cue list like you normally would. If not, that means that your Cue list is not attached to the Main Playback master

To Isadora;

1. Create a new OSC Transmit actor
2. Fill in the IP Address of the other machine
3. Fill in the Port, this should be the same as step 6 of the EOS side. (Input port)
4. Fill this in our OSC path; /eos/cue/2/fire
5. Add a Trigger value actor to our value, and send it 1 > press the trigger
6. Isadora will now tell EOS that it should fire cue 2.
7. EOS should follow :)

A few things about the OSC path and how it works;

/eos > required for all EOS commands, they all start with /eos/

/cue > We wish to execute a Cue command

/2 > The cue number

/fire > And we wish to fire it.

You can use a Text formatter to make this OSC path for you.

1. Grab a new Text Formatter actor
2. Double Click the actor
3. Paste this inside  "/eos/cue/" P1 "/fire"
4. Press OK
5. Now if you change Parameter 1 to 3 for example it will give an OSC path of "/eos/cue/3/fire"

[Juriaan]

@gapworks

A few gotchas;

If you wish to use your Console / Nomad during sending commands within Isadora you have to use so-called "Users".

ETC EOS has one primary user and a secondary user. What happens when Isadora is sending commands as a primary user it will clear your command bar.. And that is real shitty when you are working on some stuff during your show :) (In Blind mode ofc)

You should set all the OSC commands to User 2, Secondary user. That way your command bar is never cleared since that is our Primary user.

You can simply do this by adding /user/2/ to the command.

The above example will be /eos/user/2/cue/[cuenumber]/fire