Genre Delimiters - changed behaviour

[Tunesly]

App version

Production

Issue description

I’ve been using Symfonium, served to by Navidrome, for several months now and found it generally perfect However, sometime in the past few months (not sure exactly when sorry) behaviour changed around genre tag delimiters and splitting.

In Navidrome I have a custom override on the genre tag so that it does not recognise any tag splitting delimiters and treats the entry as a single string.
In navidrome.toml: Tags.Genre.Split =

My genre tags make use of commas (“,”) that I don’t want split, just treated as one string.

Symfonium was respecting this well, but now when I navigate to Library > Genres, any genre that includes a comma is not listed at all (screenshot attached).

If I navigate to Library > Album Artists, I see every artist listed with the genre below as a single string, including the genres that do not show up on the genre page (screeshot attached).

Symfonium has always split at the commas (for me) when viewing an artist page (screenshot attached: “60s” • “70s & 80s” - from “60s, 70s & 80s”) but I was happy to live with that. I primarily use genres to navigate when selecting music so when entire genres are missing from the selectable options in Library > Genres it makes it difficult.

Is this a setting I have missed in Symfonium, something I am doing wrong in Navidrome or has there been a change in how Symfonium manages commas in tags?

In the docs all I see on this is:

Separators
To support older tags and multiple values entered as single values, some separators are applied to the data.
Those separators can be configured in the provider settings too.

Happy to accept limitations (commas in tags may not be the best choice), it was the completely missing genres that struck me as odd.

Thanks

Device type

Phone

Media provider

Navidrome

Steps to reproduce

1. Have commas in Genre tags served with no delimiter for splitting the tag.
2. Navigate to Library → Genres
3. Observe Genres that include commas not being displayed.

Screenshots

I searched existing issues first

on

I understand that logs are mandatory

on

Log upload name / description

Tunesly - Genre Delimiters - changed behaviour

[Tolriq]

As all the similar issues, Symfonium displays the data that Navidrome sends and have no access to tags.

You need to see what changed there.

[Tunesly]

Thanks for the quick response.

This is confusing to me because the genres that include commas are clearly being received by Symfonium during certain API calls to Navidrome (getArtist?, getAlbum?) but those same genres are not being displayed at all in the Library > Genres view.

I’m not a developer by any stretch and I’m not sure what’s going on behind the scenes in Symfonium, but I’d like to understand if it is a Navidrome configuration issue so I can refine my settings. It’s the inconsistent results in Symfonium that have me confused.

I’ve tested Navidrome API endpoints directly using getArtist, getAlbum & getGenres both “genre” and “genres” tags and every output I get shows Navidrome serving all genres with/without commas as single, complete strings.

API test commands used:
curl “${NAVIDROME_URL}/rest/getGenres?u=${USERNAME}&p=${PASSWORD}&v=1.16.1&c=test&f=json” | jq ‘.’

curl “${NAVIDROME_URL}/rest/getArtist?id=${ARTIST_ID}&u=${USERNAME}&p=${PASSWORD}&v=1.16.1&c=test&f=json” | jq ‘.[“subsonic-response”].artist.album[0] | {genre, genres}’

curl “${NAVIDROME_URL}/rest/getAlbum?id=${ALBUM_ID}&u=${USERNAME}&p=${PASSWORD}&v=1.16.1&c=test&f=json” | jq ‘.[“subsonic-response”].album | {genre, genres}’

It seems like the same API data is parsed correctly in one view but incorrectly, or being dropped completely, in other views. Wouldn’t this be through internal handling within Symfonium?

Apologies for going on about it, I realise it’s not your job to help me get my setup working correctly, but if you’re able to point in any direction about calls that Symonium might be making to Navidrome that are ecliting varying results so I can understand what’s occuring and fix it, that would be appreciated.

If not, thanks anyway, you’ve got a killer app and great support.

[Tolriq]

Only other reason is the remove empty content on the settings that will delete genre without content, but nothing have changed about that.

In all cases, yes using , in genre is not the best anyway.

[Tunesly]

Thanks, this got me back to where I was.

Turning the “remove empty content” setting off (Settings > Advance > Database > Remove empty albums, artists and genres), clearing the scraped data in the provider settings and running a full sync has the “missing” genres now displaying. Those genres aren’t empty though, they have many artists in them.

Symfonium is parsing the commas as a delimiter in some cases, which is shown on the artist pages, even though the calls to Navidrome API are providing them as a single complete string. This must be why it considers the genres empty when they are not.

At least I understand what is happening now. Thanks!