The key advantages of Audirvana, as far as I can tell are 1. "System Optimization" where it applies "extreme priority" over software running in the background
Audio playback is an undemanding application, primarily I/O-driven. Eg: a 192 ksamples/s stream at 24-bits/sample is only 1.15 MB/s. A CPU is minimally involved (unless DSP is active) in the actual playback of audio - it is a director of traffic.
and 2. Loading the full track into memory and playing it back from there
In order for a CPU to do work on data, it
must be in memory (RAM). Whether the whole file is in-memory or not is largely irrelevant as long as the DAC's buffer is sufficiently populated, preventing underflow/starvation. For a buffer on the order of say 64 ksamples, that is about 1/3 of second of playback, a comfortably long time between transfers of data.
From Audirvana's homepage:
By taking control on your computer’s audio flow, Audirvana prevents other applications from interfering during listening and from making hidden changes to audio samples. It reduces CPU activity and stabilizes power supply to minimize digital distortion and possible radio frequency interference. Finally, it optimizes the operation of your system’s digital-to-analog converter – whether integrated or external – by providing it with an adapted and pre-decoded digital stream.
As Ray would say, "Uh-huh..."
Having said all this, it is possible that part of a system's audio stack of software could modify its input in a perceptible way.
IIRC, Windows had problems in the past with a noisy resampler, for example.
@amirm or you other professional guys with analyzers, can you do any data-based analysis?
If you have a soundcard with a recording input, and the will to learn, you can check for audio-player-induced effects yourself.
Search on this site for
@Blumlein 88's loopback test and
@pkane's null-testing software for ideas about how to proceed.