You might still be able to get Big Sur running on your Mac Mini. I have Monterey running on a 2008 MacPro.t *requires* OS/X 11.x. Well, I think that means it won't run on my Mac Mini (and lots of other perfectly serviceable hardware) at all. Hopefully, support for Q4 will continue.
Indeed, I would have to say try it and see what works. There are post OS installation patches that are included with the software for unsupported graphics on many Macs. There are some limitations, however. You would have to look at the guide for your Mac model.Since the new version uses Metal for graphics (at least for video cues) you might struggle with making those work with unsupported graphics cards.
I don't have a dog in the fight but I think that is a more than fair place to draw the line. With the reasonable cost of the software and updates I don't think it is too much to ask of users to have hardware from the current decade.ultimately you have to draw a line somewhere, right? with macOS 11, the line gets drawn at Macs that are eight years old or older. we feel that's as reasonable a line as any.
we will continue to support QLab 4 for quite a while.
the decision to have QLab 5 require macOS 11 or newer is based on longevity and on API features of macOS.
the longevity angle is this: supporting a version of macOS longer than apple themselves supporting it can be a serious challenge. some fixes to QLab 4 have been very difficult to build because we have to keep supporting macOS 10.10, so starting with the newest version of macOS possible gives us a head start against this sort of issue in four or five years' time. we decided NOT to require macOS 12, even though that was the current version of macOS when we released QLab 5, in the hopes of minimizing the number of folks with older Macs that we'd be boxing out.
ultimately you have to draw a line somewhere, right? with macOS 11, the line gets drawn at Macs that are eight years old or older. we feel that's as reasonable a line as any.
I've got multiple installations of QLab 5 running some Halloween attractions and have had no issues with reliability. And there's some very welcome changes, like Mic cues allowing for separate input and output patches, or the changes to icons for groups operating in different modes. Also having OSC cues that have built in commands for devices are pretty neat. It drastically simplified automating mixing with an X32 rack.A production company turned up to our venue yesterday with version 5. We all gasped and the PM asked why. We said it was only released in the last little while and we were all waiting for a bit until it settles and the bugs are exposed and fixed. Her response was "I guess we will be the test case then"
I went home before the show. I guess it worked
When you stop supporting 4, I will have to run it barefoot until I can replace the machines. Or stop using it at all. So before then, presumably, I will have to put a permanent license on it instead of renting -- since I assume part of "EOS" is "we won't rent you licenses for it anymore either".... right?
Does Qlab phone home at all with a census of what hardware and OS it's running on?
What percentage of installs, free and licensed, are in the same boat as us?
And those financial constraints go both ways. Building software for a wide range of hardware, in a situation where failure is unacceptable, is expensive and time consuming.[ For some reason, I tend to catch a fair amount of $EXPLETIVE on here for the financial constraints that being part of a state college imposes on me -- yes, I can still say that with a straight face in the same paragraph with "$95K refit of our black box"; sorry, but that -- as Uncle Walter used to say -- is the way it is. ]
I've been a developer since about 1983, I'm not at all uncognizant of that fact.And those financial constraints go both ways. Building software for a wide range of hardware, in a situation where failure is unacceptable, is expensive and time consuming.
You get flack because of the lack of understanding that those constraints go both ways.