Then, with a view to simplify, since this is the Roon community forum, it would make sense to focus on the Roon architecture first.
That is, local/steaming media → server → network → network steamer → DAC.
I would agree. The moment I saw Diretta included in what should be a normal model I was suspicious. The thing is, if you remove Diretta nothing is indicated as broken. The bits are all still there, timing is still correct. The things Diretta fixes in its marketing are tenuous. That doesn’t meant it has no benefits. But it isn’t necessary to include in what is otherwise a generalised model.
1 Like
If Diretta is a necessary part of the framework, then the entire premise is disingenuous.
2 Likes
This is not what you stated in your initial post:
So, good to know that you are refining your position.
6 Likes
That makes me even more suspicious that the OP just pasted AI slop without even reading it, and now we humans are supposed to discuss among ourselves.
Apologies for being too direct. We did indeed poo-poo on this thread, but I’m getting tired of this Diretta nonsense.
2 Likes
Here is a brief clarification.
The transmission methods discussed here can be grouped into three structural categories:
TCP/IP‑based pull delivery
Bit‑perfect transfer without considering the receiver’s timing or state.
RAAT‑style cooperative pull delivery
Still bit‑perfect, but coordinating with the receiver’s timing and state.
Push‑type delivery such as Diretta
A different timing model that does not follow the same bit‑perfect assumptions as pull‑based systems.
My model refers to these categories, not to any specific protocol.
Diretta was mentioned only as one example of a push‑type approach.
The same explanation applies equally to professional push‑type systems such as AES67 or Ravenna.
The goal is simply to describe how static and dynamic domains behave within the Roon signal path, without promoting any protocol or implying audible differences.
Diretta is bit-perfect, and the bit-perfect-ness of a protocol has nothing to do with being push or pull.
2 Likes
Last I checked, RAAT, Diretta, and the rest ll were running over IP networks. Usually using TCP even.
Really, this looks more and more as either rather pathetic marketing for Diretta or an exercise in trolling by posting some AI-generated slop that makes absolutely no sense, and the OP either does not know or care.
3 Likes
@Londres_H, I am uncertain whether you don’t grasp the feedback offered or you are choosing to ignore it.
Because you continually change your position, to the point of contradiction, and modify the model without considering feedback, I am of the view that this discussion has run its course.
Accordingly, I will close the discussion if there is no change in direction.
2 Likes
Thank you to everyone who participated in this thread and shared your perspectives. Since no new system models or technical corrections to the presented framework have emerged, the analysis has reached its natural conclusion. I will therefore wrap up this thread and ask the moderators to close it.
Because this post was intended from the beginning as a structural system‑model analysis, the terminology and analytical framework are deliberate. To leave a clear and definitive reference for future readers, here is the final conclusion of the static–dynamic domain model:
Digital systems appear binary, but every transition from the static domain (where data is held) to the dynamic domain (where switching and timing occur) is ultimately an analog event. These transitions always occur under micro‑volt‑level fluctuations. Modern low‑voltage, high‑current circuits are extremely sensitive to such variations; even tiny disturbances can influence timing and overall system behavior.
This physical reality shapes how different transport architectures behave:
-
Pull‑type systems isolate timing inside the endpoint. They tolerate external variability and are inherently suited to open, general‑purpose environments.
-
Push‑type systems rely on deterministic timing controlled strictly by the sender. Because they cannot absorb noise or fluctuations in the same way, they function reliably only in closed, tightly controlled environments.
A clear example of this shift is how RAAT evolved when ARC was introduced—moving toward a stricter pull‑based model to handle variable WAN and mobile conditions. Similar timing‑critical constraints appear in other fields as well, such as high‑frequency trading.
Understanding the interaction between static and dynamic domains—and the analog behavior underlying all digital transitions—explains why these different approaches coexist and why each has its appropriate application.
Thank you again for your time, and happy listening to everyone.
Demonstrandum non demonstrat.
3 Likes