@ERIC, EDIT: The explanation of samplerate problems regarding asio4all was removed as we found a solution to that (the samplerate issue). The rest remains.
@Eric, ok, files: https://1drv.ms/f/s!AgwTOVHwFIUih81uVGO_nmYfonLvYQ
I found another setup that is working fine with roon and 94/24: If I listen via this laptop’s Realtek high definition output, e.g. on headphones, everything is ok. This output can be set to 192/24 or 44.1/16, it does not matter. It is ok.
The files: Both were recorded using a virtual sound card. The players – roon and MPHC - were sending streams to this virtual soundcard (we have 4 different types). This card is then used as input to Reaper DAW, from where the recordings were made. I repeat the original file is in 96kHz 24bit format. Reaper was set to record in 44.1 24bit.
The original recording is Jen Chapin Re-Visions, a fantastic recording (HD Tracks). My two Reaper recordings:
- Roon as player. Play with some proper headphones, perhaps a bit loud. You will hear the high frequency ringing as a kind of “overtone” on the bass.
- MediaPlayerHomeClassic (MPC-HC). The setup is identical, but the error is gone.
What is going on? It looks like there is some type of bad chemistry between roon and the Asio4all generic driver, possibly related to samplerate conversion.
Importantly, another new finding, the error is gone if Directsound driver is used instead of asio4all in this Reaper recording setup, probably because DirectSound is obedient to the 96/24 format.
It could also be that Roon is non-compliant with all our 4 different virtual soundcards, but I find it unlikely. If Windows is properly installed, these virtual sound cards may even produce a 100% bitperfect stream and is therefore highly usable. I have seen Roon staff commenting on virtual soundcards in a “reluctant” manner, but I believe the problem is a4a.
I hope to learn something from further comments, and that this was helpful.