search

bitfocus / companion-module-allenheath-sq

MIT License
7 stars 3 forks source link

midi error: write econnreset - When using Allen and Heath MIDI Control Software #50

Open jhull88 opened 5 months ago

jhull88 commented 5 months ago

Hi Team,

Have my SQ5 hooked up via network to computer. I am able connect just fine (connections - add connections...) and Companion is able to talk to the SQ5. However, Companion does not work when I am also using the Allen and Heath MIDI Control Software.

Steps to reproduce error.

  1. Connect Allen and Heath MIDI control software (ex. MIDI Channel 1, CC Tranaslator, TCP/IP )
  2. Add Connection, Allen Heath, SQ5 (Click save)
  3. The 'Status' Column in the 'Connections' tab is flashing between green check mark (Connected) and 'ERROR write ECONNRESET'

If i look at the debug log it says 'error: midi error: write econnreset' over and over...

Ideally I'd like the SQ5 to connect to a computer with lighting console software via MIDI (over network TCP/IP), so I can use the faders to control the software and the lights I have connected to the software. Adding Companion, I was planning to have Companion talk to the SQ5 so I could effectively remote control the SQ5.

Is there something I'm missing?

Appreciate the help!

jswalden commented 5 months ago

I can observe a similar thing just having two Companion instances at once both try to connect to the same mixer. (One is the actual one I use, the other is the local build I use for module coding, basically.)

My assumption -- it's only an assumption! -- is that the SQ5 (and probably 6 and 7?) only supports a single MIDI connection (or maybe just MIDI over TCP?) at a time. Once you burn it on the MIDI Control Software (or on one Companion instance), you won't be able to connect a(nother) Companion instance that internally requires MIDI over TCP to work.

If you're motivated enough to ask whether it's possible to have multiple connections at once on the Allen & Heath forums, I'd love to know what you hear back. But my best guess without having asked (I've been too lazy to get around to it) is that this is an inherent limitation of the mixer and neither Companion nor this module can fix it. (Short of some highly involved work reverse-engineering the SQ Mixer/SQ4You protocol and reimplementing this module in terms of it, which I doubt will ever happen.)