
RAAT is asynchronous because the underlying network protocols are asynchronous. You can stick a dozen fake âaudiophileâ switches with clock inputs in the chain, it will not become synchronous. The only thing that matters is that the clock in the DAC is accurate enough (which it is even in a $100 DAC).
There is nothing that needs to be synchronmized between a Roon server and a DAC anyway.
Itâs a finme streamer, as far as those things go, but thereâs nothing âsuperâ about it.
Itâs quite inexpensive, as far as audio jewelry goes. Not that more expensive ones worked any better. Or cheaper ones any worse.
If you want to use an inferior synchronous mechanisms, connect your DAC with S/PDIF or I2S, and you can happily deal with jitter, and maybe, possibly, needing to use an external clock to synch things. Of course any decent DAC, including the 160, will reclock incoming signal anyway, so the only effect it will have is you fiddling with connections to achieve absolutely nothing.
On the network side of the 130, no amount of clocks will change anything at all.
Yes, because it works and works well. And even if you managed to make it talk any other protocol, like some Diretta bullsh*t or whatever HQPlasyer uses, or anything else, it would be just as asynchronous as RAAT. If you want to have a synchronous network connection, whatever that might mean, you need to come up with your own new networking standard. Of course then neither your Roon (or any other) server nor your 130 will support it, so good luck with that.


