Search Results for 'qu midi protocol'

Forums Forums Search Search Results for 'qu midi protocol'

Viewing 15 results - 61 through 75 (of 198 total)
  • Author
    Search Results
  • #69074
    Profile photo of Vanceg
    Vanceg
    Participant

    I understand that DAW control on the SQ series is “In Development”. I’d like to know a few things about what to expect on DAW control So that I might determine which of my customers might benefit from it and how I can help them integrate the SQ into their workflow.

    Can anyone here point me to a manual or general description of how DAW control will function on the SQ series?
    Here are a few specific questions that I’d like to have answer for if anyone knows.

    – I understand (from another post on the forum) that the DAW control will operate through the use of “MIDI STRIPS” which can be assigned to any layer/bank we wish. I hear that there will be up to 32 of these strips. Is this accurate and do all versions of the SQ consoles have the same 32 channel capability?

    – What control protocol does the DAW control utilize? Mackie Control? HUI? ICON? Custom/Proprietary?

    – If it uses Mackie Protocol, will the SQ series support more than one 8 channel bank of control at a time (Some other digital consoles only support 8 channels of Mackie control at a time… and that’s not useful for our needs).

    – Can you confirm that scribble strip information is transferred from the DAW to the SQ? (will scribble strips work)

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

    Hi Nakul,

    Have you followed this instructions in our DAW Control Setup document?

    Here are the steps for Ableton:

    1.Select the Mackie Control protocol in the DAW Control paneland launch Live.
    2.Open the Live / Preferences window and navigate to the MIDI/Synctab.
    3.Select MackieControl in the Control Surface #1 dropdown box, and set DAW Control MIDI 1 as the Input and Output port.
    4.For each consequent block of 8 MIDI strips present on the mixer, create a Mackie Control Extender device and assign it to the corresponding MIDI port. The following example assumes 16 MIDI strips are used:
    a.Select MackieControlXT in the Control Surface #2 dropdown box, and set DAW Control MIDI 2 as the Input and Output port.
    5.Close the window

    Thanks!

    Alex

    Profile photo of Frank
    Frank
    Participant

    I am sorry, because I think, my questions are the same like a lot of other people had, but I don’t understand this hundreds of articles and tutorials about recording to QU-drive, into DAW, with MIDI-protocols and so on and so on…

    Would it be possible to get a clear step by step manual, what I have to do for this task, with the A&H Qu16:

    I want to record a selection of 16 Channels plus stereo-channel 17+18 (my Keyboard) into Cubase 9.5 Elements AND want to playback at the same time a additional track in Cubase, where I importet an mp3-playback.

    What I have to do? Step by step?

    I also experimented with MIDI-connection to Cubase, but have a lot of problems with this also (I get strange tracks, no wave-picture, only vertical stripes and don’t know, how to include the stereo-channel 17+18…). So perhaps it would be easier for the first to record with USB-B to the DAW without MIDI-control (I don’T know?).

    Perhaps I could record also to an USB-harddisk, an play the playback from Cubase and the copy the tracks from the harddisk to Cubase, but it would be nicer to record directly into the DAW…

    At which channel must be the playback from the PC, not to disturb the recording? And is it possible to leave the keyboard on channel 17+18 ST1?

    I hope anybody has mercy with me, an absolute beginner on QU16 and Cubase and can tell me in easy words, what I have to do (my englisch is not perferct, but it wioll be possible with a dictionary 🙂

    #65778

    In reply to: QU-16 Editor?

    Profile photo of Ryan
    Ryan
    Participant

    Couldn’t an offline editor basically be something similar to the QU-Pad app that just stores all the settings to a file as midi commands, then when connected to the board, you just dump the file to the board? The board doesn’t care how the commands are received, whether live from an app or sequentially from a file.

    There are limitations to what settings can be changed with midi. The Qu-Pad app uses a custom protocol to transfer settings/control the mixer.

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

    I’m pleased to say that the new V1.2 firmware for Bome’s BomeBox supports Allen & Heath dLive, GLD and Qu mixers over a network connection.
    The BomeBox can be used to interface dLive’s TCP Protocol <-> 5-pin MIDI.
    Have fun!

    #64700
    Profile photo of agustinvolpe
    agustinvolpe
    Participant

    in the midi protocol manual> “Qu uses Bank Select and Program Change messages for Scene recall. Only Bank 1 is used.”
    So, can I set up a number of scenes with the iPad, and then directly change between those scenes using normal program changes?
    What do I need to set NRPN for?

    #63875

    In reply to: QU 16 Power Off/ On

    Profile photo of Andreas
    Andreas
    Moderator

    At least powering down the Mixer could be automated using the proper MIDI Sequence (see “Remote Shutdown” in Qu MIDI Protocol). All you need is a tiny tool which is started when the PC enters its shutdown sequence, connects to the Desk and sends the MIDI command. Could be done through network or USB. Sending a fixed data packet to a fixed IP address shouldn’t be too complicated to implement.

    #63766
    Profile photo of MikeShand
    MikeShand
    Participant

    I’m somewhat puzzled by the midi messages I am seeing. I have midi control set to 1.

    When I move a midi strip fader is see messages that appear to be channel 2 e.g. B1 00 16 which since midi channels are encoded as 1 = 0 2= 1 etc. Seems to be channel 2.

    Doc says:-

    MIDI channel number
    N
    MIDIchannel 1to16 = 0toF

    I notice that the QU midi protocol doc says that daw control uses midi channel + 1 . So does the GLD also do this, although it is not documented?

    My other puzzle is that I see messages on channel 1 such as

    B0 00 03
    C0 6E
    B0 63 10

    The latter appears to be sent fairly frequently, but apparently at random. What are they? They appear to be an NRPN MSB selecting Channel hex 10, but there is nothing following them, e.g. The expected LSB parameter etc. So what are these, and why are they being generated. I’m just ignoring them, but I’d like to know what they are for.

    Is there an updated midi spec for gld v1.51 that might explain these. As far I can see nothing in that area is supposed to have changed since 1.4 which introduced the midi strips.

    Puzzled!

    #63678
    Profile photo of Chuck
    Chuck
    Participant

    I know it’s me but I still need help. I downloaded the drivers and installed them on my computer. I went to setup and set all sixteen channels of the custom layer to MIDI. I plugged the QU into the computer via the USB B. I started the A&H application and the window popped up. In the window it shows mixer as QU, MIDI channel 2, protocol Mackie, MIDI port has the dot, but…nothing is available for the input port and the only thing on the output port is blank or Windows.

    I have uninstalled and reinstalled the DAW software; undone, powered off and redone the settings in the QU16, reconnected and tried again. And again. Can anyone shine a light one what I am doing wrong?

    Thanks
    Chuck

    #63620
    Profile photo of Roel88
    Roel88
    Participant

    Hi Guys,

    Since this week I’m the owner of a C3500/CDM48 setup, and its amazing! But there is one thing I can’t figure out.

    Because I’m going to use the setup in theatre shows, I really need a good midi connection between the surface and Qlab. I know the basics in midi programming, but not the HEX part.

    I already managed to program soft keys for Qlab triggers, so I can trigger a Que from the C3500 surface.

    My problem is the other way around…I want to program a MidiQue in Qlab, witch recalls a specific scene in the DLive. I think it should be a SysEx message, but when I choose that option, my MidiQue immediately gets a red cross.

    Who can help me out…I already looked in the GLD/DLive Midi protocol pages…but I really don’t know witch code I have to put on witch place…

    Thanks in advance!
    Roel

    #63312

    In reply to: Start App Programming

    Profile photo of DanZ
    DanZ
    Participant

    Thank you Andreas for the new version

    It is with the Get System State Sysex message. I receive then tons of NRPN and 56h is one of them. (Maybe my parser error? I don’t think all is documented)

    I am using .net and don’t know to program with c++ juce and multi platform…
    So at last we will have a nice QU program for windows

    While decoding this huge nrpn stream, I now understand a lot more my QU mixer and it is full of options 🙂

    I only dream about having the AB168 extension for the QU-PAC so my program will really shine 🙂

    With my app, it will be so much easy to mix but
    Not sure if QU MIDI protocol can be as fast as the one used by the QUPAD app
    Maybe the QUPAD app allow to have a better resolution than 0-127 for the faders?

    So still have to find the 56h…

    #63311

    In reply to: Start App Programming

    Profile photo of Andreas
    Andreas
    Moderator

    Well, latest version is here: Qu Mixer MIDI Protocol – Firmware V1.9+. NRPN ID 56h isn’t documented there either. When does this occur?
    I guess there are several people very interested to have remote capability on a “regular” computer. If you’re right at a start I’d highly recommend to use some multi-platform environment like JUCE and not only focus on Windows.
    A clever approach would include an offline version to, at least, name and pair channels with possibility to send that configuration to the desk later (when in reach).

    Profile photo of Austin
    Austin
    Participant

    Hi,

    I’m new here, I’m having a bit of a hard time interpreting the data sent back from the Qu-16 model. The protocol is 1.82 and after looking at the pdf it mentions how the data is encoded/decoded. If I understand correctly:

    -Every 8 bytes must be unpacked into 7 bytes.
    -2 bytes (16 unsigned bits) are used to decode a single float (db).

    My questions:

    -The meter data is in dB, but the meter is in dBu’s, am I missing something here? db dBu conversions is impossible if I’m understood correctly
    -The amount of data as you’ll see in the log varies everytime, why is this? If the transmission order is correct I don’t see how this would make any sense.
    -How do I get the db for the meter? (picture attached)

    I attached a more technical detailed log of what is happening. The audio is a sample of constant volume.

    Here the technical log. (Mediafire) (4.25mb)

    Any help is appreciated. Maybe I missed another forum topic regarding this…

    The protocol I’m refering to: http://www.allen-heath.com/media/Qu-MIDI-Protocol-V1.82.pdf

    Thanks,
    Austin

    Attachments:
    You must be logged in to view attached files.
    #62424
    Profile photo of davidgiga1993
    davidgiga1993
    Participant

    Hi,

    as already mentioned it does work with 1.9. But there are quite some things which are not supported
    due to protocol limitations.

    This is also the reason why there is no update recently. My plan for the future is to implement the iPad protocol which allows access to all parameters but
    there is no documentation for it available so it takes quite some time to reverse engineer everything.
    Also it seems like the iPad protocol has much less bugs than the midi protocol.

    OT: Why the hell is the A&H forum still running on http and not https?
    It’s 2017 and certs do not cost anything. Also wpengine (where this page is hosted) can integrate tls for free.

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

    No, in this instance ‘3rd party controllers’ refers to Crestron, AMX or similar control systems that can send/receive custom messages over TCP/IP. One typical application is the integration with other equipment such as light, video etc.
    The details of the TCP/IP protocol will be published with firmware V1.5 but for anyone interested, the GLD MIDI TCP protocol offers a good starting point for simple Scene recall or input level / mute control.

Viewing 15 results - 61 through 75 (of 198 total)