Hacker News new | ask | show | jobs
by aaomidi 993 days ago
> These devs didn't even notice it until they tried to rip into the inner workings.

I mean, considering the source isn't open. Yeah, you need to do that.

2 comments

Well, for audio bugs that actually matter, you can just listen to it, or if you want to get all sciencey, throw the output and input onto a scope and compare them, or send the input and output sample values into the analysis software of your choice.

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.

He posted a video in the thread comparing an M1 machine (they don’t have the bug) with an M2. It’s rather obvious in that simple sine-wave test.

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.

That's as may be, but the person I was responding to was claiming that you needed the source code to detect it.

Clearly you don't.

The point is more that, yes, it’s technically incorrect. But if literally no human noticed or was affected in any way, who cares? That’s the only reason bugs matter anyway.