Quote:
Originally Posted by
pkshan 
Sound quality is not all about bit perfect, but jitter,
complex program codes will greatly increase jitter,
Accurate data stream timing is very important for cd transport and software player
a bad timing will distort the shape of sound wave, increase high frequency noise etc....
ABX wav vs flac in foobar

and see whether it substantiates it. Jitter quoted to affect PC audio is from transmission and inherent to USB receiver (and transfer mode) + DAC chip and clock. None of these are as prominent as ground loops, DPC problems, and OS settings that cause audio to blatantly drop packets.
You're streaming data from the decoder buffer where it's in PCM format for both FLAC and WAV after the FLAC decoder that causes <1% CPU load while running. Claiming it produces audible jitter is simply pseudoscience and is equivalent to dancing around the pc naked with a set of drums and facepaint on.
Let me draw a simple parallel for you.
There are tens if not hundreds of processes and services/drivers running at a much higher priority and consuming a lot more CPU/IO and memory than the decoder. Even if the decoder caused magical jitter it would be miniscule compared to those. Use basic logic, please. E.g. do a CPU/IO/Memory profile on your system to see how little resources foobar actually consumes compared to the rest of the system. (not to mention transmitting data after it's being decoded to PCM and from a buffer

)
Moreover, Wav files are larger and consume more disk I/O as a trade-off, arguably, disk i/o is even worse than CPU use on some systems
Edited by svyr - 7/19/11 at 5:29am