Potential Bug? OSC "Fire Macro" Erratic

Question

Hello, 
 The following address/argument pair has worked just fine for the last 23,853 years, but recently it has erratically stopped working correctly. Occasionally&mdash;not always&mdash;it just enters the macro and its number into the red letters, but doesn't actually fire it. Address: /eos/macro/fire Argument: 50 
 Occasionally it will get in a funk where it just types it in red letters but fails to execute. I can send the OSC 2,438 times in a row and get the same result. I look at the Diagnostics tab and the OSC packets appear to be coming in correctly. It comes in as: [GLOBAL/UDP] RECV [OSC Packet] /eos/macro/fire, 50(s) That's how it comes in every time. But sometimes it responds by just typing in the macro and sometimes it responds by typing in the macro and then actually firing the macro (the correct behavior). When it actually fires the macro, I see the exact same line in diagnostics above pop up, but below that then appears the following: Firing Macro 50 And in those cases it does indeed fire. It seems like I'm able to get it out of the funk by saving the show file and hitting Live. That seems to sort of reset things. 
 I only just started noticing this after I updated to Eos Version 3.2.2 Build 25, which I believe I downloaded and updated last Friday or Saturday. This is on Nomad by the way. 
 I filmed a video of the behavior before and after saving the show file to demonstrate both modes.

eos moderator · Accepted Answer

You're already in the right place to report a bug. We're just currently having a hard time reproducing, but will do another round of testing. This might take a moment. 
 Current theory is that a key gets stuck, e.g. Shift remains pressed. Because you're using /eos/key with arguments rather than the keys inline it's possible that the console thinks you're trying to have a key combination. 
 /eos/key/shift=1.0 (where = denotes the separation between address and argument) is the syntax to have a button held down, /eos/key/shift=0.0 to release.

eos moderator · Answer

jordanhenshaw said: here's what I found 
 Have a look at how this looks in the online manual (rather than Tab 100): https://www.etcconnect.com/webdocs/Controls/EosFamilyOnlineHelp/en-US/Default.htm#32_Show_Control/08_Open_Sound_Control_(OSC)/Supported_OSC_Input/OSC_Key.htm 
 The formatting is not perfect but better. I will take a note that especially the table formatting in Tab 100 needs a refresh and hand over your comments to the tech writer team.

eos moderator · Answer

There isn't. The reason why button behave differently is because some act on the down edge (when pressed) and some on the up edge (when released). Buttons than can be both the first part of a key combination and a standalone button as well, will only act on the up edge for the standalone function. 
 The key combinations for About display toggles are why About only acts as the regular standalone function when released. 
 Displays also has key combination funcitonality, as well as long-press, standalone single press and standalone double press. 
 The buttons that can be the first part of a combination or have long-press functionality that come to mind are Shift, Displays, About, Learn, Fan, Params, Filter, MoreSK, the navigation buttons (like Tab) and the playback buttons (like StopEffect).

Potential Bug? OSC "Fire Macro" Erratic

Top Replies