Live data from Hacker News

An appeal to Apple from Anukari

anukari.com

191–197 of 197 posts

Re: An appeal to Apple from Anukari

#191
> (An aside: chalkboards are way better than whiteboards, unless you enjoy getting high on noxious fumes. in which case whiteboards are the way to go.)

That looks to be a smoother chalkboard than I’ve ever encountered. If I had been using such chalkboards, I suspect I’d agree, but based purely on my experiences to this point, my opinion has been that chalkboards are significantly better for most art due to finer control and easier and more flexible editing, but whiteboards are better for most teaching purposes (in small or large groups), mostly due to higher contrast. But there’s a lot of variance within both, and placement angles and reflection characteristics matter a lot, as do the specific chalk, markers and ink you use.

Re: An appeal to Apple from Anukari

#192

Earlier quoted context omitted.

Thanks for the thought, unfortunately when running as a plugin Anukari is subject to whatever plist.txt the host application uses. I think that I did try that with the standalone binary at one point, but unfortunately I did not appear to take notes! That probably means I did not have success.

Very cool work.. and frustating running into walls imposed by manufacturers, I imagine! I've also been working on GPU-based audio plugins for a long time and have done some public material on the subject. Just my two cents: have you considered using a server/daemon process that runs separately and therefore more controllably outside a DAW (and therefore a client-server approach for your plugin instances)? It could al…

Do you have a link to your stuff?

> have you considered using a server/daemon process that runs separately and therefore more controllably outside a DAW

I'm slowly coming to the same conclusion, for audio plugins on GPUs.

Re: An appeal to Apple from Anukari

#193

Earlier quoted context omitted.

My problems start long before the special APIs come into play. When we supported Mac, I just wrapped the APIs like you do for any other system. The problem is I don't use Mac, so building software for Macs is inherently troublesome. I can build and test for Windows just fine from Linux and OpenBSD. I can't for Mac. Now you might say this is problematic, Apple doesn't want third-party developers locking their platform…

Why would I want to use software that you never tested on the target machine?

I explicitly conflated building with testing not even 4 sentences into my post.

Re: An appeal to Apple from Anukari

#194
post #161

Earlier quoted context omitted.

>Once upon a time I thought either GNOME or KDE would win, and we could all enjoy the one Linux distribution, I was proven wrong. Linux users don't want one to win. As soon as one gained any traction, the users would switch just for the sake of it. It's also crazy how neither ever actually improves because they are so focused on copying whatever windows and mac are doing instead of continuously improving. The linux d…

> The linux desktop experience isn't any better now than it was 20 years ago. You can't say that with a straight face. 20 or so years ago you would barely have hardware support for anything you wanted to use, or have to go trough a battery of guides just to get 50% of your computer working. Nowadays you just boot a live environment and likely 99% of your computer works out of the box, even tough your OEM gave ZERO sh…

>You can't say that with a straight face. 20 or so years ago you would barely have hardware support for anything you wanted to use, or have to go trough a battery of guides just to get 50% of your computer working.

Sure on weird hardware, but it you had something that was decently supported like a thinkpad, everything mostly just worked, same as now. A lot of your "linux improved..." stuff doesn't matter to end users for the most part. It's nice that they're growing the tent, but it doesn't change the fact that actual desktop experience hasn't improved much, despite it having been "year of the linux desktop" for the last 20ish years.

Re: An appeal to Apple from Anukari

#195

Earlier quoted context omitted.

Feedbacks often go into a black hole unless either: 1. A bunch of people file effectively the same bug report (unlikely here) 2. An individual Apple employee champions the issue internally 3. Someone makes a fuss on Twitter/X and it starts to go viral Sounds like the OP is trying to get #2 to happen, which is probably his best bet.

Another trick is to schedule some Apple engineer time during WWDC, and plead your case.

I was going to recommend this. They may have some suggestions of how to improve things with existing metal as well.

Re: An appeal to Apple from Anukari

#196
post #37

Earlier quoted context omitted.

I don't disagree with you, but there simply isn't an alternative for pro audio developers. You go where the users are and the majority of the market (by revenue) are Mac users. Now a lot of people may reply to this that Windows isn't that bad with ASIO (third party driver framework) or modern APIs like WASAPI (which is still lacking), or how pipewire is changing things on Linux so you don't need jack anymore (but god…

> You go where the users are and the majority of the market (by revenue) are Mac users. One of the worst things about Apple is how much time and effort they spend trying to lock you into their platform if you want to support it. There's no excuse for it. Even once they have you on their system, they're doing everything in their power to lock you in to their workflows and development environments. It's actually insane…

What I always find curious is how some of the biggest Apple supports are likely some of the same folks who were super anti-MS in the 90s.

Re: An appeal to Apple from Anukari

#197

Hey everyone, it worked, I had a super productive conversation with exactly the right person on the Metal team! Thanks for helping me get Apple's attention. I didn't at all expect this amount of support. https://anukari.com/blog/devlog/productive-conversation-appl...

>While I can't share any technical details... The engineer provided some suggestions and hints that I can use right now to maybe — just maybe — get things working in the short term Great that you have a workaround now, but the fact that you can't even share what the workaround is, ironically speaks to the last line in https://news.ycombinator.com/item?id=43904921 of how Apple communicates >there’s this trick of setti…

Despite enjoying your idea, I probably won't do that, but certainly anyone who actually has this same problem should reach out to me and I'll put them in touch with the right folks at Apple, who can share the info.
Post reply on HN