Hacker News new | past | comments | ask | show | jobs | submit login

I don't quite agree with you, taking into account it's an analogy designed to help illustrate the issue for general audiences. It's not as if we don't have ProPhoto RGB or other wide gamuts or don't understand the issues of rendition accuracy and resolution within the visual spectrum. There was never any debate that sRGB alone in particular was quite limited, or that dynamic range was an issue. It's just that it represents a ton more data and is technologically and commercially much, much harder. As tech has caught up displays have continued to chase human visual limits, starting with resolution, then frame rate, and finally major industry wide improvements to gamut and range with BT.2020/2100. I mean heck, it wasn't that long ago that we barely had color at all. I still remember well the first 8-bit system I ever got, or back when I regularly had to manually change between 16-color/256/16k to prioritize resolution or color because my system just didn't have enough VRAM to handle both at once. Audio did far better at matching human limits much, much longer ago.

But within the visual spectrum but not showing on the screen is still within the visual spectrum. The article examples refer to infrared and UV+ for contrast, and that's entirely correct. Monitors displaying either of those would make no difference (well, beaming ionizing EM at your face raises significant concerns audio doesn't at any level) at any point. They're simply beyond human eyes period. It's an accurate analogy. Failing to reproduce something within human limits would be what you're talking about, but that's a solved problem and not something 24/192 offers you anything with.

Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact