Asahi dev found off-by-one bug in M2 MacBook Air bass enhancer(social.treehouse.systems) |
Asahi dev found off-by-one bug in M2 MacBook Air bass enhancer(social.treehouse.systems) |
"and obvious in a sine sweep frequency response test, which is the most basic test you can run end-to-end on a completed audio system to ensure it is performing properly. So they didn't even run that." The one conclusion you can draw, outside looking in, is: whatever tests they ran resulted in the creation of the best sounding speakers on any device in its class. That doesn't scream incompetence to me; it screams "We tested this against songs people will actually listen to, not 300hz sine waves."
This post is a bad look for Asahi.
This makes me cringe. I consider myself an experienced software engineer, but I don't think I'll ever criticize other's code like that.
It's a dev enjoying some hyperbole for something cool they fixed on a chat platform.
> "and obvious in a sine sweep frequency response test, which is the most basic test you can run end-to-end on a completed audio system to ensure it is performing properly. So they didn't even run that."
Do they want a list of all the stupid bugs there are in Linux/Desktop Managers/common apps?
Yeah an off-by-one error happens.
Funnily enough, I recently tried a PC laptop, and it had a non-obvious audio (possible hw-defect) bug as well. But the UEFI self test worked almost perfectly. Because of the frequency ranges it would use for the test
The mocking tone of this post is really not necessary. An engineer made probably one of the most common coding errors that nobody noticed because real world impact is minor to non existent. The devs should be trying to build a relationship with Apple, not mocking then each time they find a minor bug.
I mean, considering the source isn't open. Yeah, you need to do that.
They did their job. They delivered a sound system that has been called the best available in any laptop. Nobody, and I mean nobody, noticed this bug in the last three years.
Apple is doing just fine without your couch coaching about what they should have done. I might as well harass Apple for having 99% P3 color certification but not 100% accuracy certification.
Yeah I didn’t like the way the GPU stuff was presented. It was purposefully antagonistic despite absolutely no need for it.
That said, they’re 100% right on the HN issue. That’s not them overreacting or being mean. That’s avoiding abuse that HN refuses to do anything about.
It got so bad that we mostly ignored them. It wasn't good for either VLC or QuickTime.
Of course part of that is because corporate development is a black box from the outside , but even if it weren’t, there’s no way people would keep up with it anyway.
If that's the best example of the bug, then probably no one has caught it because it doesn't really matter.
Also, the tone of the post comes off as petty and immature, regardless.
The incorrect tone sounds like a train horn. There’s more than a single pure note being produced.
It's a shame because the work they have done is great, but humility is a virtue many have lost.
Sometimes it's good to be strategic, but sometimes we also need real accounts of things.
Personally an overboiling sadness & frustration that the world is captured inside closed priorietary & ultimately horrendously compromising mediocre application-centric versions of computing is a lamentation I am deeply familiar with.
The message isn't happy or here to win popularity contests. It's earnest & frank & hard, reflects on the feeling that the world is trapped & kept away from understanding.
This is one manifestion of a long running gnostic battle, one humanity has been losing for a while now, and I see no obligation or cause to pretend like earning popularity-credits helps anyone. Earnesty & catharsis on the other hand reflect the real. They portray the struggle as it is.
I think you mean "trillion" there?
*Steve Jobs would make this look tame
That being said, if the feedback provided had the same quality as the post linked above, one can justifiably see why not engaging with it at all is the best option.
Code isn't necessary to judge the quality of an audio system. You can pretty much treat it as a black box if you want.
The fact that no one has apparently even noticed this bug before says a lot.
This isn’t one of those things like the difference between 128 Kbps MP3 and FLAC, where there is a difference but it can be kind of subtle depending on the listening equipment.
It’s clear in that demo.
Clearly you don't.
It might well be the case that a bug in a bass audio driver is not that big a deal, but these sorts of bugs are easy to avoid and shouldn't happen. It does indicate something about the quality of the engineering.
But seriously, shit happens no matter where you look. At least this bug affected nobody. Windows has a bug that causes agony on a weekly basis.