This release brings an experimental Jellyfin Music API, so Jellyfin-compatible music clients like Finamp and Jellify can now connect to Navidrome. Artwork got a new background pipeline with blurred low-quality placeholders and a diagnostic CLI. Under the hood, all IDs move to a uniform canonical 128-bit format, genre and artist filtering is now index-backed, and playlist import on large libraries is dramatically faster. There is also natural sort order, playlist favourites, Refresh Metadata actions, new Catppuccin themes, and many fixes across scanning, transcoding and scrobbling.

⚠️ Breaking Changes / Migration Notes

• All internal IDs are re-encoded to a single canonical 128-bit base62 format. The migration touches every table, so back up your database before upgrading. Clients that cache item IDs (for example, offline downloads) may need to re-sync. (#5824)
• Plugin authors: Extism's built-in HTTP is disabled. Calls through pdk.NewHTTPRequest (Go), http::request (Rust) or the equivalent in other PDKs now fail with HTTP request ... is not allowed. Plugins must use the host HTTP service instead: host.HTTPSend (Go) or nd_pdk::host::http::send (Rust). Also, plugin HTTP and WebSocket connections to private or loopback addresses are now blocked for named hosts; to reach a LAN service, list its IP or CIDR in the manifest's requiredHosts, or use a bare "*". (1a8463f7d, 276d767ce)
• Shares are always owned by the user who creates them. Admins can no longer create shares on behalf of another user via userId. (1a8463f7d)
• Configuration durations are now validated. Negative values are rejected at startup. (#6002)
• Navidrome now warns about unrecognized options in the config file, so typos no longer fail silently. (#5870)

Why is an advert, albeit an advert for shareware, appearing in an artist bio on #navidrome 🤔 (Firefox on MacOS)
#music #server #Linux @navidrome @navidrome

I have transcoding enabled in navidrome and tempus..it was all good for the past year, but today I got this warning that I consumed all my data plan. I listened to one hour of my music and just like that, bam, 17GB gone.

Not my lucky day I guess.

cross-posted from: https://lemmy.world/post/50148512

Original post here [redlib link].

Written by deluan

The next release normalizes every ID in the database into a single format. It runs a one-time migration on first start. The PR with this change will be merged this weekend: https://github.com/navidrome/navidrome/pull/5824

If you run develop or auto-update, this lands soon (this weekend) and without warning. Make a backup of navidrome.db now. The migration is one-way, so rolling back (if needed) means restoring that backup.

The short version:

• Takes ~30s to ~1m20s on my 96k-track library (QNAP Celeron). Scales with library size.
• Everyone gets logged out once. Web UI and clients using the Navidrome API need to log in again. Subsonic clients authenticate per request, so they are unaffected.
• Song IDs change, album and artist IDs do not. Clients that cache song IDs (offline downloads, cached playlists) may need a re-sync.
• Cover art gets re-fetched, so the first browse after upgrading is slower.
• Share links keep working.
• Nothing is lost: favorites, ratings, play counts, bookmarks, play queues, scrobble history and Last.fm / ListenBrainz links all survive. No rescan needed.
• One manual fix: .nsp smart playlists using inPlaylist or notInPlaylist keep the old playlist ID on disk and need updating by hand.

Full write-up: https://gist.github.com/deluan/917ebc243c8b486101de857ffae6739b

If you can, please test it with your favourite client once it is merged, and reply here (or on our Discord) if anything looks off.

EDIT: For app/client developers: I'll merge the topSongsByArtistId PR at the same time as this ID migration. This means that you'll be able to detect if a server is migrated by checking the getOpenSubsonicExtensions response and looking for the topSongsByArtistId extension.

When do the updates for "number of plays" or "last played" happen? With some testing, it doesn't appear to happen immediately.

I noticed that for some time (a month or so) whenever I add a new artist and upload artist.jpg in the artist folder, I still get the default star image.

I'm running Navidrome on docker, I'm on version 0.61.2 (aa84e645) and I have set ArtistArtPriority = "artist.*". My artist.jpg images don't exceed 800px and are not large files, if that would matter.

Setting the log level to debug didn't show me anything relevant, when going to an artist page on Navidrome web client or the Android client I'm using.

Any ideas for how to find a solution to this?

#navidrome

I’ve tried some Navidrome for iOS, which are not hugely numerous, and until now I thought Arpeggi was the best one until I discovered Narjo. You should really try it, as it hugely rich in features, highly customisable both in functionalities and in user interface and it load datas way better than Arpeggi

I've been noticing demo.navidrome.org showing up in my firewall:

pFsense:

abuseipdb.com:

As with anything entering or exiting my network, I am cautious and curious why my instance of Navidrome has the need to contact demo.navidrome.org.

I am running Navidrome as a Docker Instance. I have combed my compose file and can find nothing in that itself that would trigger Navidrome to 'call home'.

Is this for stats, or other? As of right now, I have demo.navidrome.org blocked until I've gathered some information.

BTW, sweet piece of opensource software. I tip my hat to the dev team(s).

I am excited to have found #Navidrome But it's apparently SO good that I am wondering if it's at risk of being corporatized after I've committed to building my offline system around it 🤔
#music #server #Linux @navidrome

cross-posted from: https://programming.dev/post/45423765