It looks like the control network on the SQ is still a bit fragile - I had the console (SQ5) lock up when using MixingStation on a gig recently. Lost network control and also local UI, and pulling the network wasn’t enough to get back operational - I had to power cycle the console (I did not try to replicate the problem, as it cropped up during soundcheck and there wasn’t time before the show, and the console was a rental).
I did check that the unit was running 1.5.11 firmware. MixingStation was whatever was current as of the middle of November, but I was using a custom layout which had group routing buttons for 20 channels to 4 groups plus main L/R. Network connectivity was via WiFi, but the access point was under 1m from the tablet so very good (maybe even excessive) signal strength.
Anybody else seen these sorts of issues on recent firmware? Any better approaches to having a matrix of group assign buttons? The console group assignment methods are a bit clunky for my application (I need to flip some inputs between different processing groups on a song-by-song basis, and sometimes within a song).
An update on this with additional information. Maybe this is a better fit for an email to A+H support, but I’m not sure what support would be able to do beyond passing the information on to the development team. Happy to share the MixingStation layout if that’s helpful.
Saw the same issue in a different venue yesterday (same console and WAP), but noticed that both SQ MixPad and MixingStation (latest versions of both tools as of yesterday, older iPad on iOS 15.8.3) were seeing random dropout/reconnect cycles on a pretty regular basis. Signal strength was fine, though. I suspect that there was some interaction between the facility WiFi and my network that was resulting in the dropouts. System was working properly (except for the random dropouts) for over an hour of sporadic iPad use before getting hit with the lockup.
As before, MixingStation was hung in a “reconnecting” state, and the console (SQ5) local UI was completely hung - meters frozen, no response to buttons, touchscreen display frozen. Pulling the network cable made no difference. Power-cycling the console restored things to normal operation (I left the WAP disconnected). My suspicion here is that the network connectivity got interrupted in the middle of some state update transaction, leaving the system blocked and waiting for a packet that was never going to come.
This issue is very unfortunate for a few reasons - first is that the pops through speakers during the power cycle were clearly audible. Yes, I know “amps last on/first off”, but when the PA is powered speakers and the console is hung, running up to the stage to pull power from wedges and mains, or unpatching/repatching all console outputs is a worse option than letting the power transient hit the limiters. Second, and perhaps more serious, is that it makes the SQ-Rack a non-starter until the network control is reliable - having to restart the console during a show is an excellent way to lose a client, and not a risk that many are willing to take. I have an application that the SQ-Rack would be a very good fit for, but am looking at alternatives due to the network reliability issues.