3 ms·
I think I read a thread like this almost 10 years ago when I happened to be doing some audio work, maybe it was the same one. If memory serves, there was someb
by asveikau 4y ago
I think I read a thread like this almost 10 years ago when I happened to be doing some audio work, maybe it was the same one.
If memory serves, there was somebody saying that exiting the program cleanly sounds worse, you need to crash on a page fault reading the input buffer instead, and that's your end of file behavior.
Someone else said FLAC makes it sound worse, but I suspect they just couldn't figure out how to use libflac.
In other words they were bad programmers writing buggy, half baked shit, and they explained away their broken code as sounding better.
Even the snippet I see in the linked post, right off the bat they start their loop with WaitForSingleObject, that's kind of suspect; the first thing they do is enter the kernel to block at every loop. I suspect they aren't doing that in an optimal way.
- mort96 4y ago> Someone else said FLAC makes it sound worse, but I suspect they just couldn't figure out how to use libflac. Honestly, that's not so ridiculous. Lossless will sound different from lossy, and someone may prefer the lossy version.
- 323 4y agoThey were comparing FLAC with raw uncompressed PCM wave files. Some swear they can hear the difference.
- mort96 4y agoOh. Yea that's either BS or a serious software bug.
- JohnBooty 4y agoIt's pretty trivial to go PCM->FLAC->PCM with e.g. ffmpeg and verify there's no difference. I suppose it's possible there's a software bug with the actual FLAC decoder they were listening with. However it of course seems much more likely they're imagining it.
- dylan604 4y agosince the title includes the 2013 date, might very well have been the same one
- mauvehaus 4y agoI think the real problem is that all of those commented out lines of code are adding some harsh chartreuse overtones in the mid-range.