Not much to say. You know how it works. This could be a great feature.
Do you want to to send OSC or receive? Or both?
For myself, I think receive would be much more important than send. The ability to control an SQ via OSC would make it worlds easier and more reliable to integrate the SQ into Qlab setups. OSC-send would potentially be useful in a few niche cases, but I can also see that being much more difficult to implement as you’d have to introduce all the frameworks for describing OSC targets and then tying those to actions on the board.
As castillar said, receive would be used more than send. But, it would be strange if a product like an SQ only has receive support and not send support. It makes sense for other products like projectors etc., but a console would need to have both, due to the variety of users.
That’s the very reason I brought the topic up, is for Qlab integration.
1 Like
And for the AHM!! That would be great. Send and receive!
1 Like
I would also love to see OSC support for better QLab integration. Level fades can be automated in QLab with MIDI, but its really awkward. QLab natively supports OSC and can have cues to send multiple messages over time to fade a level to a specific endpoint, which is great.
As one implementation option: the A&H MIDI Control software could expose an OSC endpoint for sending messages to the SQ. I used the A&H MIDI documentation to create a small OSC->MIDI bridge application: QLab can send OSC commands (in a vocabulary I made up) to the bridge, which sends the corresponding MIDI to the mixer. It’s very much proof-of-concept code that I won’t be distributing in the AppStore or anything, but it does work. If there were something similar in the A&H MIDI Control app, that would cover a lot of potential use cases on the computer side without any changes to the mixer firmware.