[Bug]: ND_SCANNER_GENRESEPARATORS not working?

SkipperLappen commented 2 weeks ago

I confirm that:

[X] I have searched the existing open AND closed issues to see if an issue already exists for the bug I've encountered
[X] I'm using the latest version (your issue may have been fixed already)

Version

0.52.0 (92a98cd5)

Current Behavior

I have ND_SCANNER_GENRESEPARATORS set as ";." but my genres keep separating by "/"....i.e. "Techno (Peak / Time)" is split in two.

Expected Behavior

Not split by "/" when not specified in ND_SCANNER_GENRESEPARATORS

Steps To Reproduce

No response

Environment

- OS: Linux 6.1.79-Unraid x86_64
- Browser: Safari 17.4.1 (19618.1.15.11.14)
- Client: MacOS 14.4.1 (23E224)

How Navidrome is installed?

Binary (from downloads page)

Configuration

No response

Relevant log output

No response

Anything else?

No response

Code of Conduct

[X] I agree to follow Navidrome's Code of Conduct

deluan commented 2 weeks ago

Was this working for you in previous versions?
This config option is only applied at import/scan time. If you change its value, you will need to do a Full Scan for it to take effect. Have you done that?

SkipperLappen commented 2 weeks ago

Was this working for you in previous versions?

No, never worked for me.

This config option is only applied at import/scan time. If you change its value, you will need to do a Full Scan for it to take effect. Have you done that?

No, but will try that and get back to you

metalheim commented 2 weeks ago

Can you try adding a navidrome.toml configuration file and setting Scanner.GenreSeparators from there?

https://www.navidrome.org/docs/usage/configuration-options/#advanced-configuration

Im quite sure that this config option works for me as I added a bunch of Extra Genre seperators

certuna commented 1 week ago

I think this may be an upstream bug in TagLib - if I'm not mistaken, it always parses / as a genre separator in id3v2.3 and id3v2.4 even though it's against the specs.

Navidrome gets the genres as an array from TagLib, so if it splits the value upstream, there's nothing we can do, really.

I'll have to do some testing to verify this.

navidrome / navidrome