Don't forget: "most players use malloc to get memory while new is the c++ method and sounds better."[1]
reply> My favourite: "audiophile-grade" audio players which allocate a single contignuous buffer of RAM into which they load/decode the whole .WAV/.FLAC file, because supposedly the CPU "jumping" between "fragmented memory" causes audible "jitter".
replyThanks for the laugh... this is absolutely bonkers. In case anyone is wondering, before sound hits our ears it has to go through a digital to analog conversion, which takes place on hardware independent of the CPU, operating with its own clock and buffers etc.
Am486DX/100 was enough to decode and listen an MP3 at 22KHz (and maybe mono?) and was more than enough to listen for 44/16/2 PCM. It's 31 y.o. today.
replyIn addition to that, while it is possible to hit a delay and run out of buffer because memory access is slow (the most obvious would be if the input got swapped to disk at an inopportune moment), but the audible effect is really obvious. This isn't some subtle "oh my music sounds ineffably worse" effect, it's "my computer is glitching and my music is unlistenable."
replyI can tell when my CPU usage spikes because it causes a hum through my speakers, so this does not seem that far-fetched.
replyIt's just means you have a shitty audio tract with not enough shielding. Move to SPDIF/TOSLINK.
replyThe latter is probably true, but the former does actually happen, and it's easy to accidentally do--lossless or not.
reply