![]() ![]() I made the jump to 64-bit Live (which does not support 32-bit plugins without aforementioned third-party solutions) several years ago and it didn't take me long at all a.) to decide that active developers who do not update things to 64-bit deserve most of the blame for it and b.) to decide that most older/unsupported things that would require compatibility software aren't worth it. Will any of the existing third-party 32-bit bridge solutions work? I have a decade's worth of Ableton Live projects, depending on a decade's worth of plugins, some of which will never be updated to 64-bit* Posted by Merus at 2:17 PM on Octoįor anyone using music software, this is a huge headache. Now, this has meant that Windows has a backwards-compatibility shim that lets the very first version of SimCity use different rules for memory allocation, but it's also meant that games and apps from the last decade still work on the latest version of the operating system. They're going to get a refund on Windows. One of the more well-known members of the Windows team explained their reasoning: if a new version of Windows breaks backwards compatibility because an app is doing something it shouldn't, the user can't get a refund on their old app that works in the old version. Microsoft can't do this kind of thing because they sell software, not hardware. It's not surprising - Apple have never, ever cared about backwards compatibility, and there's countless examples of important and useful applications throughout the history of Macs and iPhones falling by the wayside because Apple changed something and expected everyone to do a huge amount of work to keep up - but it still sucks. * reFX, makers of QuadraSid/Slayer/Vanguard, have told users of their old plugins to go whistle, while other plug-ins, including things like AAS Strum, were replaced by improved versions which are not preset-compatible and cannot import the previous versions' settings. Of course, all this will be repeated in a year or two's time when Apple make the move from x86-64 to ARM. I hope that they bring ones with less sucky keyboards out soon. Of course, given that I also write code for iOS/macOS, I'm going to have to move to Catalina at some point, which I'm guessing brings forward the next MacBook purchase. I've spent much of my tooling-about-in-Live time this year going through old sets, seeing what I can salvage, what can be mixed down to audio stems, what can be turned into a workable Drum Rack/Sampler instrument, what can be replicated (reFX Vanguard patches are very hard if not impossible to replicate with other synths), and come to the conclusion that, for the purposes of being able to access old projects, my existing MacBook stays on 10.14 (and, eventually, will join my MacOS Classic Titanium PowerBook and OSX/PPC PowerBook in the old-laptop cupboard). I have a decade's worth of Ableton Live projects, depending on a decade's worth of plugins, some of which will never be updated to 64-bit*. For anyone using music software, this is a huge headache. ![]()
0 Comments
Leave a Reply. |