[FEATURE]: Use Custom Control Buttons as Companion Buttons

[wuffwuff2003]

Hi :)
Is it possible to implement the Custom Controls as Action Buttons (later also the knobs as variables for the new Stream Deck plus). I would do it myself if there was a possibility. I am Beta Tester of the wing, so have the whole docs about the OSC Commands.
My main goal is to use the TAP Tempo Button, as well as the SendsOnFader with a dedicated BUS (as it is only possible in the CC).
Many thanks

[istnv]

Does OSC expose the custom controls? I was unable to find any way to detect (or press) them on other consoles.

[wuffwuff2003]

Hi take a look here
WING-OSC-Documentation.pdf

[istnv]

I have that document.
Via OSC you can SET the purpose of a button/knob or GET what the button/knob is configured to do.
Unless I am not seeing where, nothing is sent to indicate any particular button/knob is being pushed or rotated.

[wuffwuff2003]

Yes I dont understand the programmation of this, but when it is not possible to fire the action behind an CC so I think it would then be possible to fire an Action directly form an effect , like a delay, and then of course this will then result in lots of programmation.

[wuffwuff2003]

What I can suggest maybe is when you write the code for one effect, and send me this I can try to add all the current effects in the wing. I only need a presentation of 1 effect. That can help you save time if you wish? Thx :)

[AntonioPatane]

I would like the "Disable Bus Assign" to be implemented on the Talkback page, it would be useful in programming direct talk on one bus, excluding the others

[elliotmatson]

@janikwitzig I'm looking at this feature. It looks like if you assign any MIDI push action to a button or encoder, it will send updates when pressed or released. The OSC update seems to only be related to the button being pressed, not the MIDI command assigned to it. For example this is pressing user button 1 on a WING Compact:

Updating variable: /$ctl/user/U1/1/bu/val [ { type: 'i', value: 127 } ]
Updating variable: /$ctl/user/U1/1/bu/val [ { type: 'i', value: 0 } ]

I just messaged in the bitfocus slack to see if there's a common design pattern for triggering companion actions via a module. I feel like the UI is going to be the hard part for this

[janikwitzig]

I don't fully understand this request to be honest. Is the idea to eventually be able to control something within companion from the WING?

[elliotmatson]

Yea, I think the idea is to be able to use the custom buttons on a Wing as companion buttons. The companion devs are working on a module system for surfaces, and I think we should just wait until that is released for this feature

[janikwitzig]

Sounds good to me