The search changes r definitely a big win! MUCH better than before and seems truly predictive for the 1st time. Still some sluggishness here and there but overall a win! Also server reboot time is better and I have large library of over 25k albums. Keep up the fixes! I still cant keep Arc going but thats a whole other problem!
I have the same issue. Nothing in artists, composers or tracks but albums are still there.
Perhaps this helps:
Changing browser sort view does seem to change the x of y album count issue
Yes, but once it does not let you switch to one particular sort, it can be difficult to get out of this state, so the sort option is unusable.
My point was that, at least for me, if it doesnât let me switch from, say Artist sort to Most Played sort, I can work around this by first scrolling down in Artist sort, and then switching to Most Played. Instead of trying the switch in the top scroll position.
Understood. I see a different stale state though. None of the sort options now work and album count shows 0 of 18529.
Same on iPad and iPhone.
Will reboot and see what comes back
Note 1 reboot restores a working state
Note 2: spoke too soon. Despite reboot, the client on win11 is still stuck at this
Reset doesnât function
IIRC, the container was running, but I couldnât connect because there was an outstanding update.
With regard to the âtry removing some focus criteriaâ and no albums being presented when using sort by date added with all focus criteria disabled:
- when connected to Roon server on ROCK: I do see the same when sorting with most recent at top; but with reverse order (earliest addition to library at top) everything seems ok.
- when connected to Roon / Roon Server on MacOS: everything seems ok, all albums are presented as expected, regardless of chosen sort order.
Itâs a little bit like Early Access has nudged into the old Alpha builds territory. Find the fundamentally broken things rather than confirming a ready to go build.
Perhaps it time to bring alpha back with the increased feedback that gave on things like installation instructions and impact on users.
But, IIRC, there was only Alpha and Production, no Beta, so no change there thenâŚ
Itâs true that there are major changes at the moment, so more chance of things going wrong when exposed to a larger group. But then thatâs what EA is for? I know itâs no comfort, but the build is working perfectly for me so far. Iâm just waiting for two backup issues to be fixed - I havenât been able to take a backup since the 12th of AprilâŚ
My apologies, I wasnât clear and it wasnât a complaint about the build quality. I think reinstating an alpha level would be a good idea before it gets to Early Access (EA)
It seems that there are quite technical things arriving in EA whereas itâs audience may include those that are therefore struggling a little.
I was thinking of keeping EA but adding a small alpha team for that day one testing.
Since the release on June 9th, the 2.70 1663 buildâs memory management has performed better than any release since March 2026, when I began tracking things.
Iâve not seen memory come down and remain flat like the screenshot above (taken at the time of this post). Nor have i seen the percentage of garbage collection pauses trend downwards before.
Before I installed this EA build, Roon displayed a message about updating the music libraryâs database. Iâm paraphrasing as the message was on the screen for a few seconds then disappeared.
Has anyone else seen such a message?
Hi, @ncpl, we have a fix for the browsers item count and display inconsistencies in #1665 EA build, the newest one, please, check it out and let us know if things are back to normal on your end.
If anyone else had an issue which looked like this or this, please check how #1665 EA build behaves as well.
Thanks!
â
Ivan
Hey @Dadoo -
Thanks for sharing the memory and GC profiling data. Thatâs exactly what I expected to see with these changes, and its particularly rewarding to see you experiencing it with all the effort youâve put into understanding whats going on.
Regarding the database updating message, that is a slightly misleading message that can appear with some new-content processing from streaming services (remove/add cycles or reclassifications), or new files discovered or rediscovered. I experience this on a pretty regular basis with the large+streaming libraries i am testing with - We just havenât had an opportunity to clean it up and disambiguate it from an actual DB update.
Cheers!
Steve
@Suedkiez are you experiencing this with the new 1665 version?
With this build, Iâve been running Roon with scheduled maintenance turned off and am now noticing how the search index is updated periodically.
These are the types of lines in the logs I am now seeing:
Trace: [music/searchindex] [search-index] added in 1226ms: 1 album documents, 11 track documents, 0 work documents, 4 performer documents, 0 genre documents, 0 label documents, 0 tag documents
Trace: [music/searchindex] [search-index] removed in 121ms: 1 album documents, 11 track documents, 0 work documents, 0 performer documents, 2 genre documents, 0 label documents, 0 tag documents
Does the search index update as the music library changes?
Trace: [library] finished with 11 dirty tracks 1 dirty albums 9 dirty performers 11 dirty works 11 dirty performances 3 dirty genres 0 clumping tracks, 0 clumping auxfiles 11 compute tracks, 0 deleted tracks, 11 tracks to (re)load, 0 tracks to retain, 0 auxfiles to (re)load, 0 auxfiles to retain, and 46 changed objects
It absolutely does!
I think Iâm all good, thanks:
@Steve_Becker any possibility this can finally be addressed?
Hi @DDPS - weâve received the ticket and it is in the queue, but I canât really comment on priority at the moment.