It most probably has to do with the roon protocol standart but can anyone clarify that if using Roon with a Node 2i as endpoint if Roon pushes the data to the Node or if it instructs the Node to pull the data?
Thanks
john
April 14, 2020, 4:12pm
2
Hello @Lynn_Sorenson ,
I’ve attached two posts from our CTO describing how Roon RAAT streaming works:
A RAAT streamer never adds an source of clocking discrepancy.
Instead of thinking of the streamer as an extension of the device, think of RAAT as an extension of Roon that gives Roon a presence on the streamer.
The reason for this: Stacking multiple layers that pull data from each other does not create new clock sources so long as the data flow is controlled by the last layer in the stack.
RAAT does insert an extra layer (or 5, see below) of “pulling”, but there are many other layers of “pul…
Agreed about S/PDIF. I have guesses as to why they “got it wrong”, but I don’t know for sure.
Roon/RAAT are based on a pull model. I’m not sure where my explanation went wrong to cause confusion.
(Meridian’s streaming protocol is also a pull model).
For multi-zone, we run in pull mode with the zone that has been elected as clock master and push to the other zones, which are forced to compensate for drift internally.
The actual implementation is slightly indirect. The core knows how quickly t…
-John
Hi thank you for your answer
as I understood it, what happens is roon creates a command layer above the device’s OS/FW, this layer does not interfere with signal’s path.
when a device is roon ready is means it adheres to a command language that makes it compatible with the roon layer (I’m probably oversimplifying it…)