So what you could do to fix this is basically send it as a master playback which allows ONYX to select what it wants to do. (Just like set your master buttons normally)
If you don’t use the masters you can only send go, pause, release, select and toggle.
I could fiddle around with OSC and see if i can find any solutions for you and me. From what iv’e understood many people/technicians want the “flash” function for OSC playback buttons.
I’m not sure I follow. I’m already using my all of my Main Playbacks for other functions.
I don’t understand why an Override will function properly via the Playbacks page, if you hold the button on the screen and then release the button it releases just like a flash button. So it would seem the behavior should work the same via OSC
Okay, So what i ment was that you cant use OSC to triggers to trigger flash buttons unless its in the main playback. Onyx cant recieve a osc command that says “flash submaster 1”, it can only recieve commands such as “go”,“relelease”,“toggle” and so on.
If this doesnt help at all then you could contact me on discord. @Hedsma#9220
Hi there. I have the same issue. I have a playback button programmed to toggle on/off when held/release for one of my cues. Works fine in Onyx but latches on when using Touch OSC. Any quick workarounds while the developers work on it?
I’d have to play around in OSC Editor, but I believe that OSC does not (at least by default) send an ‘up’ notification when you release the button. Or Onyx does not listen to it if OSC does send one.
So you can trigger things with Down presses, but not Up.
In your case Taraguitar, can you leave it as toggle and tap the OSC button again to release?
I’m hoping once the hardware side of things settles down that we’ll get some OSC development.
There are a lot of things that could be included as OSC commands that are not currently.
Hell I’d even settle for a complete breakdown of OSC command identifications for the existing stuff.
(Yes I know there’s that pdf doc, but its limited and does not map what ID#'s are for what control very well)
Well, you just do something and read through the list of feedback in an OSC viewer method. If there’s an associated OSC command then I’d think that it would show up in the feedback.