Perhaps it’s not surprising that Roon have not been able to duplicate the issue.
I commented some time ago on Devialet Chat that I had never had the problem with my 140 with content at CD resolution, 96/24, 176.4/24, or DSD64 but that I hadn’t tried 192/24 as I had no content at that resolution. I later commented that around 4 weeks ago I tried a direct ethernet connection between my Nucleus+ and my 140 (network connection via a n ethernet to USB3 adapter) and immediately ran into the problem with CD resolution content so I reverted to my previous setup using a Netgear GS105 switch and the issue went away,
Late last week I replaced the GS105 switch with an Orbi satellite and had no problems with any of the different resolution format content I have on the Nucleus+ and decided to really give things a “torture test” so I used Roon’s DSP to convert everything to 192/24. I played a range of CD quality, 96/24, and DSD content for over 4 hours without problems. I ended up swapping back to sending everything in bit perfect mode because I decided I preferred the sound of bit perfect mode slightly.
Yesterday I had another go at setting up a direct ethernet connection between my Nucleus+ and my 140 but this time I set up manual IP addresses for both the Nucleus+ and 140 for the direct connection. I’m still using DHCP on the network connection to the Nucleus+ via the USB adapter. I’ve only done about 3 hours listening with this setup so far but when I had no problems with bit perfect output from the Nucleus+ I again used Roon’s DSP engine to convert all content to 192/24 and played 2 records without problems before I went to bed. I haven’t fired up the system this morning to see whether my luck, or whatever it is, is still persisting.
If we stop and think about it, there’s no problem with a wifi connection to the Devialet yet there is a problem with a wired connection. That’s weird to my mind, and the only difference is generally an ethernet switch of some kind between the server and the Devialet. I had no problems with a GS105 switch, I ran into problems with a direct Nucleus+ to Devialet connection with a setup using DHCP and the wifi input on my 140 active, no problems when I reverted back to the GS105 switch, no problems with an Orbi satellite instead of the GS105, and no problems with a direct Nucleus+ to 140 connection using manual IP addressing. All connections have been gigabit ethernet.
I’m inclined to agree with @noris. This isn’t a Roon problem and I’m not certain the problem is essentially a Devialet problem. I’m currently inclined to think it’s related to what we stick between the server and the Devialet and probably not so much the device as something to do with network settings for the device.
But as far as I’m concerned here with my system, as of last night with my new direct connection arrangement between my Nucleus+ and my 140, I couldn’t be happier. Everything is running without problems, it sounds great, and I’ve managed to get rid of an intermediary device in my signal path. OK, 3 to 4 hours and 3 or 4 records doesn’t guarantee that my current situation is still going to work long term without problems but with this setup, and with the Orbi satellite, I’ve thrown everything I can at it including 192/24 courtesy of Roon’s DSP engine and I haven’t had a single issue at any resolution. I think that shows that it may well not be a Roon problem or a Devialet problem but rather a problem elsewhere in the network and possibly setting related.