rededfred2010 Posted March 9 Share Posted March 9 Does anyone know why Logic Pro 10.8 cannot be installed on Monterey? What is it that stops it from being installed? Is there a way round it? I want to upgrade but have too many other apps & plugins that will not work with more recent MacOS's. Quote Link to comment Share on other sites More sharing options...
des99 Posted March 9 Share Posted March 9 27 minutes ago, rededfred2010 said: Does anyone know why Logic Pro 10.8 cannot be installed on Monterey? Because it requires Ventura as a minimum. 27 minutes ago, rededfred2010 said: What is it that stops it from being installed? The macOS libraries the software is built for and compiled against. 27 minutes ago, rededfred2010 said: Is there a way round it? Nope. 28 minutes ago, rededfred2010 said: I want to upgrade but have too many other apps & plugins that will not work with more recent MacOS's. Then you have a choice to make as to what software is most important, or have a dual-boot with both macOS versions installed. Quote Link to comment Share on other sites More sharing options...
rededfred2010 Posted March 9 Author Share Posted March 9 (edited) Thanks Des. Are you saying that Logic 10.8 is a completely rewritten piece of software vs 10.7.9 or has Apple put measures in place to stop it working? Edited March 9 by rededfred2010 mistake Quote Link to comment Share on other sites More sharing options...
Solution des99 Posted March 10 Solution Share Posted March 10 5 minutes ago, rededfred2010 said: Are you saying that Logic 10.8 is a completely rewritten piece of software vs 10.7.9 or has Apple put measures in place to stop it working? Neither. When you write software, you choose what frameworks to build against. If you build against older frameworks, you often cannot use OS features that exist, or have been improved in more recent frameworks. Or you have to rewrite working code to handle the differences in macOS frameworks, or can't take advantage of bug fixes in the system etc. Or perhaps an older way of doing somewthing has been deprecated, so you have to change how the code works using the old way, versus the new way, and if you continue to support older macOS versions and have customers running on both systems, you now have to develop and maintain different code that works on either system. It's a choice, but it's a delicate balancing act between what you want to do in the app, and the cost of having it continue to work and the development required to do so - and it's often quite a complex calculation. And being Apple software, the Logic team are mandated to a certain extent to support modern/recent features of macOS, and to do that, they often have to build against more recent frameworks, at the cost of backwards compatibility. The bottom line is, these decisions are not arbitrary, you usually choose to move your minimum requirements forward because certain things your app needs require it. And those decisions are certainly not made because the developers just want to stop people upgrading, or because the Logic team want to try to force people to buy new hardware (despite what the conspiracy theorists will say). Developers usually want to try to support the largest amount of userbase possible, but that comes with a cost that can't be born by the developers forever. If you can't move forward at this time, your current existing version of Logic will continue to work fine on your existing system. 1 Quote Link to comment Share on other sites More sharing options...
rededfred2010 Posted March 10 Author Share Posted March 10 13 minutes ago, des99 said: Neither. When you write software, you choose what frameworks to build against. If you build against older frameworks, you often cannot use OS features that exist, or have been improved in more recent frameworks. Or you have to rewrite working code to handle the differences in macOS frameworks, or can't take advantage of bug fixes in the system etc. Or perhaps an older way of doing somewthing has been deprecated, so you have to change how the code works using the old way, versus the new way, and if you continue to support older macOS versions and have customers running on both systems, you now have to develop and maintain different code that works on either system. It's a choice, but it's a delicate balancing act between what you want to do in the app, and the cost of having it continue to work and the development required to do so - and it's often quite a complex calculation. And being Apple software, the Logic team are mandated to a certain extent to support modern/recent features of macOS, and to do that, they often have to build against more recent frameworks, at the cost of backwards compatibility. The bottom line is, these decisions are not arbitrary, you usually choose to move your minimum requirements forward because certain things your app needs require it. And those decisions are certainly not made because the developers just want to stop people upgrading, or because the Logic team want to try to force people to buy new hardware (despite what the conspiracy theorists will say). Developers usually want to try to support the largest amount of userbase possible, but that comes with a cost that can't be born by the developers forever. If you can't move forward at this time, your current existing version of Logic will continue to work fine on your existing system. Thanks again Des. That makes a lot of sense & will save me from pulling out more hair. Cheers. 1 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.