ROON ROCK
OS: Version 1.0 (build 186) stable
Server Software: Version 1.7 (build 528) stable
ROON Remote
Windows 10 Pro 64-bit, Version 10.0.18363 Build 18363
Network Details (Including networking gear model/manufacturer and if on WiFi/Ethernet)
Not relevant.
Audio Devices (Specify what device you’re using and its connection type - USB/HDMI/etc.)
Not relevant.
Description Of Issue
DEVICE SETUP: After changing “Buffer Size” from “Default” to any other value, when trying to set back “Default” value, this is not possible. When user clicks on “Default”, application is not setting this value (current value remains the same).
This is happening on Windows remote only, for any device. It is working fine on Android remote. I don’t know about other remotes (iPhone etc.).
Restarting ROON ROCK, ROON Remote or Windows doesn’t help.
I just gave this a try on a Windows 10 remote connected to a ROCK Core and things worked okay on my end. Can you record a video of the issue you’re seeing and share it here? This should help us understand what might be happening.
On this occasion, I saw that things had become… different. Now I have one DAC to which I can replicate the problem, and one that I can no longer replicate (can be seen in the movie). Moreover, now the behavior is the same in all ROON Remotes - Android and Windows. There is no more difference between Android and Windows.
I am absolutely sure that the first time I tried, the behavior was the one described in the support request. I set both DACs to “Default” using Andorid. In fact, it is also seen in the movie that the DAC Devialet was initially set to “Default”. If it had been the same situation as the first time, then I couldn’t have set this value.
Now I can no longer set it to “Default” from any ROON Remote. I also tried power off and on for DAC, as well as deactivating and reactivating the audio device in ROON.
Seems to be a random behavior. I’m sure I never had problems using “Default” value in the past (2018 + 2019). On the other hand, I see that @Petri faced this problem during september 2018.
I checked with our team on this — We don’t have any specific updates we can provide just yet, but our team is continuing to investigate.
We haven’t been able to reproduce this in-house so far, so the QA team things this is likely device-specific. Can you confirm the models of the audio devices you’ve seen this occur with? Can you share a screenshot of Settings > Audio for both of them? I’ll get this over to the team to aid in their ongoing investigation.
