Live data from Hacker News

macOS 11 (Big Sur) Compatibility News

support.native-instruments.com

61–70 of 72 posts

Re: macOS 11 (Big Sur) Compatibility News

#61

What this shows you is that it has become financially unviable for pro audio companies to support Apple. [1] is practically the same announcement by Avid Pro Tools, which is the standard for Hollywood movie production. I also have a personal stake in this, because I used to sell pro audio software, including things that integrate with Pro Tools and OS X. We saw the writing on the wall around OS X 10.11 when major stu…

Thanks for valuable information. I am planning to make a little home studio for me and my friends, would you be so kind to give me advice in which DAW to invest my time, and what are alternatives on linux regarding support of thunderbolt or usb interfaces. Is windows the only future-proof and viable option for producing music nowadays? Thanks in advance.

Re: macOS 11 (Big Sur) Compatibility News

#63
post #32

Earlier quoted context omitted.

Sounds like a nightmare, I guess SANE is an ironic name?

IIUC, that example seems more like an indictment of the scanner manufacturers, not the developers of SANE. SANE includes that code because some manufacturers didn't implement such a simple, obvious, and crucial constraint in the hardware. Unless maybe the poster's point was that the SANE developers shouldn't try to support such fundamentally broken hardware?

I didn't mean to suggest that SANE was a poor project, I guess I just supposed it was sort of gallows humor from developers working on a hard problem.

Re: macOS 11 (Big Sur) Compatibility News

#64
I make music, and I have to say, the jump to 64 bit and the jump to macOS 11 have been pretty damaging to my workflow in the short term. My DAW, my drivers, and my plugins are all written by different developers and they all need to update for me to get fully back to work (In fairness, I made the mistake of upgrading eagerly to macOS 11, which is on me).

At the same time, working on a Mac in general has been so, so much more reliable than working on windows. I used to have endless problems with dropouts or latency problems on windows, regardless of the driver, sound card, or buffer size I used. I’m sure things have improved in the time since, but I’ve been so much happier making music on the Mac. I’ve used my 2013 laptop at plenty of live shows and haven’t had any sort of problem yet. We’ll see what happens in the next year, but I’m not ready to count macOS out as an audio workstation OS.

Re: macOS 11 (Big Sur) Compatibility News

#65

I make music, and I have to say, the jump to 64 bit and the jump to macOS 11 have been pretty damaging to my workflow in the short term. My DAW, my drivers, and my plugins are all written by different developers and they all need to update for me to get fully back to work (In fairness, I made the mistake of upgrading eagerly to macOS 11, which is on me). At the same time, working on a Mac in general has been so, so m…

> I make music, and I have to say, the jump to 64 bit and the jump to macOS 11 have been pretty damaging to my workflow in the short term. My DAW, my drivers, and my plugins are all written by different developers and they all need to update for me to get fully back to work (In fairness, I made the mistake of upgrading eagerly to macOS 11, which is on me).

Apple doesn't care because they'll still get their $99/year from developers and their App Store is almost infinitely profitable.

Re: macOS 11 (Big Sur) Compatibility News

#66

I make music, and I have to say, the jump to 64 bit and the jump to macOS 11 have been pretty damaging to my workflow in the short term. My DAW, my drivers, and my plugins are all written by different developers and they all need to update for me to get fully back to work (In fairness, I made the mistake of upgrading eagerly to macOS 11, which is on me). At the same time, working on a Mac in general has been so, so m…

> I make music, and I have to say, the jump to 64 bit and the jump to macOS 11 have been pretty damaging to my workflow in the short term. My DAW, my drivers, and my plugins are all written by different developers and they all need to update for me to get fully back to work (In fairness, I made the mistake of upgrading eagerly to macOS 11, which is on me). Apple doesn't care because they'll still get their $99/year f…

None of the plugins or pieces of software I use had to be installed through the app store, and I think that's something of the norm there. I think managing large, required changes (like updates in processor architecture) is difficult, but I don't think I can fault Apple for going through the changes regardles.

Re: macOS 11 (Big Sur) Compatibility News

#67

Earlier quoted context omitted.

Many forget that a large number of Mac customers are not US based. In fact, many live in areas with no apple stores at all. Seems to me that apple is glad to sell to everyone but only really care about a few.

And even US based folks might now have an Apple Store within reasonable driving distance.

That's on them.

Re: macOS 11 (Big Sur) Compatibility News

#68
post #59

Earlier quoted context omitted.

Many forget that a large number of Mac customers are not US based. In fact, many live in areas with no apple stores at all. Seems to me that apple is glad to sell to everyone but only really care about a few.

I'm not US based either but support is available online as well.

Apple online support has probably been my worst experience ever. On something as simple a ordering 2 magsafe power supply, they manage to only send me 1, and had to wait 3 weeks without any communication to finally get the notification for the second one shipment after a support call. Every low-key chinese Ebay sellers has better support than that.

Re: macOS 11 (Big Sur) Compatibility News

#69

Earlier quoted context omitted.

It's just buggy, not dead. However there should be a point when backward compatibility should be dropped, if you want to keep maintaining a sane codebase and interface, or force a "better" way of doing things. When Apple deprecated OpenGL and moved to Metal, I hated it but I actually respected a lot, cuz Metal does have a superior design, and by deprecating old technology they're forcing devs to use this better techn…

> It's just buggy, not dead. However there should be a point when backward compatibility should be dropped, if you want to keep maintaining a sane codebase and interface, or force a "better" way of doing things. Not when millions of people rely on working computers, and as much third party peripherals.

Then I'm interested to know when, what's the number of years, should we drop backwards compatibility for a certain version of interface, if ever. I'm sure there're still a lot of punch card programs and today no new system support it. Also there's always a option to not use the new technology that dropped backwards compatibility, which is why many people still buy second hand game consoles and casette players. I love them, but I accept the fact that they're no longer backward compatible with new devices.

Re: macOS 11 (Big Sur) Compatibility News

#70
post #59

Earlier quoted context omitted.

I'm not US based either but support is available online as well.

Apple online support has probably been my worst experience ever . On something as simple a ordering 2 magsafe power supply, they manage to only send me 1, and had to wait 3 weeks without any communication to finally get the notification for the second one shipment after a support call. Every low-key chinese Ebay sellers has better support than that.

>Apple online support has probably been my worst experience ever. On something as simple a ordering 2 magsafe power supply, they manage to only send me 1, and had to wait 3 weeks without any.

Worse support experience ever, or worst experience ever?

If it was the latter, you have a pretty sweet life!

But even if it was the former, you must have had some pretty great online support experiences until that point...

Post reply on HN