Thank you for the non derogatory, intelligent response. It’s refreshing.
To put some context around the latency discussion and link I shared, it was specifically regarding a Roon bridged device. The topic of discussion which most recently brought this about was a NUC with Audiolinux running Roon Bridge. The Roon Core server was a high powered device, also running Audiolinux.
I took statistics and I’m not talking about network latency. Did you read Andy’s response?
How do you know the processor’s buffers aren’t too small? How do you know whether interrupts aren’t impacting the processor? How do you know the drivers don’t impact access to the processor or maybe the buffers are too big? How do you know latency doesn’t impact sound quality?
Your ears combined with input from others who hear similar benefits. Until someone with the right tools can conduct a scientific study and publish them.
You can use a Pi with a HAT that provides an SPD/IF output like the Hi Fi Berri Digi, or the equivalent IQ Audio (can’t remember the model that provides digital out).
I don’t see any advantage of using a full blown PC for just an endpoint, especially not one with Windows running on it, with lots of irrelevant processes going on in the background. That would probably apply almost as well to a full blown Linux desktop distro. ROCK would be overkill, if you’re just using it for an endpoint. If you want to run your core on the same box, different story.
1 Like
Bill_Janssen
(Wigwam wool socks now on asymmetrical isolation feet!)
47
I just ordered a Canakit Pi 3 B+ to try as an endpoint. No hat. Just use the USB from the Pi out to my Mytek DAC, like this guy does. $61 including 32GB card.
Bill_Janssen
(Wigwam wool socks now on asymmetrical isolation feet!)
48
Well, you could try a test setup like this one. Use different OSs on the Pi and see if the results change.
hi there I am tryng to understand if sound is affected or not if latency is not controlled by any method or hardware . In my case I use as endpoint an old pc with a amd processor and 4 gb of ram. Do you think that working on lowering the clock values on processor as well as ram memory should help in any way to improove the final sound out of the box?
any help here should be very appreciated. amd
Your biggest gains would be in dealing with power.
1 Like
Bill_Janssen
(Wigwam wool socks now on asymmetrical isolation feet!)
59
I really don’t know, but I’d doubt it. It’s hard to come up with a reasonable hypothesis as to how that would happen. I’d be inclined to believe what @Henry_McLeod says: what you’d mainly notice is reduced power usage. But only by a tiny amount, I’d think. Perhaps the equipment would run cooler, so less fan noise?
On the other hand, there are always software/firmware bugs in modern downstream devices, as with this XMOS chipset problem in a number of DACs. Many of them are timing issues, race conditions in various parts of the software. So changing the upstream timing would tend to affect those downstream issues, which may shift the balance either towards or away from better SQ – almost impossible to tell in advance. I’d think the most hopeful thing to do in such a situation is continue to pester your vendor to fix their firmware, and stay up-to-date on firmware upgrades. What a pain!
Or, you know, drop digital and do everything in a firmware-free analog world, back to vinyl and tape and tube amps.
This is not my experience. I use a server core (NUC) and endpoint output device (microRendu 1.4), and have found changes at the server level (power, OS, etc.) to still have a big impact on sound quality.
I can’t explain it, considering the RAAT architecture. Seems like the server noise shouldn’t matter one bit, but it definitely does.