I am running Roon Core on a Linux box but Roon Control on a Win64 desktop. After several minutes, the control app closes and I have to waken it with a hit on the keyboard space bar.
The Win64 desktop is set to never turn off the display and never to sleep and that works for other operations.
Sounds like there’s something else going on. I run core on a Nucleus and often use Roon on my desktop PC. The app never closes. I’m assuming the core continues to play music even though the app has shut down? I do know sometimes when I go back to Roon if it has been in the background it sometimes needs to refresh. But it never shuts down or goes to sleep.
@support
How about this? Roon can control the volume in my exaSound DAC but, every time I want to use it, I have to click on the VC button to pop-up the VC control. How about having it up there all the time when volume is not fixed?
Just to clarify here, the Roon app closes, as in it’s not opened any longer or just the screen goes to sleep and Roon keeps running in the background? Can you please share a screenshot of your Windows Power settings?
Thanks for the feedback here. I would recommend also posting your suggestion in the Feature Request section of the site.
Our product team and developers keep a close eye on that category, so that’s definitely the best place to propose a change like this and get feedback from the Community.
Thanks for that screenshot. If you look under “Change Advanced Power Settings” and navigate to the Display section, do you have the option to change your screen timeout there?
Does the same behavior occur if you try to temporarily use the PC as the Core?
Open Roon on the other PC you wish to try as the Core
Roon Settings -> General
Disconnect
On the “Choose your Core” screen, press “Use this PC”
If asked to Unauthorize, you can go ahead and do so. You are limited to one active Roon Core at a time but you are free to switch between them as often as you’d like.
Verify if the same behavior when the Remote is the Core