Since I updated core new version, if i listen on a remote and then go back to listening on pc with core, i cannot get sound though at begining it was stil displaying pc…today, after a remote session, impossible to get any audio source: remote (zen ifi) disappeared, wasapi on pc and just pc : disappeared even after reboot of pc and roon indeed. back to foobar and really disappointed by the quality of new release !
You are running the Roon software on your Windows PC.
Roon OS is the operating system built by Roon Labs that is used on their Nucleus hardware, or on self-built Roon systems using Intel NUC hardware that have ROCK installed on them.
So when you are asking Roon to “Find Roon OS” in the Settings > Setup menu of Roon, it’s never going to find a Roon OS in your home network, because you don’t have Roon running on a Nucleus or an Intel NUC using ROCK.
in theory i won’t argue, just yesterday it was showing my pc in ‘Find Roon OS’…
so roon software is my core, right ? or have been since i’m using Roon so i cannot imagine what has changed.
before new update, i could switch between listening directly on pc (with core) or on my streamer (zen ifi)…since the release when i have listened remote, i could not get audio on software on my pc (it was fine after rebooting, but reboot + 5 mns to load roon is not really agile and is a bug for me) and now, i cannot listen with roon on my pc, i have to select an audio zone and it just see my avr which i don’t care, i don’t see wasapi on my pc neither my streamer)
As far as I can tell your core is on your PC and you appear to be logged in just fine. The only end point you have enabled is an AVR that you are streaming to via Airplay. Be aware that your enpoints must be turned on for Roon to see them. So if your ifi Zen is not on, it won’t show up in Roon. However, since your core is on a PC you should see several PC related outputs in the “Audio” page such as System Output and/or ASIO. It’s possible your update didn’t complete properly or was corrupted. I’ve never seen this happen, but Roon help will be along here soon so bear with.
Well for me, the update caused ROCK to lose access to Tidal. A quick logout/in again for the Tidal service in Roon fixed it, no drama. I think this has happened once before (track count drops by a few thousand on Home page, so is easily spotted).
One thing to note with PCs, rebooting them is often a cause of issues in Roon because Windows will often use the opportunity to install a bunch of updates. These do cause issue for Roon and its detection of connected devices sometimes. Windows can also reset its firewall settings for no apparent reason during a Windows update, causing Roon issues. It is a Windows issue when this happens, not a Roon one. Not defending Roon updates here, just stating that Windows PCs can be troublesome.
but it wont help, and just i can see is ‘effortless’…not really true
