31–40 of 62 posts
This seems like a needlessly aggressive and poor take. Its a cool bug that they discovered; but going into "Apple's audio engineering team is, at least on some level, incompetent (or incompetently run; I'm not blaming the employees here, but rather the organization)" is just unproductively mean. "and obvious in a sine sweep frequency response test, which is the most basic test you can run end-to-end on a completed au…
Earlier quoted context omitted.
It's a bug that shouldn't have happened though. One hopes that they have a well verified reference implementation for all their signal processing pipeline (and ideally both a high level and a bit accurate model) and they're testing the output of any optimised implementation against that, with random input data. This is Apple, one of the most "valuable" companies in the world. They should do their job.
> They should do their job. 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.
Earlier quoted context omitted.
> They should do their job. 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.
I'm sorry, dropping samples is a pretty egregious signal processing cock up and one I'd be ashamed to have made. I think the market assessment is pretty meaningless in the face of objective evidence like this. By all means, you can keep buying Apple, but I'd have no trust they're doing things properly under the hood.
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.
If I were the engineer who wrote this bug, this post would not motivate me to fix it. In fact it would do the opposite.
At Apple we would see this tone all the time from people on the VLC project. It got so bad that the senior people would refer to them as DCS, Drunken College Student. It got so bad that we mostly ignored them. It wasn't good for either VLC or QuickTime.
Honestly, there’s the ego if “we did this when the paid elites didn’t” in a lot of open source communities. I contribute to many projects and it always rubs me the wrong way because they don’t consider how many other variables the team has to juggle, and what priorities are like. To be clear, I’m not saying this is everyone, and it’s often the vast minority but it also often goes unchecked and unchallenged when it do…
It's a shame because the work they have done is great, but humility is a virtue many have lost.
It's hard for me to understand how noticeable this actually is. In the video where he plays samples from an affected and unaffected machine, I can hear there's a difference, but I couldn't tell you which one is correct. It sounds like it could just be normal differences in speakers between the two models. If that's the best example of the bug, then probably no one has caught it because it doesn't really matter. Also,…
The incorrect tone sounds like a train horn. There’s more than a single pure note being produced.