The New Shiny and a Little Temprament…

(Image from wallpaper cave.com)

Hi everyone!

Sorry it’s been a bit since some rambling on here – Summertime is always the busiest around APITEland and EduCorp®. Things should get even busier as the Holidaze® get closer… 🙂

So The Mothership® showed off a bunch of new Shiny Shiny this past week as they do every September. Hope all your Credit Cards (or that Shiny Shiny new AppleCard) are paid down and ready for the onslaught. Still not sure what I’m going to get (do I *really* need anything new?) but that’s not what I want to talk about this go ‘round anyway.

We need to talk Computer Updates and the next big one from the Kids in Cupertino.

Back in the days when an Operating System update was way more than a year between changes and came on something called a CD-ROM or (heaven forbid) a Floppy Disc, the Technorati (and anyone else who actually liked to get work done on their machine) had a simple plan – never upgrade a ‘Mission Critical’ computer.

You might have a ‘secondary’ machine that you would test a new update on (Operating System or even Application!) and if it passed muster, didn’t crash, and added something that you didn’t already have (or really wanted) then you would take the plunge and install it on your main system(s). If you weren’t blessed with a ‘Testbed’ Computer, then you scoured the Trade Mags for info and talked with other users about their experience to see if it was worth installing or not. But sometimes you just had to take the plunge because you really, really wanted some new feature that was available.

And every time I did the last thing I always got bitten where the sun doesn’t shine…

I’m telling you this as a bit of a warning, since I’ve been testing the latest MacOS (10.15, a.k.a ‘Catalina’).

If you’re doing Music Creation or Production you seriously need to wait a bit before upgrading your main machine.

Let me say that one more time: Don’t upgrade to Catalina when it’s first released in October!

But why?

The 64-bit requirement is probably the biggest issue.

“A-ha!” You might say. “All of my software has been 64-bit compatible for years! I’m taking the plunge…”

I thought that too – and then I did a bit of digging…

You see, even though the software might be 64-bit compatible some of the embedded libraries it relies on are still 32-bit.

I’ve seen this in nearly every DAW I’ve checked and many other music/media Apps too. The culprits are usually Propellerheads’ ReWire or QuickTime-related, but there are others too…

And until they are updated or worked around, NONE of them will function properly in 10.15.

Some examples: As of this writing ProTools won’t even launch on any of my machines running Catalina. Ableton dropped a note saying that Live 9 is not and will never be 10.15 compatible (meaning you’ll have to upgrade to 10 when they get the fix done for it). Reaper seems stable but I’ve had issues I’ve never seen before. I’ve read blurbs from many other Music Software companies with similar problems running 10.15.

Some further lurking revealed that Apple’s own Final Cut Pro, Motion, Numbers, Pages, and Keynote are still showing incompatibility with Catalina! These will be fixed before launch certainly, but talk about waiting until the last minute…

What about Plugins?

Again, most are 64-bit ready, but several on my system are not. I’m not a Code Junkie, so all I can really assess are the ones that have companion Standalone apps. All are 10.15-incompatible on my setups. I will say that most without Standalone Apps seems to work as normal though.

But that leads us to Installer Apps. None of them are 64-bit ready on any of my systems (this goes for the Uninstallers too). Izotope shows Dialog Box after Dialog Box of warnings when you try to install a plugin, ultimately leading to Catalina saying is wasn’t installed properly. I tried Eventide, Korg, and Valhalla as well – only Valhalla would actually install without issue. Go Sean! 🙂

So will Plugins already installed on a pre-Catalina System update just fine? I’m running a clean installation of 10.15 in a Container so I can’t say at this point. I will be upgrading one of my ‘less critical’ machines from Mojave to Catalina, so I’ll update you with what happens when the official release comes out.

But as Han Solo would say, “I’ve got a bad feeling about this…”

It’s been about a decade since I’ve warned people about updating a Mac OS, and since those issues were resolved a few months later I’ve never hesitated in telling anyone to go ahead and install the latest version. This will happen again very soon, so don’t worry about sitting on the sidelines for a bit.

Until next time…

Just as a disclaimer: my intention is NOT to panic anyone out there with this post – it’s merely my own observations with some age-old wisdom attached. I’m certain MacOS 10.15 is going to be a powerhouse when it’s ready for Prime Time – the functions and security are setting the pace for OS’es to come in the next decade.

But I have decided I’m not going to upgrade any of my Macs that I actually need to do work on, and I’m recommending that you don’t either if you’re in the Music and/or Media Production Industries. I’m lucky enough to have a Testbed Machine that I will keep checking upoming updates (both OS and Apps) on, but until everything I need is ready and working as it should I’m happy to stay put on 10.14. Apple doesn’t force anyone to upgrade, and going Bleeding Edge just because it’s the new Shiny Shiny is not worth losing work (and money) over! These issues will get resolved, and for all I know everything might be perfect by the time I hit ‘Publish’… If that does magically happen, I’ll provide an update to this post. 🙂

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s