The Roon team has prepared a fix for this issue. It’s currently undergoing testing in the #earlyaccess testing group.
You can migrate your server and remotes to the Early Access branch to try the fix if you follow these instructions:
Alternatively you can wait for the next Roon update, which will also contain the fix after it’s been tested in #earlyaccess.
If you keep an eye on the tracking thread shared in the post above, you’ll see announcements from the team related to this issue moving forward. We’re going to close this report so that all responses stay in the same place. Please post in the tracking thread moving forward if you’d like to share updates after trying the fix.
What @Carl has posted is exactly the right info to catch up on! We should have a fix for you included in our next few Roon updates - we appreciate your ongoing patience in the meantime!
To ensure that all users have visibility on the main tracking thread and to keep responses/updates in a single place, we’re going to close this thread and instead reference the main tracking thread moving forward:
As others have mentioned above, there is a test fix for this issue available in the Early Access section. You can follow the instructions in the post above to move your Roon devices to the Early Access branch to try the fix. Alternatively, you can simply wait until the next Roon update (forthcoming shortly) which will also contain the fix.
This thread will now close for inactivity - please respond with any questions in the main tracking thread above and we’ll continue from there. Thanks!