DEVIALET now Roon Ready.

[pjcamera]

Roon RAAT keeps dropping out for a few seconds. Never had this problem before

[pjcamera]

Cat 5 cable direct to router. Roon on dedicated NUC. Rock solid before update

[thumb5]

Roon RAAT keeps dropping out for a few seconds. Never had this problem before

I've not experienced any dropouts, before or after the FW update. Bear in mind you may have always had some packet loss, but not known. UDP (AIR) does not re-request lost packets, whereas TCP (RAAT) does. Are you using WiFi or cable?

Although UDP itself doesn't have a built-in mechanism to detect and re-transmit lost packets, are you sure that this is not part of the AIR protocol running on top of UDP?  I thought it was; there is enough information exchanged between the peers to enable detection and re-transmission of lost packets.

[Axel]

I like the new RAAT implementation, although I can’t tell much difference in SQ compared to Roon Air.
It is nice that we’ve got the return of Tone, Balance and SAM feedback under Signal Path. It makes it easy to make adjustments without having to peer at the Devialet screen. I don’t use these settings, they’re just an example.
   

[tbj]

Still showing the generic speaker icon with a big red "uncertified" on my setup 

Try to remove the power cord, power it up again and restart Roon.  Had to do that for one of my 220 (the other was OK).

[tategoi]

Did the above numerous times and I’m still “uncertified” but that will not stop me from enjoying RAAT.

[Soniclife]

Roon RAAT keeps dropping out for a few seconds. Never had this problem before

I’m getting the same thing, there are some threads on the roon forum about it, there is a suggestion to change a router setting, I’ll try that tonight and see what happens. Air was and is totally stable.

[midi]

Mmmh. ROON Air was never stable for me, but RAAT is until now. Strange, how it ever was.

[struts]

These are Danny's words exactly 120 days ago. Not bad at all Devialet! 

Another thing to look at: the previous version was fw 13.0.0 and dos 2.2.2. This version is fw 13.1.3.1 and dos 2.2.4.

Since we've got a 4 number fw code we know there were at least 4 versions prepared and tested to get to 13.1.3.1 (13.1, 13.2, 13.3, and 13.1.3.1) but there may have been versions between 13.0.0 and 13.1.3. We also know there were at least 2 versions of the dos prepared and tested between 2.2.2 and 2.2.4. Again there may have been versions that ran to 4 number designations as well. That means they've gone through preparing at least 6 different softwares since the last version was released 8 months ago.

I think a lot of work went into this. Some of those software versions may have been minor and simple bug fixes. I suspect the difference between 13.1.3 and 13.1.3.1 was pretty minor given the numbering, but there would have been bigger differences between 13.1.0, 13.1.1, 13.1.2, and 13.1.3 with minor bug fixes between each of those iterations and the same for the dos versions.

That's a fair bit of development work and a fair bit of testing, and we know there were earlier versions before the last release because they showed a beta version of the roon ready software in Munich last year. The numbering of the new and the last versions does tell a story.

I agree.  Evidence that this has been managed to a quality target rather than a date target.  Kudos to Devialet (and Roon).  The wait was painful and the silence was even more painful, but the result (for me at least) is worth it.  Cranking through some favourite tracks on the bigrig with a big smile on my face.

[Desert38]

First timer here......Since I implemented the new FW, I am finding that when I choose a song from my iPhone which controls ROON, the song begins to play immediately and sometimes cuts off the first couple of notes of the song.  Can you insert a buffer in ROON so that it isn't so quick?