Roon build 1490 causes continuous playback issue (ref#KIIH1A)

What’s happening?

· Other

How can we help?

· None of the above

Other options

· Other

Describe the issue

Roon build 1490 installed today. After that, it won't stop playing. Continues to play even after app is shut down with task manager. Only way to stop the music is to reboot Windows 11 PC.

Describe your network setup

Not relevant I think since it all worked fine before 1490 update.

Hmm. I think I saw the same problem the other day - which would have been 1489 Early Access…

I wasn’t paying enough attention; I think I shut it down from the (Naim) streamer control app.

Thanks for the input.

I’m using my Windows 11 PC as the core server. In the zone there’s a Bryston BDP-3, WiiM Pro Plus and an USB connect to an integrated amp with digital inputs via an AISO driver. If you click/press the pause on any of these devices, including the Roon Remote on my phone, instead of stopping it moves to the next track in the queue. I have also tried the WiiM and Bryson apps and get the same result. Besides rebooting the PC, the only other way the music stops is if the queue is empty.
I have been using the setup for at least a year without any problems. It just started doing this today after the 1490 update.

A few more clues.

I can get the music to stop with a LONG press of the pause “button” on the Roon Remote app. Also stops via a click of the pause button from the server app IF you click and hold the mouse button for a second or so.

Apparently 1490 has somehow changed the sensitivity of the pause soft button. Kind of annoying but I can get it to work within the Roon software apps. External apps from Bryston and WiiM, along with the start/pause button on my PC keyboard, still don’t work and jump to the next song in the queue.

Not reproducible here I’m afraid for any combination I’ve tried; I don’t think I’m going to be much help! We’ll have to see what support come back with… :man_shrugging:

1 Like

thank you for trying.

1 Like

Hey @Jeff_C_EE,

Thanks for the report - it’s good to see you community again!

While our team takes a closer look and enables diagnostic mode for your Roon Server, lets see if refreshing your RAATSever database may 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

We’ll be on standby for your reply - thanks! :raised_hands:

And clicking Pause in the app does not work either? Asking because shutting down the GUI app has not stopped the music since the RoonServer has been made a separate process about 9 months ago - this is normal and on purpose.

Benjamin:

Thanks for the reply. I followed your instructions, but I did have to reboot the Windows PC to rename the RAATServer folder. Even though I exited Roon Windows would not rename claiming the folder was still in use.
Once renamed, I restarted Roon and a new RAATServer folder was created.
Unfortunately, the symptoms I have encountered since updating to 1490 today still exist. As noted later in this thread, I can get the music to stop within the Roon apps with a long press or extended mouse click on the pause button.

Suedkiez:

Thanks for the reply. Good to know that stopping the app doesn’t stop the music. I realized the original post was not very specific, so I added more info in later posts to this thread. The problem was first noticed when I couldn’t get the pause software button to stop the music. Clicking just advanced the music to the next track in the queue. As you read further in the thread, you’ll see where the issue now stands.

Got it, isn’t happening to me.

Benjamin:

You can close this ticket. This morning, I deleted the zone containing the 3 endpoints then rebuilt it. The rebuilt zone works fine. During earlier troubleshooting, I deleted the zone’s endpoints one at a time thinking I had a bad actor but that didn’t solve the problem. Rebuilding the zone did the trick. :+1:

Best
Jeff C

Jeff C

1 Like

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