The list of new features and improvements in version 1.6 is impressive! There are some really exciting additions that I’m looking forward to exploring. However, I’m a bit hesitant to update our SQ7 mixing console right away, as feature releases are sometimes followed by bug fixes. For now, our console is still running version 1.5.
Smartphones, on the other hand, typically update apps automatically. This evening, I had four musicians whose phones had already updated to SQ4You 1.6. As a result, they were suddenly unable to connect to the mixing console because SQ4You 1.6 appears to be incompatible with an SQ7 still running version 1.5.
Honestly, I find this quite frustrating. It seems like an issue that could have been prevented, yet it unexpectedly caused a problem during our session. In the future, it would be helpful if app updates maintained backward compatibility for at least one previous firmware version or if users were given a clear warning before updating, ensuring they don’t lose functionality unexpectedly.
I have the same issue, I had 5 of our 8 iPads update overnight so they would not work this morning.
So today updated the console. Now 2 of my older iPads (iPad Air 1) will not run it at all since SQ4You needs iOs13 and they can not upgrade past iOs 12. There are ways around this, but this having people use their phones and whatnot. But I had a fully functioning system yesterday and now I need to buy 2 new/used iPads.
Mind you I have been doing some playing around w/ 1.6 and I like the upgrades. I just wish I had the choose of when to implement it.
Same issue here… we were about to start rehearsal last night before youth service and suddenly lost all remote control including with MixPad. Horrible timing. Needs fixed.
On the Iphone you can chose how your app is update, automaticly or manualy. All my Ipad who is using an Audio APP are on manualy. is the best way to prevent version issue.
Glad that I have auto update turned off on all devices. It’s just too dangerous. This issue is not limited to A&H or Apple products.
Fun fact: IOS 15 has broken MIDI support, and most people either have IOS 12 with working MIDI, or IOS 15 on middle-aged iPads. But MIDI wasn’t fixed until IOS 17 which won’t run on middle-aged devices. So this unfortunate combination will now lead people who wanted to use SQ4You and some MIDI something on their iPad to having to buy a rather recent iPad which is expensive.
Me & myself, I’m still in IOS for the old QuControl app, otherwise I’d be on Android.
You can use MixingStation on IOS 12 still (actually even on IOS 11). It can also connect in SQ4You mode to the mixer. However, re-inventing the SQ4You surface in MixingStation will take some effort.
It’d make a lot of sense for A&H to release a new suite of apps each time they release new firmware (perhaps with the firmware version appended). I know it could get unwieldy with lots of Apps on the stores, but it would mean people wouldn’t get caught out by an automatic update on tablets/phones rendering their devices unable to work with the desk from one day to the next. At least with a new app the firmware on the desk could be updated manually, and people notified that they will need to then download the new app. It’s the disconnect between one thing auto updating and another manually.
Or, of course, maintain backward compatibility within the app!?
There is a topic in the Feature Suggestions section requesting having legacy versions of the Apps available in the App/Play store to avoid such problems.
Can I encourage other users affected to use the vote option to support the request.
The option to vote to support Feature Suggestions available and used by A&H to monitor user support for Feature requests.
(Search for SQ MixPad/SQ4You and was the only result )
Backwards compatability is not too hard to implement so for example Mixpad 1.6 can and should have been made to work with firmware 1.5.
Dropping old iOS support for a minor release is a disgrace. Making hard-working and not necessarily well-paid musicians invest in new hardware to avoid A&H having to invest in the compatibility is not fair. Too much like Microsoft behaviour for my liking.
If older versions are available through some direct links these should be made readily accessible on the download page.
It would be good to see somebody from A&H explaining and defending their position on this.
