HI @Joseph_Gerardi ----- Thank you for the report and sharing your feedback with us, the insight is appreciated!
I have moved your posts regarding this behavior over to “this” thread where we are tracking this issue. Our tech team is currently looking into this behavior to try and determine what the cause could be. I have the details of both yours and @G997’s setups (thank you again for the PM) which I have been added to my report.
Additionally, I would also like to enable diagnostics on your accounts so I have an up to date set of Roon logs for my report. If I may kindly ask you both to please reproduce the issue and note what was being played/the time the error occurred I will enable this feature on your accounts.
I discovered a strange problem with playback of 16-bit tracks. When I try to play those tracks it takes about 10 seconds for the playback to start. Interestingly this does not affect any 24-bit tracks nor DSD files, where playback starts pretty immediately.
When RADIO starts and 16-bit track is chosen to be played, sometimes the tracks starts to play (of course after 10 seconds pause) and plays only 1 or 2 seconds and the sound is ceasing completely. In this case I have to press stop and play again, this usually helps. I have not noted this kind of problem with previous version of ROON.
This error persists and is regularly repeatable in 100% trials on Vivaldi Upsampler (we have 2 sets) and Vivaldi ONE (one set).
@Jaroslaw_Orszanski - sorry for the trouble here, I moved your post over here, where we have been discussing this issue.
To give everyone an update, we did make some progress today identifying the cause of this regression. We are still looking into a fix and how soon testing can begin so it can be rolled out, but identifying the underlying cause is a critical first step.
We will let everyone know as soon as we have more information, and we appreciate everyone’s patience.
Go into your Audio settings in Roon and you’ll likely see your bridge under Roon Ready devices with a blue “Enable” button next to it. Press that and then “Save Settings” in the pop-up that appears and you’ll get your bridge back in it’s normal form.
Scroll down a bit more to the AirPlay section and click the gear icon next to your bridge and click disable. That will turn off the AirPlay device.
You’ll go back to having playback start delays on 16 bit content but that will be corrected very soon.
We did some testing on Friday and determined that this regression was related to a low-level networking change. We put a fix for this into testing on Friday, and hope to release a surgical build to address this regression in the next few days.
Hello, this is my first post. We are experiencing an issue with our Roon system. This is a new wrinkle that did not happen at first. When we select a track to play there is a 10 second delay before the chosen track actually plays. I have been able to get the lag down to 1 second if we change our dsp engine settings for sample rate conversion. If we have this feature disabled the lag occurs at 10 seconds of delay before a track plays. If we enable sample rate conversion the player behaves properly. Delay is about 1 second. This occurs on my Rossini as well as my dCS Network Streamer. I do have a couple of BluOS devices here as well and they work fine. No lag regardless of sample rate settings.
My system consists of:
Roon core running on an HP desktop computer.
Music files located on a Synology NAS drive
All dCS pieces are hardwired to my network
Computer and NAS are hardwired to my network
Network router is a Luxul XWR-3100V1
We suspect this problem may have begun after a recent update to our Roon which is set to auto update. However, we cannot be sure.
This is a known issue and is in the process of being corrected. As @mike mentioned above the issue has been identified and a fix is going through testing now. Assuming all goes well there will be a Roon update which corrects the problem in the coming days.
Now there is a delay shuffling from a 96 file to a 44.1 file (resync set to 0)
In the past the delay was always going up in resolution…
When will this ever be solved???