bayswater wrote: ↑Tue Mar 19, 2024 12:28 am
James Steele wrote: ↑Mon Mar 18, 2024 3:55 pm
Again, it may be wishful thinking but I sure wish Apple could devise a way to let us revert to a previous OS version as painlessly as possible. I installed 14.4 because I’m not recording others professionally. If I was, I wouldn’t have done it, of course. It was just sheer luck that because I had an M1 Mac that I dodged this bullet.
I’ve never seen a processor-specific issue like this before. I guess the takeaway is that developers need to test on M2/M3 machines as well. It also makes me wonder about Apple’s beta testing. Is it possible Apple had ZERO beta testers with M2/M3 Macs doing audio work and owning some iLok-protected plug-ins?
I think that was only one developer who didn’t test on M2/3 but yes, that seems pretty obvious that you would test on the machines your customers use.
This morning there were reports that the last developer’s beta did not have all the bugs that are now being reported. If so, another flaw in the QA process, and another reason to wait a few days after any OS update on anything.
Oh yeah... mea culpa! Guilty as charged. As I said, normally I would dive into an OS update like that, but a) I'm not at the critical stage of any project right now, b) I was desperate to find a solution to an issue I was having with DP 11.31, Console 1, and Sonoma 14.3.1. I was hoping 14.4 would fix it. Wrong. And, c) I'm on an M1 so I lucked out and dodge the problem anyway.
Again, yes... in hindsight the developer quoted in the article should have tested on M2 and M3 as well as Intel and M1, but I've never seen an issue like that before where something breaks like that on one CPU variant but not the other. I can't blame them for thinking that if it was working on Intel and on Apple Silicon, that it would break on a different variation of Apple Silicon. Just never saw that before. As a Mac user, I always thought that was something the Windows people dealt with AMD, Intel, Ryzen and whatever. You'd really think that if you tested on Intel and Apple Silicon your bases would be covered. Now we know.
Fortunately for me on this older M1 I'm going along okay, however still waiting for Apple to fix the graphic glitch that's affecting Console 1. Namely, the on screen RTA display and controls in the On Screen Display app get sluggish in DP unless you close all windows except the Track Overview. Royal PITA. Apple kinda needs to get their act together. Seems like a company that's valued at 2.6 TRILLION DOLLARS, could afford to have a bit more robust QC. Seems like they should understand that creatives make up an important portion of their user base, so a company with that much money could afford to have a systems in house that mimic a typical DAW setup with various current common hardware peripherals and third party plugins. Sigh... I dunno.
Lastly, I really do think it would be a selling point if Apple could devise a system to make rolling back macOS to an earlier version easier—especially if their testing is going to be sloppy or they just can't keep up with it. I understand they have all this security now, but Apple taking away the ability to make bootable backup (via apps like Carbon Copy Cloner and Super Duper) kinda sucks... big time.
