I just found out that Cubase 12 is no longer supported on macOS Sequoia, and if any issues arise, Steinberg won’t provide technical support. The software is only 3 years old, and it was released with Apple Silicon compatibility.
Is it just me, or does it seem a little unreasonable that I’d have to pay $200 to update just to keep using it on a new macOS—even though I don’t need any new features? I get that companies need to push new versions, but dropping support this quickly feels off.
What do you guys think? Is this standard practice now?
Problem is that if Apple break compatibility on a supported product with an o/s update then Steinberg are stuck having to recode older version rather than working on new versions.
I guess they just don’t want to guarantee they’ll keep fixing things broken by o/s updates.
My intent isn’t to sound crass, but I’m not sure it matters what we think. In my limited “shipping software” experience, yes, it’s “common” to stop providing support for a sunset codebase beyond the OS it was developed to run on. Being released with “Apple Silicon compatibility” is not the same thing as “supported on future OSs where the developer is powerless to anticipate requirements and code dependancies.” You don’t HAVE to update to Sequoia if you’re concerned about support, and that is (to me) a reasonable response. If you want/need Sequoia, and you want/need to be supported, then you’ll need to upgrade to a supported platform.
which is exactly what I will do. It’s just a bit frustrating because I usually update stuff when I can, and maybe I can get my mac to perform better with a new OS, but if that has to compromise my softwares, I won’t update
I do the same thing. While not strictly a “need,” it’s a decision I’ve made (supported by other factors). In those cases I just approach it with a plan to upgrade and test, and even if unsupported, see if I can work around issues in a reliable manner. I’m typically on the OTHER side - I’m updating my OS and waiting for the software vendors to catch up with support. Worse case is that you can keep C12 running and update, and do what works for you. That’s not as easy to do in a production studio, but at least you can document an approach.
Keep the original os and don’t allow Cupertino to install further os updates (if you desire). Or at least, be in possession of your current os as install media etc if you decide to try os updates in the future and subsequent rollbacks…which of course, Apple tries to roadblock.
Cupertino is notorious (since 1984) for breaking 3rd party software in the course of the Mac os years of evolution.
I understand. I mean it would be all less troublesome if they kept at least support running, which means if I update to the last OS I can at least get some help if there are glitches of some kind, but they don’t.
anyway, thanks for the support, I think I’ll wait a long time before updating, then.
it would be all less troublesome if they kept at least support running, which means if I update to the last OS I can at least get some help if there are glitches of some kind, but they don’t.
From many reports seen here on the forum, they barely manage this with their supported versions so you probably don’t miss much in that respect
