Devialet Chat

This is a weird one.

I had a thunderstorm last night and shut down and unplugged the system. This morning I plugged everything back in, started up the system and started to continue playing the album I was playing last night when I shut the system down. Roon was showing that I was playing to the Roon Ready input of the 140 and everything was sounding normal. That album finished and I started on another one then got up to make breakfast. As I walked past the 140, I noticed that its display said I was using the AIR input so I went back and checked. Roon was showing the Roon Ready zone was in use, the signal path info said the signal was going to the 140 with RAAT, I opened up Roon's Audio setting menu and the Roon Ready zone was active and the AIR zone was inactive. Everything I could check in Roon said I was using RAAT and the 140's display said I was using the AIR input.

So I changed the 140's input to Roon Ready by using the input button on my Devialet remote. Music kept playing with no difference in sound and the 140's display now showed the Roon Ready input.

After the album finished I turned the Devialet off and restarted it again with another album. This time the 140's display showed the Roon Ready input, music was playing, and everything was totally normal.

Has anyone else had this situation occur with their Devialet's display showing a different streaming input to the stream the amp was receiving?

The only similar report I've seen is this one: https://community.roonlabs.com/t/deviale...rnet/64895
Maybe entirely different, but I believe he had to disable the other zones and devices before RAAT worked on his Devialet amp.

@ogs

Thanks, but I think that was something different.

I only use 1 input to my 140, ethernet, and all other inputs are disabled in my config file. I also run Roon with only 1 zone active at a time so disabling other inputs/devices/zones in either the 140 and/or Roon isn't an option for me, they're already all disabled.

My problem was simply Roon using RAAT, the only zone it had active, and the 140 saying it was using AIR on the ethernet input, the only input it had active.

We seem to be getting a few bad thunderstorms again lately here, another one late yesterday afternoon, so that means I end up doing a lot of shut downs, unplugging systems, and then reconnecting and turning things back on. When I reconnected everything last night after yesterday afternoon's storm had passed over, everything worked normally.

I think there may be a small window of time when the Devialet is starting up, right at the end of the startup, when there's an internal process going on in which the Devialet can detect RAAT input and switch its soft input to that but the advice to the display to show the change doesn't work and I probably started playback from Roon in that brief period. Whatever the reason it hasn't happened again over 2 complete restarts now. Both of those total system restarts worked perfectly. I think whatever the reason, this was simply a "glitch" with the 140's display process. It didn't affect playback and I would never have noticed it if I hadn't looked at the display in passing at the time.