That’s what a “Community” is about, or is just a cliche name…me think.
Peace,
Tony
I’ve just noticed something - Roon doesn’t shuffle more than 5000 tracks no matter how many are in a Tag! So this isn’t the same old Roon under the hood - it seems to have created a bigger problem than just the performance and reboot issues?
This kind of kills my main avenue of listening to Roon, which is to shuffle Tags. No I don’t need to listen to more than 5000 songs, but if there are 10,000 songs under a Tag, and Roon shuffles THE SAME 5000 songs every time, I never hear the other songs!
If it just plays a different selection of 5000 songs, I guess that probably then is OK. But how do we know?
This is not a network issue.
you are right about the “same 5000”, but this was already fixed in this release:
We never let you add more than a few thousand tracks to the queue, but having the ability to shuffle in more than 5000 tracks is an important use case, so we added this wacky shuffle “mode”, which was different than radio, and different to queue shuffle. It created a lot of confusion.
So, to solve this confusion, we decided to eliminate the confusing “shuffle mode” and just add tracks to the queue w/ shuffle on.
The problem is if you hit shuffle or play or something in more than a few thousand tracks, it’ll overload your queue. The solution was to do the shuffle algorithm up front and add the first 5000 tracks added to the queue, which should be about 4-6 days of music.
In the first 1.8 release, we had a bug where it truncated the list to 5000 and then shuffled. That gives you the buggy behavior you see, but it was fixed in the above release.
2 Likes
Not sure that I’m adding to the discussion but my 7i7 NUC runs Roon on top of Win10 continuously and I have not experienced any of these issues. My library is on a Synology NAS and has about 5000 albums of all different formats. I will not restart the NUC for usually a couple of months until I notice some Win updates on my other computers.
It must be terribly difficult for the Roon engineers to troubleshoot all the different configurations we all run. I can imagine that the log files only provide so much insight. I sure hope that you get a decent resolution to your issues.
I don’t have any of the delay or dropout problems that you’re describing. For me, Roon has been rock solid through any version, and certainly not with 1.7 or 1.8.
Did you have problems with previous versions or is this a new thing?
That’s great to know. Thank you.