If I drop a grouped zone or add one to a group, Roon momentarily says “Go Find Something to Play” and then when the Queue pops back in, it is reshuffled and includes tracks from above the currently playing track - skipped tracks and already played tracks are now shuffled back into the Queue.
Anyone else seeing this?
Yes. I am seeing this behaviour as well but triggered in a different way. I have no involvement in early access, or any wish to be involved, but by accident I learn that it is a known issue there. What I don’t know in the confusion is if roon are treating this as a production or early access issue:
This happened immediately after the production update. I don’t have early access.
I can’t believe more people aren’t seeing this…I guess people don’t modify their zone groupings as much as I do (really it is just PCs with Roon installed and configured as an endpoint, going on and off).
I have another Roon Server that I will try after work today. But I am going to try to avoid updating that one until this is resolved.
It’s truly evil. I have no control over the queue. Can’t use Roon that way!
I don’t have early access either. Very surprised a known bug like this affecting a central feature of roon’s working was allowed through into production.
Linking the EA thread for context and examples:
Well, but I don’t need support. I need Roon to fix what is now a known bug that is actually really quite severe. Support would indicate that the Roon team needs to look into my specific software instance. I don’t think they do. They need to roll out a bug fix across the install base.
I’m seeing the same. Well, actually what I noticed first was that albums I added after the upgrade had each song added twice.
I then thought ‘well, let’s see if restarting the server fixes it’, and when it came back I noticed that my hundreds-of-songs queue had gone through the blender. I’m not sure if that is tied to the server restart, I didn’t check the queue before restarting.
Analyzing and fixing a bug IS support. Roon Software Discussion is for, well, discussion, and Roon Labs doesn’t even read this section.
I’ll add a new thread under support…can’t find an existing one.
Edith: Created “Duplicate Album Additions and Queue Reordering Post-Update (ref#VAQ57U)”
This issue is being investigated by Roon see …
I know the report is in Early Access but I can confirm that Roon is very much aware that this has “escaped” into production.
I’d encourage people to read that topic and should it not encompass their personal experience / manifestation of the issue to provide additional datapoints (be that in that topic or by creating a specific support request.
I’d also like to clarify that discussion topics in Roon Software Discussion are not monitored by support.
