Navidrome recently updated to “Big Refactor” indexing (Help test the next version of Navidrome (a.k.a BFR) · navidrome/navidrome · Discussion #3676 · GitHub) and I updated my server to 0.55.2 (latest) yesterday.
after a complete rebuild of the database, this introduced an issue with “Recently Added Albums” list, which now shows many albums that weren’t recently added on top. I found this issue on the web interface of ND and other apps. That brought me to search ND Github issues and find this was due to a recent change in the server ([Bug]: Recently Added - Random album order · Issue #3823 · navidrome/navidrome · GitHub). I changed the server setting as advised in the bug with RecentlyAddedByModTime = true
and that indeed solved the issue when I use ND web interface, Dsub app, Feishin desktop linux app - but for some reason, the issue still remains in Symfonium.
I tried adding the server as a “new” server to the media providers, but with no difference
Logs:
Upload description: Recently Added Albums show a lot of older albums after Navidrome update to 0.55
Additional information:
Reproduction steps:
upgrade Navidrome server from 0.54 to 0.55.2 (BFR major server update)
rescan entire database
sync Symonium to server
Duplicate of a few, nothing I can do on my side, it’s the data that Navidrome returns, and yes I know other apps using the dedicated endpoint that return different data without another way to get have the Navidrome workaround working but it’s irrelevant here.
Not necessarily. However, it won’t happen with future updates (or shouldn’t, unless there’s another big refactor). There is also the option (check the Navidrome website & documentation for details) to make navidrome use the old style of managing albums.
Personally, I would just leave it as it is now so you don’t run into issues later if that option gets deorecated, but it can be done if you feel that it must.
Some additional information and possible help for anyone coming after me:
As Tolriq mentioned, Symfonium does not call the dedicated Subsonic endpoint getAlbumList?type=newest. There are many reasons for this. The most obvious is that Symfonium supports aggregating data from multiple providers. As a result, the data for sorting albums by recently added has to be uniform so that Symfonium can sort albums across providers. Symfonium therefore cannot rely on one provider’s endpoint.
Instead, Symfonium seems to use the cache of scraped metadata to sort albums by created_at which, as of the refactor, seems inconsistent in navidrome. updated_at seems less broken but the Subsonic API getAlbum?id= does not expose that information. I wish that it did and I wish that Symfonium could then pull it and sort by that information as well but we are not yet there.
Setting RecentlyAddedByModTime = true in navidrome is irrelevant because, again, Symfonium does not use the getAlbumList?type=newest API.
To presently address the problem, I copied values for updated_at to created_at on my navidrome.dband re-synced Symfonium with the following SQL command: UPDATE album SET created_at = updated_at;
Remember to backup your database before trying this!
Hopefully navidrome will fix created_at at one day we’ll have updated_at exposed and integrated into Symfonium. For now, here’s a temporary fix.
This is with regards to Symfonium v13.5.0b (127586) and navidrome 0.58.0 (9dbe0c18). Thanks to Tolriq for the great applications centralizing control of so many different media sources!
