Locking a Console via OSC ?

Hi James,
you can lock the console with OSC.

The trick is to send a shift keypress 1 than the esc keypress 1 when the button
is down, when the button is up you send first shift keypress 0 and then escape keypress 0.
-> SHIFT 1, ESCAPE 1, SHIFT 0, ESCAPE 0
The OSC sequence SHIFT 1, ESCAPE 1, ESCAPE 0, SHIFT 0 doesn't work.

It is a litte bit different, e.g. you have a button to fire a MACRO and another button for LOCK
- MACRO and LOCK have the same user -> when locked the macro button don't work.
- MACRO user 0, LOCK user 1 -> it works as expected, the MACRO can done in background.
- MACRO user 1, LOCK user 0 -> when MACRO is pressed, the macro overrides the lock state,
  you have to press the LOCK button twice the get the console locked again.

Hi James,
try with grouping like you mentioned.

Did you ever tried https://github.com/ETCLabs/OSCWidgets or https://www.luminosus.org ?
Maybe this works for you.

Yes I'd had a look at both. I'd thought of Luminosus as more of an intermediate application between say a MIDI controller and Eos.

And I couldn't see any obvious way of scripting ETC's OSC Widgets or providing input from another source.

(Both excellent applications / tools by the way, just couldn't immediately think of a way to apply them to my problem.)

Specifically, I was thinking if I had a spreadsheet with cue notes, or a patch spreadsheet with fixture data I wanted to merge into text fields, it would be great to have an application that did something along the lines of:

Get data from open excel / numbers front most sheet, A2.
Query does Eos Patch have a channel matching that ?
If yes, write data from B2 in Eos field Text 1.
Write Data from C2 in Eos field Text 2.
etc etc

Repeat for A3, A4, A5, A6 etc 
Stop when you reach an empty cell.

Similar tools for labelling colour palettes, cues, scenes, macros, etc etc.

Similarly you could use an excel sheet to list a series of Eos osc strings, and then have this application submit them in order.

Moving Light Assistant can do much of what you describe. I wouldn't call it a simple program, however... it's a pretty significant investment. In the past, I've used MLA as an interface when I've wanted to send a series of OSC commands to Eos based on CSV data, but I've had to write the scripts to do that myself—this isn't built-in functionality.  MLA scripting is all written in Lua, which is simple enough to figure out if you aren't familiar, and MLA has a basic framework for sending OSC commands. MLA is already aware of cue and patch data so you wouldn't need to import a special CSV for those. Other record targets would be a little more complicated to read/write, but not impossible.  

Found it: /eos/out/event/locked
this is missing in the manual Page 261 "Miscellaneous Console Events"
can you add a get method? /eos/get/event/locked

Found a small bug with /eos/out/event/locked
when the console is locked by user 1, and send a macro via OSC with user 0,
there is an implicit output /eos/out/event/locked, 0(i)
this is wrong because the console stays locked