Greetings list!
I have tried unsuccessfully to get the A&H TCP MIDI Driver to connect to the QU-32. It’s difficult to find any documentation on this little app, and it is also only in its 1.0.0. version.
Has anyone been successful with using this driver? I try to connect but it never confirms a connection — just hangs on “connecting…”
Following this, I made various attempts to connect to the mixer using the documented sysex messages using python or node.js, and ran various packet sniffers in the terminal & processing in case I could catch any transmitted data, yet there is no indication of a response from the mixer.
Here’s what I tried:
I wrote basic TCP client scripts in Python and node.js. I confirmed that these work, using the localhost, then edited them to use the mixer’s IP address and Port (192.168.1.60 and 51325). I ran many versions of these from the command line. For the most part, the hex I’m attempting to send is the “Get System State” message on page 9 of the QU-MIDI-Protocol document
https://www.allen-heath.com/media/Qu-MIDI-Protocol-V1.82.pdf
Each time, the client timed out.
I’ve attempted each change in code by running on different machines — Mac Pro, Mac Mini (El Capitan), and MacBook Pro (Yosemite) — and using the wireless router connected to the network and also by going straight from the mixer’s “network” port to the computers’ ethernet port.
I’m also wondering if it has anything to do with the “Active Sensing” byte as mentioned on page 9 — HUI protocol has a similar message, a ping sent to the DAW and back. I’ve sent the sysex message (start, header, active sensing byte, end byte) to no avail.
Any suggestions or thoughts addressing this would be very helpful. Thanks!
.
