Search Results for 'qu midi protocol'

Forums Forums Search Search Results for 'qu midi protocol'

Viewing 15 results - 31 through 45 (of 198 total)
  • Author
    Search Results
  • Profile photo of Michael


    I’m working on writing a module for the SQ series mixers using QSC’s QSYS platform, and will be with Crestron soon after.

    I found the SQ-MIDI-Protocol-Issue1 document, which provides a lot of help, but I have a few feature requests:

    1) There is no way to ‘get’ the last/current recalled scene on the mixer over the MIDI protocol.

    2) It would be super helpful to have access to the scene names for tighter integration/feedback through our control system.

    3) There are a number of other controls that are available on the GLD series, D-Live series, and even the QU series that would be fantastic to have on the SQ, in terms of (IMHO) priority:
    Remote Shutdown (HUGE for power sequenced systems, which is 90% of our installed systems, so the board can be prepared to be shutdown automatically)
    Channel Name and Color
    Preamp Gain
    Phantom Power

    There are also no real guidelines in terms of best practices of polling intervals or limitations, which could become a problem when tracking 100++ controls within an acceptable ‘live’ tolerance. Via wireshark, I can see there are other methods in use for the SQ-Mix application, and I can’t help but wonder if that interface/protocol is a better solution for integrator such as myself to work with, but there’s no documentation or support available for interacting with that. Thoughts?

    Profile photo of KeithJ A&H
    KeithJ A&H

    Hi Marcin,

    Yes, there are ways to send MIDI via TCP/IP from a Stream Deck and use this to control an SQ.
    The most simple way is shown in this article ( You would just need to use the IP address of your SQ and the messages shown in the MIDI Protocol Document here (

    Another way would be to use stream deck ‘companion’, which is third party software. Though this doesn’t currently have SQ presets, so it might be quite hard to get it all working!

    [just for clarity, as we have been asked before, there is no way to connect a stream deck directly to the console]



    In reply to: Midi for scenes

    Profile photo of Nicola A&H
    Nicola A&H

    You would need to open a TCP connection to the SQ, not something the dLive can do automatically I’m afraid.
    A dLive can recall Scenes on a remote dLive, Avantis, GLD, iLive using Embedded Recalls, if on the same network. SQ and Qu are a different platform despite the similarities of the TCP protocol, and would not be seen by the dLive.

    Your best option is a programmable MIDI interface like the BomeBox.

    Profile photo of Alex A&H
    Alex A&H

    Hi Salem,

    The easiest way to control the Qu faders and mutes from Reaper would be to use the CC Translator protocol available in the latest version of DAW Control Driver.

    Unfortunately, this does mean you won’t be able to use DAW Control via the Mackie protocol at the same time.

    You can find more information on the CC Translator here:

    It may also be worth having a look at the Qu MIDI protocol here:


    Profile photo of KeithJ A&H
    KeithJ A&H

    Hi Jason,

    I can give you some of the answers here, but I’m sure there will be other users with experience of both systems that can give some feedback too.

    1. iLive was supported for about a 6-year window. I know none of you have a crystal ball, but do you think SQ’s will be supported for that time considering the SQ series was announced in 2017? What has been the supported life of an A&H series in its history?
    We are still supporting customers using A&H consoles from the 1980’s. It does become a trickier question to answer with digital consoles and especially compatibility with future computer operating systems (which we also would need a crystal ball to know about!) but we do support consoles for as long as possible. If your question is more about firmware updates, then there will always be a time when a system matures and there is a finite number of features that can be added. But looking at our other digital consoles (actually iLive launch to last firmware was approx 10yrs), this won’t be for some time with the SQ. We always advise considering at the capabilities of a system today though, i.e. make sure the console does everything you require right now, and then future updates are all a bonus.
    2. Does the SQ series support AVIOM in-ear monitors?
    The SQ features a built-in SLink port, which works with dSnake, ME, DX and gigaACE protocols. There is also an option card slot with currently available cards being Dante, Waves and a secondary SLink. But no, there is no direct support for the Aviom protocol.
    3. The IDR-32 is NOT compatible with the SQ series, correct?
    If you mean to use the iDR-32 as a stagebox for the SQ, then you are correct – the iDR-32 is a mixer (for which your T112 is a control surface), and the SQ is a mixer. So these are two systems that you would be connecting and you would only be sharing audio between the two and no control messages. That is to say, with a Dante or Waves card, you could send and receive audio to and from each system, but the SQ would not be able to directly control the preamps in the iDR.
    4. How many monitor mixes are available on the SQ?
    The SQ has LR + 12 mono or stereo mixes that can be used as auxes or groups + 3 stereo or mono matrix mixes. So if you are not using groups, then you could have up to 12 stereo monitor mixes along with the main LR.
    5. Any other information for my consideration would be greatly appreciated considering I am migrating from the iLive-T112…
    – SQ uses the latest technology for processing and mixing, and is built on a 96kHz XCVI core, with benefits to audio quality and latency as well as the ability to run DEEP add-ons from dLive.
    – iLive has 64 input processing channels and fully configurable mix busses, SQ has 48 input processing channels, and a more fixed mix bus structure.
    – From Q3 it sounds like you may need to consider the digital expansion options, the SQ works with every A&H expander, but it’s worth thinking about the whole system at the same time, and what would work best for you. (
    – Your T112 has a lot more hands-on control, and information displayed at one time, whilst the SQ is a much faster system overall (boot times, mixer config changes, fader speed…).
    – The SQ has more built in options for recording.
    – Probably the best thing would be to note which features are essential in your iLive system, and then check to see if they are also on the SQ. Previous to dLive, iLive was the flagship console, and there are a few features that are just not possible on the much more compact SQ (very granular scene management and filters, built-in show storage, MIDI control mapping, fader banks and strip freeze). The Avantis would be a closer match in channel count, but of course the equivalent of the iLive would be a dLive.

    Hope some of this is of use.

    Profile photo of Mr.X

    Use Method #1.

    No custom MIDI required. The dLive spits out a MIDI PC message that should match the Waves MIDI format on Scene change.

    You’ll need to download and install the A&H DAW driver to convert the TCP MIDI to a Virtual MIDI port on your computer that houses the Waves Rack software.


    In reply to: QU-32 Mute button

    Profile photo of Alex A&H
    Alex A&H

    Hi Thomas,

    You can find how the Qu uses MIDI here:

    In your generic controller, try changing Un-mute to Note On 1 G♯0 63.

    I say this because a mute control uses a Note on message followed by a note off message. For example

    90 20 7F 80 20 00 – turns the mute on for CH1

    It is the velocity which changes the control on Qu. For example

    90 20 3F 80 20 00 – turns the mute off for CH1

    You may also notice that the note off message (80 20 00) is the same in each example. The Qu does work when you don’t send that last message for this control, so you can just send the first Note on message and change the velocity to change the control.

    You may find our MIDI webinar useful also:



    In reply to: QU-32 Mute button

    Profile photo of tom42

    Hi Alex,
    thank you very much for fast response!

    Yes, the Mackie Control Protocol via ‘DAW Control’ works fine, I also tried this out. But connecting via Generic MIDI Controller I can use also the EQ encoders on QU-16 to do my EQ settings in Cubase, that’s a lot of fun 🙂
    But You pushed me to a interesting point saying that ‘Note on’ and ‘Note off’ Messages are not the same.
    So today I installed ‘Midi Monitor’ and debugged the Messages between QU-16 and Cubase when you push ‘Mute’ or ‘Un-mute’ in Cubase to find the difference between the Mackie protocol (which works fine) and the Generic MIDI Controller (which doesn’t).

    The difference is:
    Mackie: pushing ‘Mute’ or ‘Un-Mute’ in Cubase, always a sequence of 2 Messages (‘Note on’ and ‘Note off’) is generate by DAW Controller App and sent to QU-16:
    (Example for Channel 1):
    14:21:58.892 To MIDI In Note On 2 C-2 127
    14:21:58.892 To MIDI In Note Off 2 C-2 0

    14:23:13.653 To MIDI In Note On 2 C-2 63
    14:23:13.653 To MIDI In Note Off 2 C-2 0

    Generic Controller: only one single message is sent from Cubase directly to QU-16 (without ‘translation’ from DAW Controller App):
    14:19:39.700 To MIDI In Note On 1 G♯0 127

    14:20:32.555 To MIDI In Note Off 1 G♯0 0

    ==> So along to my understanding Cubase always sends one single message (Note-on or Note-off) and only via the DAW Controller App they will be ‘translated’ into the needed sequence of 2 messages expected by QU-16, right?
    (By the way: QU-16 also sends this sequence of Note-on & Note-off message to Cubase for a single push of Mute button – what’s the reason for this?)

    You mentioned the need of two separate controls to be able to send back a Un-Mute MIDI message understandable for QU-16 using Generic MIDI Controller (I think the MIDI sequence described above is needed).
    I tried this but I coulnd’t make it working.

    Do you have a concrete description how to do this?

    Thanks a lot in advance & Many Greetings!

    Profile photo of Smalltown Jim
    Smalltown Jim

    Hi, I’m pretty competent with the the audio functions of the QU series and many other live PA products but recently I’ve been delving into DMX and some DMX control systems, If I understand the QU series user manual correctly, it appears that it can send MIDI information Out via the USB -B or Ethernet network ports?
    One of the DMX control systems I’m considering working with can respond to multiple signalling protocols including GPI, MIDI, UDP, TCP & OSC, I’m interested in making the lighting system respond to audio gate open functions on specific input channels of our QU series mixers, so my initial question is can the QU series output a code on the event of a audio input gate opening? I assume that it’s more likely to be a MIDI signal as opposed to the other protocols available to me but as the lighting system also has four General Purpose Inputs (GPI) ports that can be configured to respond to either incoming analogue or digital signals, I’m open to suggestions if I can setup some suitable electronics to match up the necessary electrical parameters to match the equipment.

    Thanks in advance.

    Profile photo of Mike C
    Mike C

    This depends on a few things:

    – What MIDI message is being sent out? Does it match the protocol for mute control?
    – You could use either the USB B or Network port for this, so it depends what outputs are available from the converter and how configurable they are.
    – You could use something like the BomeBox ( to interface between the two systems. This also has the option to translate the incoming and outgoing messages, so it doesn’t matter if the message being sent by the converter is compatible with the Qu.This depends on a few things:

    Here is the contact closure to MIDI unit I found
    The BomeBox looks like it would take the midisoultions unit and let me connect to the USB B for the midi control input.

    I just downloaded the MIDI protocol info for the QU. I’ll see if the Midi Solutions unit can be programed to output the protocol needed.

    The only things I need to control will be individual channel mutes and a group or DCA mute.

    Mike C.

    Profile photo of Alex A&H
    Alex A&H

    Hi Mike,

    This depends on a few things:

    – What MIDI message is being sent out? Does it match the protocol for mute control?
    – You could use either the USB B or Network port for this, so it depends what outputs are available from the converter and how configurable they are.
    – You could use something like the BomeBox ( to interface between the two systems. This also has the option to translate the incoming and outgoing messages, so it doesn’t matter if the message being sent by the converter is compatible with the Qu.


    Profile photo of Mfk0815

    What do you mean with „the server“? Hardware, software and in particular which one?
    Have you read the MIDI documentation MIDI can be used to control several parameters of the QU. If you want to find the documentation of a particular model you have to look at the web page of that model.

    Profile photo of Chrissy

    GLD is a user-friendly, cost effective and scalable live digital mixing system, conceptually based on the hugely successful digital iLive series. A standard GLD 32 input system offers 28 XLR mic inputs with plug n’ play I/O expanders allowing easy expansion up to 48 inputs (44 XLR mic inputs).

    At the heart of the system is the GLD-80 mixer, providing 48 input processing channels, 8 stereo FX returns fed by iLive’s acclaimed FX emulations, 30 configurable buses, 20 mix processing channels, and DSP power to provide full processing without compromise.

    GLD-80 has an analogue-style channel processing control section complemented by a graphical 8.4 inch touch screen. A fully-customisable drag ‘n drop layout allows quick and easy assignment of inputs and mixes to fader strips. There are 20 fader strips in 4 layers, each with motorised fader, a channel LCD display which can be named and colour-coded, plus a rotary control for direct access to gain, pan and aux/FX sends. The mixer‘s local I/O comprises 4 XLR mic/line inputs, 4 XLR line outs, 4 RCA inputs, 2 RCA outputs, and digital outputs in SPDIF and AES3 formats.

    The GLD-80 connects to a range of plug ‘n play I/O racks to ‘build’ 28, 36 or 44 mic input systems. A primary AR2412 rack (24 XLR inputs, 12 XLR outs) and up to two AR84 expander racks (8 XLR inputs, 4 XLR outs each) can be connected over 120m CAT5 runs using A&H’s dSNAKE protocol. dSNAKE provides control to the remote preamp, and all mic preamps are scene recallable. AR2412 also includes a connection for personal monitoring systems.

    GLD has the ability to record and playback a stereo signal on a USB memory stick. Standard iLive audio I/O option cards for Dante, MADI, EtherSound and Allen & Heath’s ACE protocols can be fitted, allowing multi-channel record/playback, FOH/monitor splits, and connection to A&H iLive systems, which can easily be configured using GLD’s extensive soft-patching.

    • Compact digital mixer with scalable, remote I/O
    • Systems from 4 to 44 mics
    • Easy to use, quick to access, analogue style interface
    • dSNAKE Cat5 digital snake—up to 120m cable length
    • 8.4 inch colour touchscreen for graphical view and setup
    • 20 faders, 4 layers, 80 channel strips in a freely customizable layout
    • 48 input channels into 30 assignable buses (Aux, Group, Matrix, Main, FX Send) into 20 mix outputs
    • 8 stereo RackFX engines with dedicated ‘short’ returns with 4-band PEQ
    • Full processing on all inputs including trim, polarity, HPF, insert, gate, 4-band PEQ, compressor and delay
    • Full processing on all outputs including insert, PEQ, GEQ, compressor and delay
    • LR, None (monitors), LR+M (sum), LR+M (bus), LCR main mix modes
    • 16 DCAs / mute groups
    • Built-in Talkback, RTA and Signal Generator
    • I/O module options for FOH/Monitor split, multitrack recording, link to iLive and more
    • MIDI In/Out and Ethernet Network port
    • AviomTM Pro16 compatible Monitor port on main AudioRack
    • High end 1dB step recallable mic/line preamps
    • User definable channel names and colours
    • Engineer’s mono Wedge and stereo IEM strips
    • Input, output and insert soft patchbays
    • Quick copy, paste and reset of mixes and parameters
    • Libraries, Scenes and Show memories with USB transfer
    • Get started quickly with Template Shows

    $4200 shipped

    Pm me for pictures and inquiries.

    Profile photo of mixJM

    Elgato looks very complex to setup, requires a running computer with Elgato software and it’s limited to dLive MIDI protocol.

    Soft Keys are far more powerful and I am hoping more people would support this suggestion.


    In reply to: Qu MIDI specs

    Profile photo of tim4742

    To find the document select one mixer and look under the “documents” tab.

    The direct link to the currently latest document is:

Viewing 15 results - 31 through 45 (of 198 total)