Roon 2.60 build 1649 unable to enable local audio zones (ref#FYR97P)

Hi! What’s not quite right with Roon?

· None of the above quite fits

None of the above quite fits

· None of these quite match

Tell us what's going on

· After update to 2.60 build 1649 on Windows, Roon no longer recognizes my local audio zones (on my PC). Trying to enable these zones (local System Output and my USB connected DAC via WASAPI (Schiit)) just gets stuck on "enabling". No firewall or other changes have been made and these zones have been working for years since. Other zones in the local network still function fine and play music. Truly baffling

Tell us about your home network

· VPNs have been disconnected and turned off. The zone previously worked with VPNs anyways.

I will add that my PC and roon server are on the same network and both wired into my router directly. There are no firewall rules prohibiting connection between them. I can connect to the server just fine and play to other network devices.

I would love to see if an older version of Roon will fix the problem. Can someone point me to a place where I can download an earlier build?

I have the same issue since tonight after updating to 2.60. All local audio zone are stuck on “enabling”. Server and remotes are all on 2.60.

I’m also having the issue with “Metadata Improver : Paused. Roon is having trouble verifying your connection to our servers."

Hopefully the two issues are connected and once the “metadata improver” issue will be fixed also the local audio zone will work again.

A post was merged into an existing topic: Connection Issues, Login Issues, “Metadata improver paused” errors, “Unexpected Error” messages [Roon Tracking] [See Service Alert Pinned Post]

@forgz - Is your Roon Server an earlier build than version 2.60? If so, then your issue is being caused by an incompatibility between Roon clients version 2.60 and earlier versions of Roon Server. See:

Roon Bridge 2.60 (build 1501) Production with EA Roon Server - Early Access - Roon Labs Community

Either update your Roon Server to version 2.60 (Production) or, if you are running Early Access builds of Roon Server, wait until Roon Labs release a new Early Access version. Roon Labs had hoped to release a new Early Access version last Friday, but it didn’t get through their QA testing apparently.

Hello @forgz ,

We wanted to check in with you since it’s been some time since your last reply, are you still seeing this issue on your end? Is there any change in behavior if you perform a full reboot of the Roon Server? You can try to perform a RAATServer refresh, this can sometimes help.

You can generate a new RAATServer instance on your device by following these instructions, but please be aware that this will reset your Roon Settings -> Audio Tab to factory settings and I would advise making a backup of any custom DSP settings you have:

  • Create a Backup of your current Roon database
  • Exit out of Roon
  • Navigate to your Roon’s Database Location
  • Find the folder that says “RAATServer”
  • Rename the “RAATServer” folder to “RAATServer_old”
  • Restart the Roon App to generate a new RAATServer folder

Let us know how this goes!

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.