Since updating Roon to v1.3 build 274 yesterday, I am experiencing a 6-7 seconds delay with every DSD file on my dCS Network Bridge. So DSD playback in Roon behaves as if there is a resync delay enabled, even when I set the resync delay to 0ms in the device setup. This issue has been confirmed by other Network Bridge users too.
What might be the issue here and how to solve it? It’s very annoying… Restarting all components in the chain did not help.
We’ve been working on this all day…wanted to share an update.
The change in behavior happened in context of some tuning changes made to RAAT to help the stability/performance of some WiFi speakers. These were relatively minor tuning changes, and the parameters that we changed are within a range that Roon Ready products are expected to tolerate.
The fact that this type of change caused a problem at all suggests an underlying issue in the dCS firmware. I believe that they are working on stability improvements in this area, and we will follow up with them about this soon in case there is any way in which we can assist.
Anyways–this week, we received a few reports of trouble with the Network Bridge and one reporting similar symptoms with the Vivaldi Upsampler.
Over the past 36hrs we’ve performed extensive tests on both products and both Roon builds. We also engaged the assistance of a knowledgeable dCS dealer, who duplicated our tests to produce an extra data point.
Those tests found that B269->274 did not modulate the behavior of the Vivaldi Upsampler or Rossini, but did cause a new bad behavior on the Network Bridge.
I’m fairly certain that the problems @G997 is having have the same root cause as the problems that Network Bridge users have reported, despite our inability to make them repeatable on two separate dCS Vivaldi installations. This discrepancy leads me to conclude that there is something setup dependent or environmental happening in addition to the changes in Roon.
Since we could reproduce the issue on the Network Bridge, we were able to figure out which change caused it. For the sake of continuity, will revert the new tuning changes for dCS products only in order to make time for dCS to investigate and address the underlying firmware issue that causes them to be incompatible with the new tuning.
This temporary fix will go into alpha testing tonight. If all looks good, we will try to release it to stable as soon as possible afterwards.
If I understand correctly, you will issue an update addressed only at dCS endpoint devices until dCS sort out their own firmware. Do you have an exact timeframe for this?
We’ve backed out of the only change in 274, so for now we are going to have to wait on more news about some of the underlying issues Brian mentioned above.
Yes. The device was unexpectedly sensitive to some minor performance tuning changes that we made on the Roon side. No non-dCS products were affected.
As a near-term fix, we made a special case in Roon to keep the old tuning in place for dCS products until this is sorted out. So the behavior of Roon with dCS products is now exactly the same as with Build 269 and previous builds.
We sent over a detailed post-mortem of the issue to dCS today to make sure everyone is on the same page and they have what is needed to move forward on this.