It is not biologically possible for us (unless one is an alien) to hear above 22kHz. 44.1kHz is enough to record in perfect fidelity [0]. For strictly listening purposes, 192kHz/24bit is wasteful, just extreme overkill because "bigger numbers = more good".
People can't even reliably detect a difference between 320kbps MP3s and source-quality FLAC/ALAC/WAV/PCM. On very good headphone and speaker setups. Good quality MP3/AAC is all one needs for airpods and the bluetooth protocol can easily handle those bitrates.
[0]: https://en.wikipedia.org/wiki/Nyquist%E2%80%93Shannon_sampli...
edit: changed record->playback. Here I'm just discussing playback; for audio production purposes 192kHz/24bit is desireable for several reasons. Once one ships that album/song though, it should be downmixed back to 44.1kHz/16bit.
I've got all music in 44.1kHz or 48kHz FLAC (only on the server, so I can transcode it to ogg opus for mobile playback reducing the space usage without lossy to lossy artifacts). Similar effects apply to many other such cases.
Audiophiles buy 10'000$ golden HDMI cables... which don't even support HDMI 2.0a. They buy gold-plated toslink cables (!)
I've simply written a small python utility to handle everything automatically.
Aside, "Nyquist criterion" would be a sick band name.
What's suspicious about it? Do you take this to mean something other than lossless compression/encoding?
- not particularly a huge upgrade in audio quality, or
- an attempt to upsell me on some audio-related product
The same for higher resolution samples, an audio pipeline using that available dynamic range can do cool stuff.
Both are pointless for 99% of music sold though.
I hope the availability of high resolution, or more importantly the spacial audio, will inspire some artists to really explore the space. I'm hoping for some stuff like the Flaming Lips' Zaireeka or Yoshimi album's 5.1 mix.
Have you seen the gold plated overkill?
> found that a function called memcpy was the culprit, most memory players use memcpy and this is one of the reasons why memory play sounds worse ie digital sounding. Fortunately there is an optimised version of memcpy from http://www.agner.org/optimize/, using this version removes the hard edge produced by memcpy.
Just imagine if stuff was like this though and computing were more 'analogue' -- each of those 15 layers of JavaScript transpiling just degraded the quality of the end result slightly.
That said there absolutely is a case for high-bitrate, losslessly-compressed, DRM-free, watermark-free audio as the standard, and that is sampling and remixing. Slowing down a 320 kbps mp3 by just 50% sounds like shit.
It's possible to do this in a way that's not in any way distinguishable from a real 5.0 setup
Dolby provides a similar system, but with a generic room simulation, as do several others.