-
Search Results
-
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 07Where “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 07as 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…
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?
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.pdfI’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!
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 > MapsChanging/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/
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 PowerThere 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?