alankila
Member
- Joined
- Mar 28, 2025
- Messages
- 81
- Likes
- 66
I personally do that as well, i.e. match the Linux pipewire's sample rate of 96 kHz with the Genelec internal DSP clock. IIRC, The Ones actually has multiple internal sample rates: woofers run off 48 kHz sampled stream, tweeter and midrange off 96 kHz. I don't know the details of how and why, this is just something I read off from somewhere, along with some other details of the process such as that the internal DSP is based on 64-bit floating point samples.For those of us who stream, it is beneficial to ensure that the DSP circuitry of the 8361A and W371A is matched by your streamer (in my case that's both Roon and my Dell XPS-15). This minimizes sample rate conversion. For me, that meant setting both Roon and my laptop to a sampling output rate of 96 kHz (in keeping with the Genelecs).The sonic improvements are obvious and immediately audible.
Gratitude to Genelec UK for the advice!
However, there is some doubt in my mind about your claim that it is audible improvement because resampling algorithms are already expected to be audibly transparent, and the additional bandwidth in sound output should be inaudible to a human. I think it is unlikely that there would be problems in resampling from lower sample rate to the internal clock in a professional monitoring product such as 83x1. I agree that it is theoretically obvious that minimizing number of conversions is good, but in practice it still might make no difference. What did Genelec say, exactly?
I personally did not notice any benefit when doing a sample rate switch, I was doing it more because I could and because it is useful to prove that the link between the speakers and the sound card is stable. One issue I noticed with running the higher rates is that S/PDIF signal is less likely to work in lieu of the AES/EBU signal. The signal is apparently much quieter and the higher sample rates makes it more difficult to receive correctly. I was able to get near instantly reliable transmission at 44.1 kHz and 48 kHz, probably thanks to short cable lengths. At 88.2 kHz, sound faded in and out for a few minutes but eventually stabilized. However, at 96 kHz the sound seemed to never stabilize. In addition to this, if the signal ceases, soundcards go to sleep, the digital link shuts off, and that resulted in the synchronization process starting all over again, which made me disable soundcard sleep altogether. Because of the difficulties in reaching the speaker, I decided to buy one of those cheap usb soundcards off Amazon with usb plug on one end and AES/EBU XLR plug at one end, which has worked without issue at every sample rate.
I'll say this much: I did end up improving the default resampling quality on a Linux system. Resamplers use CPU and people are somewhat obsessive and neat freaks on that operating system, and I've read complaints over the decades whenever a sound server uses any noticeable CPU. Of course, it is resampler inside the sound server that is busy converting from source's sample rate to system's fixed sample rate, so the tendency has been to push the default quality down to silence these complaints. For me personally, switching a couple of notch higher quality resampler seemed to make the treble a little less noisy, somehow, but I didn't try to ABX it. IIRC the default had about 60 dB SNR, and while it should have been sufficient, I would still swear that there was a little bit of fizz/noise in the treble and it became completely clear after improving that.