UK event with Mathieu Pernot - 17 July

[David A]

@Greg There is the little issue though that Roon didn't have any dramas streaming when they tested it and have had quite a bit of trouble duplicating the problem. I think this is more about bad luck than anything else.

You maybe right, but reading all of Dannie’s posts on the roon forum, I get the impression there is a degree of arrogance and belief their QC is infallible. Clearly it is not. Having said that, it is clear roon seem to understand what the problem is and has offered help to Devialet to sort it out and it seems Devialet are being unresponsive. What a shame!

I don't get the feeling that Roon think that their QC is infallible but I do think they believe it is thorough which is a different thing. They also admit problems when they find them, and fix them fast. A lot of us had problems with Roon not recognising our specific Expert Pro models in the first few days after Devialet released the latest FW and our amps became Roon Ready. Roon tracked that down quickly, admitted it was their problem, and instituted a fix on their servers in a matter of days which fixed the problem for us. That kind of response doesn't support claims of arrogance.

On the other hand, what have we got from Devialet on the gigabit ethernet problems? Nothing definite in the way of any statement about whether there is a problem, how common  it is, what the likely cause is, or even a whisper of a time frame for a fix. I's now more than 6 months since the FW which triggered this problem was released and we've had nothing concrete from Devialet though we at least have had several comments from Roon stating that the problem isn't theirs but lies with Devialet and also saying that they've reached out to Devialet with offers of assistance which appear not to have been accepted.

I didn't see arrogance in Danny's responses on the Roon forums, I saw a concern for Roon's customers and a frustration with Devialet who aren't being open with their customers and also don't seem to be overly concerned at fixing the problem.

I wish the probnlem were a Roon problem because if it was a Roon issue we'd have had a clear acknowledgement of the problem and it would have been fixed months ago.