Search Results for 'qu midi protocol'

Hello, I’m working to control our Qu-16 through MIDI using some third-party software. I’ve downloaded the MIDI Control application for Mac, but I’m running into a few roadblocks to get started.

I’m a bit lost after taking a look at the Allen & Heath MIDI documentation to do some basic control of the faders – mute on/off and fader levels.

The software asks for the MIDI message type, channel/input, parameter 1 and parameter 2. Would I simply set the MIDI Control protocol to CC Translator and do something like this?

Maximum volume – control_change, 1, 7, 127
Minimum volume – control_change, 1, 7, 0

To mute/unmute, what value do I use for the key/note number? I understand I need the following:

Mute on – velocity >= 40 followed by note off
Mute off – velocity <40 followed by note off

Also, do the inputs start at 0 or 1?

Thanks in advance.

[KeithJ A&HModerator]

@vtmn7777

There is no API, but the Qu does include MIDI for remote control of most all parameters.
The full protocol is described here – https://www.allen-heath.com/content/uploads/2023/06/Qu_MIDI_Protocol_V1.9.pdf

Thanks,
Keith.

[Nicola A&HKeymaster]

The authentication is only required for the TLS/SSL connection. With the TCP connection on port 51325, no authentication is required. I would suggest using this port first, to test and verify control messages, before moving on to a secure connection if needed.
All of the apps you listed should be able to communicate with your AHM without the MIDI Control driver in between.
Make sure you’re referencing the latest TCP protocol from https://www.allen-heath.com/hardware/ahm/ahm-32/resources/ and give us some examples of hex strings you’re trying to send.

[BobbyDazzler59Participant]

CQ mixpad is not that bad to use for setup and initial levels. Its the lack of user layout and or grouping for live set tweaking.

I will run it on my touch screen laptop which is so much easier than a touch pad or mouse, its hard wired network thru my router to the CQ with a private network for the iPad remote operating

I have indeed tested out the timed trial version on Mixing Station and manage to create several IDCA faders and group controls and finally paid for the CQ version a couple days ago. So that now fills some operating holes. I can now adjust the drum group, backline group and the vocal group overall levels now which also gives a group mute, which is missing as a function on the CQ and I presume then does not allow creating same group mute function in MS, so its handy the IDCA can do it. This makes life on stage simpler now as I can also create custom console screen which just has the drum and backline group controls, 4 vocals with the group control intervl music st channel and master fader all in one screen. Super easy for quick glance and adjust if needed and not wading thru pages.

Wait with bated breath for the first CQ and or app firmware updates, maybe then there will be midi protocols added and we can use usb midi controller faders

[AudioMarshParticipant]

Hi there, sorry if the answer to my question is buried in the technical stuff above. I have a qu-24, and I’m trying to control Pro Tools. Whenever I collapse folder tracks, the physical faders that were assigned to the now hidden tracks are reassigned to different tracks. This makes it really difficult to label the qu and get used to what channels/groups I’ll find on what faders… I’ve tried to experiment with MIDI Thru instead of the HUI protocol but I didn’t get very far! (there seems no generic midi protocol option in the peripherals dialogue!) Any pointers on where I might be failing would be greatly appreciated! TIA 🙂

[KeithJ A&HModerator]

@pcpmafic

We’ve had requests for slightly different implementations at the moment.
One way would be closer to Qu, where more parameters can be controlled at lower resolution (https://www.allen-heath.com/content/uploads/2023/06/Qu_MIDI_Protocol_V1.9.pdf)
The other is closer to SQ, with fewer parameters at higher resolution, relative control and ‘get’ messaging (https://www.allen-heath.com/content/uploads/2023/11/SQ-MIDI-Protocol-Issue5.pdf)

The former is generally from producers and engineers, the latter from installers and integrators.

From your mention of use with Ableton, please add your voice to the feature suggestion section here – https://community.allen-heath.com/forums/topic/cq-recive-midi-from-ableton 🙂

Thanks,
Keith.

Hello all,

I’m exploring using an SQ-6 as an interface+mixer centerpiece for a home studio, in concert with a DAW and some analog gear. Here are some of my pre-purchase questions:

1) How good are the AD/DA converters? I’ll probably be using outboard pres, but I am looking to use the local analog IO to accept the output of these pres, as well as to go out and back to analog insert processing. I’ve seen mentions here of the superiority of DX and Prime over the local IO, leading me to believe the local IO is not the best A&H has to offer.

Specifically related to the AD/DA converters (not the pres) – how do they compare to the ADC/DAC chipsets in the current crop of audio interfaces from Motu/Focusrite/UAD/RME et al?

What chipset is being used for conversion in the SQ?

What’s the difference in conversion between SQ/DX/Prime?

2) Related: given there are no pre-bypassing line ins (other than the TSRs), how transparent are the pres to line-level input with zero gain?

3) How do the “DEEP” add-ons compare to equivalent VST plugins?

4) I’ve watched the ‘latency’ video (and many others 🙂 which unfortunately didn’t cover MADI. Has anyone subsequently tested MADI latency with SQ, especially vs Dante?

5) How loud do the fans get?

6) I appreciate and intend to use the MCU-based DAW control. Given that the SQ does not have touch-sensitive faders, does anyone have experience writing/updating DAW automation with it?

