We appreciate the offer; this should actually be released to Early Access quite soon, although we don’t have an exact timeline at this point. We’ll reach out here once the fix is public so you can test it out. At this time, the broken shuffle logic for Play All is technically still in the public build, but we’re glad to hear it’s infrequent.
Does your offer to test this for us still stand? We’ve enabled some verbose logging for your account and we’d like to request that you try to catch Shuffle playing Banned tracks red-handed. This will help our team ensure that the fix we’re preparing is exhaustive.
If you’d like to help out, you’ll need to reboot your Roon Server two times in order to activate the new logging.
We’ll watch for your reply. Thank you again.
Hi @Stewart_Wood,
The team is preparing a fix for this issue, but in order to be sure it’s thorough and completely prevents this condition, we’re requesting users who reported it to try to reproduce the problem once more.
If you’re willing to help out, you’ll simply need to reboot your Roon Server machine twice and then play My Tracks → Shuffle to try to see if Banned content appears in the queue.
If you’re not eager to deal with this problem anymore, then no worries; you can simply wait for the fix to be released into an upcoming Roon release once it’s been finalized. We will notify you here when that occurs at a future date.
We’ll watch for your reply. Thank you!
Sure I can Help, Connor. A question; With reboot you mean a software restart or switch of my NUC twice? Just to be sure I will do it right. Next friday morning CET I have time to support. Just tell me what you want me to do.
Is this helpful?
Marten
Hey @Marten_van_Heusden,
You only need to reboot the Roon Server software twice for this. Thanks again!
Just did, and started shuffle play on all tracks. I’ll report back.
I have not experienced the issue the past two hours. Looks like e erything works just fine. Shoul I experience it again in the future I will let you know.
Thanks, @Marten_van_Heusden. The mechanism remains in the wild on the production build, so we’re going to keep logging enabled for now.
If we should happen to ship the fix before you see the issue again, we’ll mark this resolved in the background.
Hi everyone,
Re-opening this thread to make sure we have a place to report Banned tracks that popped up via Shuffle play in Roon.
So everyone is aware of the status:
Banned tracks are not meant to queue automatically via Shuffle on Roon browser pages. This maintains feature parity with Roon Radio, which also omits Banned tracks. Banned tracks are only playable via a direct Play Action on the banned track object itself.
However, Banned tracks will occasionally still queue under Shuffle in the Artist/Album/Track/Playlist browser. We’ve added verbose logging in the latest builds to pin down the exact mechanism and add a block.
Hi @Stewart_Wood,
Checking in here since we have verbose logging still enabled. Have you encountered any Banned tracks during Shuffle play in the last few weeks?
Hi Connor,
I have not experienced it for quite a while now. With 13k banned and hidden tracks out of 86k I feel it is fixed.
Marten
Thanks @Marten_van_Heusden. Scanning the history of reports on Community, it’s not common for Ban-related issues to go dormant for even a few weeks of playback. We’ll keep this thread active until we can confirm it’s resolved to retain the full investigation history in one place.
We want to ping @Stewart_Wood and @terry_castillo (who separately reported this and related issues) one last time in case they’re still seeing Banned tracks come up in Shuffle play. Verbose logging remains enabled for your accounts, so if you encounter this bug, we’ll pin it down immediately in logs. Thank you!
Hi everyone,
We’re going to allow this thread to auto-close at this time in the absence of any new reports. This remains in the wild but incredibly intermittent. We are equipped now to pin it down once we have a fresh instance.
If you encounter erroneous plays of content you’ve banned in Roon, please report it here moving forward.
Thank you again!