Same song repeats despite skipping and preferences (ref#HQH1WC)[Ticket in]

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

· i had the same song play repeatedly (perhaps 10 times), even after skipping multiple times, stating 'i do not like this track'

Tell us about your home network

· BGW 320; netgear 5-port gigabit ethernet unmanaged switch

Hey @terry_castillo

Thanks for performing that test, we have added this info to the investigation ticket. The ticket has been submitted for developer review, meaning that this may take some time to be reviewed.

There aren’t any additional details needed at this time, so we will go ahead and close the thread for the time being, and if any other questions arise after the developers have reviewed the case, we will re-open the thread and reach out once more.

Thanks again for your report, and thank you in advance for your patience as the ticket progresses through the development queue for review.

this sort of thing happens routinely. not exactly the same song, but definitely songs from the same album, even after i’ve skipped and stated that i do not like. it creates a terrible streaming experience…especially when we’re hoping for a good music discovery tool.

Hi @terry_castillo,

Thanks for the follow-up! As mentioned by Vadim, our team has a ticket in to improve this behavior, which will eventually be included in a future Roon update.

We very much appreciate your ongoing patience in the meantime! :folded_hands:

i recently submitted a ticket for a similar problem, and was assured the matter would be worked on…

i’ve now had a long series of oddly selected repeating songs. There was a series of 32+ Pink Floyd songs that were - inexplicably - played after my Memphis Soul songs.

@terry_castillo, your original support request has auto-closed because there are no updates.

However, the status has changed to [Ticket In]< which means it is with the development. Roon will update the thread when there is news.

Hello @terry_castillo ,

I know it’s been some time since we last spoke, but I wanted to reach out to you since the team has been looking into your report further. We’ve just enabled an additional diagnostics mode for your account, can we kindly ask that you reboot your Roon Server twice , reproduce the issue again, and let us know the exact local time + date + track/album when you next experience this behavior? Once we have that information, we’ll review the diagnostics and pass them to our dev team for further processing, thank you!

this has happened a few times in the last few days. i do not have exact dates and times, but i believe these screenshots were captured yesterday afternoon. (this is just the most recent two instances…and i can’t capture the entire length of the items i kept skpping)

Hey @terry_castillo,

Sorry you’re still experiencing this issue after all this time!

We can clearly see the underlying issue is tied to Roon Radio. Roon Radio seeded a “swim” session, and the recommendation graph kept returning the same small pool of closely-related tracks.

Your skips register as feedback calls to the cloud service (I can see the POST …/feedback events fire right when you skip), and “I don’t like this” registers as [banned] skips, but the next-item picks kept landing back in the same neighborhood.

There are also a couple of session-health warnings worth noting: failed to init swim session: FailedSeedNotFound and reinitializing because session was lost, which suggests the Radio session occasionally drops and re-seeds from the most-recent track, which can restart the same cluster.

Some more troubleshooting steps to try in the meantime:

  • Re-seed Radio deliberately. Start Radio from a different seed (a different artist/track than Hand Habits) rather than letting it continue an existing session. The FailedSeedNotFound/session was lost entries suggest the current session state may be stale.
  • Use the ban/dislike at the right level. In Roon, "I don't like this track" only bans that track; Radio can still pull adjacent songs by the same artist/album. If a whole cluster keeps recurring, banning the album or being less narrow with the seed helps more than per-track skips.
  • Clear history / restart the Server. Since this spans days and a session got "lost," a clean restart of the Server can flush the stuck Radio session.
Let’s also clear any stale cache just to be safe as well:
  • Exit out of Roon/RoonServer (from the taskbar)
  • Find and open your Roon database
  • Navigate to /Library/RoonServer/Cache
  • Move the contents of the /Cache folder elsewhere, like your desktop
  • Try restarting Roon and verify if the issue still occurs

Our development team is still digging into this further, so we should have more information to share once that happens. Thank you! :folded_hands:

Hi @terry_castillo,

If you’re able to recall, how specifically did you start Roon Radio when this last occurred?

Depending on settings, Roon Radio can start passively when the queue finishes, or actively by selecting “Start Radio” as a Play Action on an object in Roon (a seed track, album, artist, or playlist).

We do have a fix forthcoming that prevents Banned tracks from playing during Shuffle playback, but that would be independent of Roon Radio. We still have ongoing reports of Banned content playing during Roon Radio sessions (like this report), and we are actively investigating with developers.

Hi @terry_castillo,

Our QA team would like to ask for your assistance pinning down this problem. We have enabled some verbose logging for your account.

If you’re willing to help out, simply reboot your Roon Server twice to enable the logging, and then attempt to reproduce this problem with Banned tracks appearing in the queue.

Please let us know specifically how you started playback (the artist/album/track/page, etc., as well as the Play Action).

We’ll watch for your reply. Thank you!

Hi @terry_castillo,

We’re reaching out once more to see if you were willing to enable some verbose logging on your account; we’re proceeding with some additional analysis and testing for affected users and wanted to include you.

Please simply reboot your RoonServer twice (you may have already done so by this point), and we’ll be able to access the additional logging we need. Thank you!

Hi @terry_castillo,

Have you encountered any Banned tracks during Shuffle play in the last few weeks? If so, we will merge your report into the main tracking thread here:

Otherwise, we’ll close this thread due to inactivity. Thank you!