7) related: I noticed that the SQ scribble strips can pick up the DAW track names, but I didn’t see a way to address the scribble scripts via the SQ MIDI protocol – how does that work? (I’m presuming that the MIDI Control MCU driver sits on top of the SQ MIDI protocol, if not, what then?)

8) Is there OSC support for SQ?

Thanks so much for any info!

Rich

[KeithJ A&HModerator]

@FatherTime

Nothing at the moment, but we needed to include MIDI in the USB connection in case we ever want to implement a MIDI protocol (as we’ve done with Qu and SQ over USB-B in the past).

Thanks,
Keith.

We use Allen & Heath consoles in House of Worship projects frequently. And calling particular EQ presets for particular mic inputs from the automation system would be a great combination and strengthens our hand when designing a solution. Since müezzins and imams are like professional singers and different EQs are vital for different users.

When you are updating the SQ or QU mixers control API, I would appreciate if you take into account this concept and maybe you can enhance the protocol by adding the ability for recalling EQs from the library.

Best,

[Nicola A&HKeymaster]

I’m sure there’s other options, but Qlab can send program changes based on real time clock, and is widely used in the show industry.
You will need to run it with the A&H MIDI Control driver.

To answer your other question: Director, the dLive Surface, dLive MixPad and Custom Control all use our proprietary AH-Net protocol to communicate with the MixRack. However, program changes and many other parameters can be controlled via the public MIDI/TCP protocol available on our website.

[Rafael A&HModerator]

Hello Steve,

For quick control of scenes I suggest using Soft keys, it is very easy to program.
The amount of scenes will relay on the mixer itself, no external application would be able to increase these.
However, just for your reference, SQ mixers offer up to 300 scenes.

Whether is with QU or SQ, another very practical way of controlling scenes is through an external software using MIDI such as QLab.
If you most stick with QU and still need more than 100 scenes, you might want to look into creating all your Mute/Unmute cues directly from QLab and trigger them as QLab group cues, rather than switching scenes in the console.
You can create a group containing multiple cues that would Mute or Unmute different channels in the mixer and trigger these simultaneously by triggering the group.

For your reference: https://qlab.app/docs/v5/
https://www.allen-heath.com/media/Qu_MIDI_Protocol_V1.9.pdf

Cheers,
Rafael

Not troubleshooting, just curious.

Does anyone know if there is any MIDI commands for Input Source (ABCD) selecting? I would like to have all my spare body packs selectable through my stream deck XL, I currently use the custom buttons on the s7000, but it’s not enough.

I can’t seem to see any commands in the dLives documentation, but that doesn’t always mean its not there.
https://www.allen-heath.com/media/dLive-MIDI-Over-TCP-Protocol-V1.9.pdf

Thanks

[nottooloudParticipant]

I never liked my Soundcraft Impact, but it had a great front panel layout. A&H’s QU desks have a full set of EQ controls in a straightforward grid. I really wish SQ had the same instead of this arty smattering of knobs. Seems like a big step backwards.

Interesting. I hadn’t dug into the SQ MIDI Protocol doc before, but it doesn’t seem to have anything for EQ and such. Nothing about parameters for the selected channel. This is, fortunately, a trivially easy thing to do via Mixing Station. Run Mixing Station on a laptop or tablet, plug pretty much any MIDI controller into it, tell it what knob or fader does what parameter, and you’re set.

[KeithJ A&HModerator]

Just before anyone opens up their mixer – there is nothing in there to solder anything to!

The best way to incorporate an external switch is by using the MIDI protocol, either through a computer or with a BomeBox (https://www.bome.com/products/bomebox).
The BomeBox sits on the same network as the mixer and can take a USB or 5pin MIDI input, messages can then be sent directly or translated to the Qu.
This means you could hook up virtually any MIDI controller or footswitch and use it to control most any parameter on the mixer.

MIDI messages the Qu can receive are all detailed in the MIDI protocol document (http://www.allen-heath.com/media/Qu_MIDI_Protocol_V1.9.pdf).

Thanks,
Keith.

[MityVeeParticipant]

Thanks, Keith.
Yes, I have tried every possible combination of starting and setting up MIDI CONTROL First, chosing virtual ports, starting App.
I usually know my way around Midi Setups.
I try to clarify:
When I choose CC Translator Protocol in MIDI CONTROL and then start any Midi Message App three virtual Ports have been created: CC Translator Inputs, CC Translator Outputs, CC Translator Midi Thru.
If I choose “CC Translator Midi Thru” as the Apps Output all messages get through to the SQ, as indicated in the bottom right corner in MIDI CONTROL and the “reaction” of the SQ to that message.
When I choose CC Translator Inputs (or Outputs) as my Apps Output and send the exact same messages (or the simple CC’s and note on/offs that would be translated for the SQ) they don’t even seem to reach MIDI CONTROL since there is NO indication in the bottom right corner any more and no “reaction” from the SQ of course. As if those two Ports just “swallowed” all data. Change back to CC Translator MIDI THRU and everything’s working fine again.

I’ve not heard of before but could other ports from other interfaces and such impede on those MIDI CONTROL Ports? I have quite a few up and running in my system (around 20) but have never had any problem.
I have not tried the USB Midi connection yet, which I will do out of curiosity. But TCP/IP it needs to be for me.
Of course, in the end I can run all messages through MIDI THRU as well, i was just wondering if there’s a fix or something I’ve missed.

Thanks for your help!