Bug report v3.1.3 : OSC command "encoder_category_custom" seems not to work

I have reproduced this bug.  I think it stems from the change in v3.1.0 to replace the Custom key with a Focus key so that Custom could be repurposed for Custom Encoder mapping.  Our documentation didn't keep up with those changes, unfortunately.

In v2.9.x and 3.0.x, /eos/key/encoder_category_custom would put the console into the Focus category anyway, so I would replace that command with /eos/key/encoder_category_focus (which is also supported in v2.9.x).

There is an additional command of /eos/key/encoder_custom in v3.1+ to enable / enable Custom encoder mapping.  That feature is described here: Custom Encoder Maps  I will see about getting this command documented since I don't see it currently listed in this list: Eos OSC Keys

Hi Matt,

Do you think it would be possible to supplant the toggle behaviour of the Custom softkey in OSC by adding an argument at the end of the OSC message (for example /eos/key/encoder_custom [0 or 1]) ?

Hi Matt,

Do you think it would be possible to supplant the toggle behaviour of the Custom softkey in OSC by adding an argument at the end of the OSC message (for example /eos/key/encoder_custom [0 or 1]) ?

"Key" commands are meant to replicate the pressing of the actual console key or button.  An argument of 0 or 1 when related to a key means "edge_up" or "edge_down". 

If you would like a deterministic behavior, please post a request in Feature Requests: (+) Eos Family Feature Requests - Eos Family Consoles - ETC - Community

Thanks Matt, that's what I did one year ago :

 Argument 0 or 1 for the Custom Map OSC command 

but no one will ever vote for this suggestion.
And you're right, tha'ts not exactly the point, cause my wish is indeed a determinastic behavior, not the ability to press or release this key in OSC.