eos/key OSC commands in multi-console session

Hi. 

I'm currently testing Bitfocus Companion connected to EOS via OSC to control Keypresses, fire macros , going to cues etc... and Ive hit a little bit of a road bump with the integration of the eos/key command.

In the documentation it says "All OSC traffic from or to an Eos multi-console session must be handled by the device acting as the session Host."
From my testing this also means that every eos/key command acts like a key is pressed on the session host. This makes the command effectively useless for navigating Tabs, opening ML Controls, Navigating encoder pages and so on, since all these eos/key commands will be executed on the Host exclusively. 

I was wondering if there's a way to get OSC keystroke commands working on a user/device basis. I'm trying to avoid recording like 300 Macros since i wanted to keep this project as non invasive to the EOS showfile as possible.

Any advice is appreciated. Thanks

Parents Reply Children
  • Thank you. This helps to some extent. 

    However, it seems like not all keys found under "OSC Eos Keys" in the "OSC Dictionary" follow this behaviour. Originally, i was trying to page encoder categories via OSC. This works fine in a single device session with "eos/key/Encoder_Category_Color", but in a multiconsole session "/eos/user/2/key/Encoder_Category_Color" (U1 is Primary and U2 is Backup) only pages encoder categories on the Primary, which is the wrong user in this Case. 

    I'm aware this can be done with an "Encoder_Category_Color" Macro and a device target, but I'm trying to get this to work with OSC only to reduce the amount of macros necessary in each showfile.

Related