Search Results for 'qu midi protocol'

Forums Forums Search Search Results for 'qu midi protocol'

Viewing 15 results - 46 through 60 (of 221 total)
  • Author
    Search Results
  • Profile photo of jBam
    jBam
    Participant

    Hi there – I’m wondering if someone can help confirm whether the QU16 midi protocol will allow me to ping/query the value of a parameter without changing it?

    e.g. if I have HP filter on Channel 1 set to variable “120”, the message is:

    B0 63 20
    B0 62 13
    B0 06 “VA”
    B0 26 07

    Where “VA” is the variable (“120” in my example)

    If I don’t know what this value is, can I send a message to the Qu16 to ask what the current value for this parameter is?… and then it would send back a response (e.g.):

    B0 63 20
    B0 62 13
    B0 06 120
    B0 26 07

    as a return message??

    I see the protocol document has some guidance on “Get System State” for ipad / q-pad connectivity (which seems similar), but not sure if that’s able to give me individual parameters?

    I’m writing a Bome’s Midi Translator script for using the custom layer (with faders set to midi) to control weird and wonderful things back within the Qu… Being able to ping existing values would be amazing for my purposes…

    #92125
    Profile photo of Alexandernaut
    Alexandernaut
    Participant

    Hey all, I’m trying to parse meter level data from the QU via a TCP connection, but getting confusing results. I’ve successfully made the connection and receive the meter data, but am unable to parse it properly.

    I follow the specs outlined in the Get Meter Data section of this document: https://www.allen-heath.com/media/Qu_MIDI_Protocol_V1.9.pdf.

    As a test, I’m first trying to get the data from CH 1, Post Preamp. If my understanding is correct, this should be first 3 response bytes after the response header.

    So to get these 3 bytes, I look at the response buffer. The first 10 bytes are the response header, so I grab the following 3 bytes:

    uint8_t extraByte = _meterBuffer[10];
    uint8_t msb = _meterBuffer[11];
    uint8_t lsb = _meterBuffer[12];

    I then perform the logic from the spec using those bytes. Here’s the log for one pass:

    extraByte: 0101 0101
    msb: 0001 0011
    lsb: 0101 1001
    msb (parsed): 1001 0011            // after prepending with the appropriate bit from extraByte
    lsb (parsed): 0101 1001            // after prepending with the appropriate bit from extraByte
    combined: 1001 0011 0101 1001      // after combining them all to make a 16 bit int
    offsetedValue: 0001 0011 0101 1001 // after subtraction of 0x8000
    dbValue: 19.347656                 // after dividing by 256.0f

    All of the logic makes sense to me and follows the midi spec, and the values do change as the mixer receives input, but… over time, the values are simply not what I expect. They don’t follow the meter ui in the Qu-pad app, and seem to jump all over the place.

    Here are some dbValues following a short impulse response from a synthesizer. All values of complete silence are -126.929688 (as you can see these values bookend the response):

    dbValue: -126.929688
    dbValue: -126.929688
    dbValue: 19.414062
    dbValue: 57.402344
    dbValue: 93.390625
    dbValue: -124.617188
    dbValue: -86.628906
    dbValue: -71.640625
    dbValue: -12.652344
    dbValue: 27.335938
    dbValue: 67.324219
    dbValue: 105.312500
    dbValue: -112.695312
    dbValue: -74.707031
    dbValue: -37.718750
    dbValue: 1.269531
    dbValue: 39.257812
    dbValue: 73.246094
    dbValue: 114.234375
    dbValue: -103.773438
    dbValue: -66.785156
    dbValue: -26.796875
    dbValue: 8.191406
    dbValue: 1.179688
    dbValue: 86.167969
    dbValue: 125.156250
    dbValue: -93.851562
    dbValue: -55.863281
    dbValue: -17.875000
    dbValue: 21.113281
    dbValue: 58.101562
    dbValue: 96.089844
    dbValue: -122.917969
    dbValue: -84.929688
    dbValue: -126.929688
    dbValue: -126.929688

    As you can see, the response data does not show a simple decaying impulse. Anyone have any idea what’s going on?

    Profile photo of jonathansp
    jonathansp
    Participant

    Hi Everbody,

    have you already planned to add more commands for MIDI remote control?

    For QU there are a lot more commands implemented:
    https://www.allen-heath.com/media/Qu_MIDI_Protocol_V1.9.pdf

    I’d like to have commands for
    – Input Channel source
    – Insert In/Out
    – Channel Names (and Coloring)
    – PAFL Select (of mix)

    And one more command i liked from my GLD:
    – Mix Select (Like pressing the keys on the right side for send levels)

    Thanks a lot!

    #91766
    Profile photo of Alex A&H
    Alex A&H
    Keymaster

    Hi Qu Users!

    Using a program called Ctrlr (from ctrlr.org), I have made a panel which uses MIDI to control various parameters of a Qu mixer. The intention was to have a Mac/Windows based application that offers a good level of control for Qu mixers. It is by no means finished or fully tested/working at this stage, but it’s a great start for anyone who would like to look at developing something themselves.

    In addition to the Ctrlr panel, I have create maps for the DAW Control Driver. These are used to translate the MIDI messages used by the Qu and Ctrlr and appear as a Protocol option in the DAW Control Driver. You will need to add these maps manually into the Maps folder of the DAW Control Driver, which is usually found in:
    Windows: C:\Program Files (x86)\Allen & Heath\DAW Control\Maps
    MAC: Applications > DAW Control.app > Contents > Resources > Maps

    Changing/adding files in the DAW Control Driver is done at your own risk, but there is a section at the end of this message if you need to return to defaults.

    This panel (and associated files) is not provided, tested or supported officially by Allen & Heath and this is a personal project of mine. Therefore, any questions you have can be posted in the community, but not via any official support channels (such as support.allen-heath.com).
    ———————————–
    Get started:
    – Unzip Qu CTRLR.zip.

    – REPLACE the file ‘mixer_map.json’ in the Maps folder with the new ‘mixer_map.json’ file in the Qu Ctrlr folder.

    – ADD the file ‘QuCtrlrTranslator.ahmap’ from the Qu Ctrlr folder to the Maps folder for the DAW Control driver.

    – Launch the DAW Control Driver and select the Qu mixer and Ctrlr Translator protocol.
    *Some SysEx messages are used with the panel (get system state), so please note that USB MIDI ports will work for all visible controls, but not hidden SysEx commands. Please use the TCP/IP connection for SysEx messages*. See https://www.allen-heath.com/media/DAW-Control-Help-V1.7.pdf for DAW Control Driver setup help.

    – Download and install Ctrlr from ctrlr.org and launch Ctrlr.
    *I’ve confirmed the panel to be working (for most things) in version 6.0.4 for Windows and version 5.3.198 for Mac*.

    – Open the Qu Ctrlr.panel

    – Add all of the .png files in the PNG folder to the resources of the panel in Ctrlr. To do this, select Panel > Panel Mode. The press on the Resources tab on the right side of the screen and click Add. Locate the PNG folder, highlight all PNG files and click open. In the Resources tab, press Reload. Then press Panel > Panel Mode again.

    Have fun!
    ————————————
    To return DAW Control to its default:
    Windows: Go to Settings > Apps, click on DAW Control and select Uninstall. Now go to C:\Program Files (x86)\Allen & Heath\ and pertinently delete the DAW Control folder.
    Mac: Go to Applications, right click on DAW Control.app and select Move to Trash.

    Then install a fresh download of the DAW Control app from https://www.allen-heath.com/daw-control/

    Attachments:
    You must be logged in to view attached files.
    #91338
    Profile photo of KeithJ A&H
    KeithJ A&H
    Moderator

    @jline – The linear taper does allow for high resolution NRPN control, though this relates only to the control to and from the SQ core.

    As in the introduction of the MIDI protocol – “[MIDI] can be broken down into two sets of bi-directional messages. Those that are used with SQ mixing parameters (i.e. level control of SQ audio channels), and those used to control external software or equipment (e.g. to control a DAW)”

    #91095
    Profile photo of Alex A&H
    Alex A&H
    Keymaster

    Hi!

    This post is in the Qu forum and the Qu does not have MIDI control for soft keys, whereas the SQ does.

    The Qu has a lot of parameters available for MIDI control, including mutes and an option to send a fixed delay time value.

    You can find this information in the Qu MIDI Protocol here: https://www.allen-heath.com/media/Qu_MIDI_Protocol_V1.9.pdf

    Let me know if you have any questions!

    Thanks
    Alex

    #90765
    Profile photo of Alex A&H
    Alex A&H
    Keymaster

    Hi Anthony,

    Could you try sending the MIDI messages from Cubase to something like MIDI Monitor for Mac? This way, you can check that the message being sent out matches the Qu MIDI protocol.

    Thanks
    Alex

    #90441
    Profile photo of dB Tech
    dB Tech
    Participant

    Good afternoon friend, I have acquired a QU 16, I have previously installed the DAW Control, then I have connected it through the usb port that is located on the back of the QU 16 to a Mac Book, it has perfectly recognized the inputs and outputs in Ableton Live 10, I open the DAW Control and configuring it respectively, Mixer: qu series, Midi channel: 2, protocol: HUI, option: midi ports and input and uotput ports to QU 16.

    Then I follow the steps you have indicated in this post, I go to Ableton / preferences / audio / audio device / type of controller … and that’s where the option to select QU Asio as controller does not appear, it only appears CoreAudio.
    I need to use the QU 16 to integrate it with Ableton to use some channels via USB B Streaming and other instruments in other physical inputs that I want to go through Ableton to process and send them back to their respective channels so that they can be controlled from the QU 16.
    Try to map from Ableton as a control surface, and when mapping the mutes it is inverted (i.e. active mute in the QU 16 and in Ableton it is deactivated and vice versa)
    I would like to know where I am failing, I appreciate your help.

    Profile photo of Michael
    Michael
    Participant

    Hi,

    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?

    #89441
    Profile photo of KeithJ A&H
    KeithJ A&H
    Moderator

    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 (https://support.allen-heath.com/Knowledgebase/Article/View/using-stream-deck-with-dlive). You would just need to use the IP address of your SQ and the messages shown in the MIDI Protocol Document here (https://www.allen-heath.com/media/SQ-MIDI-Protocol-Issue1.pdf).

    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]

    Cheers!
    Keith.

    #89324

    In reply to: Midi for scenes

    Profile photo of Nicola A&H
    Nicola A&H
    Keymaster

    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
    Keymaster

    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: https://www.allen-heath.com/media/DAW-Control-Help-V1.7.pdf#page=5

    It may also be worth having a look at the Qu MIDI protocol here: https://www.allen-heath.com/media/Qu_MIDI_Protocol_V1.9.pdf

    Thanks!
    Alex

    #88716
    Profile photo of KeithJ A&H
    KeithJ A&H
    Moderator

    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. (https://www.allen-heath.com/everything-io/).
    – 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.
    Cheers!
    Keith.

    #88112
    Profile photo of
    Anonymous

    Use Method #1.
    https://www.waves.com/support/how-to-control-multirack-with-midi

    No custom MIDI required. The dLive spits out a MIDI PC message that should match the Waves MIDI format on Scene change.
    https://www.allen-heath.com/media/dLive-MIDI-TCP-Protocol-1.50.pdf

    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.

    #87893

    In reply to: QU-32 Mute button

    Profile photo of Alex A&H
    Alex A&H
    Keymaster

    Hi Thomas,

    You can find how the Qu uses MIDI here: https://www.allen-heath.com/media/Qu_MIDI_Protocol_V1.9.pdf

    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: https://www.youtube.com/watch?v=Lgk9xbsqxsA

    Alex

Viewing 15 results - 46 through 60 (of 221 total)