[BUG] Allen & Heath - SQ modules - Slider not released on Fade

[JustAddSoftware]

I’m finding an issue with the Allen & Heath SQ module. In particular we are running an SQ-6. Here’s the issue - if you try to set a “Fader Level to Output” and fading is set to anything other than “Off”, companion grabs that slider and never let’s go. Additionally, if I set Fading to 3 seconds, the fade happens immediately. It’s not 3 seconds for it to go from 0 to wherever I want it to go to. It is instantaneous and then I never have control of my slider until I disable the SQ6 connection. If I don’t set any fading (ie: Off), then things work fine, but I want to fade this output. Maybe I am doing something wrong or not applying this correctly. Happy to report it as a bug but wanted to check first if I am misunderstanding this.

[belac9615]

I'm also experiencing this on an SQ6. The fader will lock at the end of a fade and the only way to release the fader is to quit Companion.

[JustAddSoftware]

The good news is you don't have to quit companion. Just disconnect from the SQ6.

Sadly, it seems the developer of this module is not maintaining it. There are other reports of this same issue that have been out there longer than mine.

[productioneccc]

I'm having an issue where the SQ module will just keep connecting and disconnecting. If I leave it for a day or two, it stabilizes. But once my fader gets stuck like you guys are talking about, I have to turn off and on the module and then it goes back to loses connection.

[JoshDarnIt-All]

Another bump for this issue. Still experiencing this intermittently.

Only solution at the moment is to shutoff and restart the companion module.

[jswalden]

The SQ MIDI protocol level controls consist of messages saying, "set this parameter to this level". There's no grabbing or releasing in any of it. (The "Fading" option, tho, does for nonzero fades result in Companion sending however many messages in succession to set the parameter to successive levels, with no way to cancel the series. But after those 1-3s there's still no control retained at all.)

I haven't noticed this in testing on my own SQ-5, or with the most recent module code. But maybe, once a first release that contains updating to be 3.0-compatible and conversion to TypeScript is out, this can be tested again and it can be figured out who exactly is at fault -- as I don't see how it can be the module at fault (maybe a bug in the SQ MIDI-over-TCP support instead?).