Magic Sheet Button Label Changes When Sending OSC

Both the down edge / up edge behavior and the labeling are expected behavior.

If you hover your mouse over the Command field you will get a tooltip showing what possibilities the command field offers. The same text is also available in the Eos manual. You can use the behavior with a single address where arguments of 0 or 1 are added, or you can define the down and up edges yourself using two addresses, the first one is the up edge, the second one the down edge:

/device/slider=0.75
/device/slider=0.25

Command objects are meant to show you the argument of a specified OSC address, this is what you're seeing. If you feel this behavior should be changed or expanded in any way, feel free to add a feature request.

Ah, okay — I didn’t realize that the object text being overwritten by the argument is intended behavior.

When I use

the text label is not overwritten, and that actually works well for my use case. Thanks for pointing that out.

One more question: is it possible to send two different OSC strings on button press and button release?
For example:

When I enter it like this, both commands are sent at the same time instead of on press and release.

The down/up edge definition only works if you use the same address twice.

The down/up edge definition only works if you use the same address twice.

Okay, thanks for your help.

We’ve now found a way to make this work. Our goal was to trigger a button in Bitfocus Companion, and it was important for us that the tap and release behavior works correctly. Unfortunately, Companion listens for two different OSC paths for tap and release, which doesn’t match what Eos sends:

As a workaround, we’re now using the ETCLabs OSCRouter to translate the OSC commands. We created a route with the input path /tap/* and the following JavaScript as the output:

location = OSC.split("/").slice(-3).join("/");
if (ARGS == 1) {
    OSC = "/location/" + location + "/up";
    } 
else {
    OSC = "/location/" + location + "/down";
    }

Our MagicSheet buttons are sending the following commands:

/tap/<bank>/<row>/<column>=0

/tap/<bank>/<row>/<column>=1

The JavaScript now translates all paths starting with /tap into the format that Companion expects.

Maybe this description will be helpful for someone else as well.