No more dropouts streaming Roon RAAT over gigabit ethernet

[thumb5]

I think there's a danger in simply saying that the problem "belongs" to anyone.  The failure may only arise for certain combinations of hardware and software, and a handful of hardware manufacturers and software developers will have produced those components.  Only when the right intersection of components is put together will the problem result in a failure, so it can't truly be said to "belong" to any single hardware or software developer.  The fact that a failure is only reproducible when component X is used doesn't mean that it's caused by a defect in X: it may be a fault in component Y which is only manifested by some interaction with X.  You can only say the problem belongs to a specific component when the root cause is known, and even then it may not be a cut-and-dried decision.

This kind of problem needs to be investigated by finding a hardware and software set-up in which the failure is repeatable, and then painstakingly testing hypotheses to gather more information and eventually isolate the root cause one step at a time.  Trying to assign the problem to any specific hardware or software components without having concrete evidence (that's to say, well-defined test cases to disprove or add weight to those hypotheses) is not usually a route to successful resolution.

In principle that investigation could be done by anyone with the technical knowledge, a test system capable of reliably reproducing the problem, and the necessary hardware and software tools to gather information about what's going on.  But tracking the problem down may require expertise across many disciplines including some obvious ones: audio streaming, network protocols, etc. and some less obvious ones such as the details of various operating systems, network stack and device driver implementations, and the operation and peculiarities of specific network interface hardware.