2.0 Server on Windows 10
12GB RAM DDR4
i5 2.4Ghz
512GB SSD
Networking Gear & Setup Details
CommScope CGM4331SHW TG4482 router/modem from ISP in Bridge mode
Archer AX55
Ethernet to core
Connected Audio Devices
MicroRendu
Pi4 HifiBerry
MacBook Air MacOS 12.6
iPhone 13 iOS 16
Hiby New R6 Android 9
Samsung Tablet Android 12
2 Yamaha AirPlay receivers
2 Google Chromecast speakers.
I generally shut down controllers or endpoints not in use.
Number of Tracks in Library
98,302
Description of Issue
Discover no longer works.
I see the Roon icon pulsating infinitely
I switched from the full install to Server about a week ago and upgraded to 2.0 on launch day.
Discover was working previously but I hadn’t used it since changing to Roon Server.
The Roon icon pulsates but nothing else happens.
Is it working for anyone else?
Do you have Daily Mixes?
Does it work if you switch Profiles?
I had a similar issue some time back but I lost both discover and Daily mixes which is why I ask. Switching profiles worked for me but creating a new profile did not.
I appreciate you’re very busy helping folks with bigger issues than mine and by all means, take care of them first.
But I’d really like to be able use Discover again at some point so I’m giving this thread a Simple bump so you Don’t Forget About Me.
Thank you for your continued patience here! And, you have my sincerest apologies for the long delay in following up. The team and I are digging into this more deeply, and I wanted to confirm: are you seeing this issue happen across all your roon devices? Or, only your Windows 10 core?
By chance, do you have another machine you might be able to test as another core to see if the issue occurs there as well?
With that, can you simplify your setup and only stream audio from the system output of your Windows core (disconnect all else) and let me know if this issue persists?
We’ll enable diagnostics in the meantime to take a look at your Roon logs and see if there is any evidence pointing to what might be causing this issue
Hi.
No worries. I saw how wild things were getting here for a bit.
I only have the Win 10 machine the core is on and another Win 10 PC.
I do have a MacBook Air that will probably still run Roon (it used to be my core) however my music library is on an NTFS formatted USB drive.
So I don’t know if that will help us here.
Oh, yes, I have this issue on all my remotes.
MacOS, iOS, and Android.
The core is running Roon Server.
Although as mentioned above, it used to run the full Roon.
Thank you for giving that a try! It sounds like there may be some minor corruption happening on the specific database backup you’ve loaded up.
If possible, could you try using an older backup that may pre-date when you noticed this issue take place? If you’ve made any major changes to your database settings recently, you may need to take note of the changes and repeat any necessary changes to the older database after it’s been loaded.
Hi,
Thanks for your continued support.
I rolled back to my oldest 1.8 backup and my oldest post 2.0 backup.
Neither helped.
I realize correlation isn’t causation but this seemed to start right after updating to 2.0.
Is there anything else we can try as I’ve made 100s of edits going back years and it would crushing to lose that.
NUC with ROCK als Core.
Version 2.0 (build 1137) earlyaccess
NUC with ROCK, Streaming Client, USB → DAC,
Version 2.0 (build 1133) production
remote: Android Phone, Samsung Galaxy FlipZ 3,
Version 2.0 (build 1133) production (“discover” doesn’t work")
and
remote Android, Samsung Galaxy Tab 7 FE,
Version 2.0 (build 1133) production (“discover” doesn’t work")
and
remote Windows 10, 64bit,
Version 2.0 (build 1133) production (“discover” doesn’t work")