mayhem What I can do is re-work the lb content resolver to expose the de-tuning engine with a minimal set of requirements -- quite possibly 1 or 2 python libraries (unidecode is one). This way you can include the library without adding a lot more stuff to install
I'm not sure using the lb content resolver lib into funkwhale is a good approach. Different databases / would be easier for fw to have an approach that is not base on file directory. Also we wanted to have jspf resolver anyway for other things, so we need to write this code anyway. That's why I would implement this without the library.
If we want to use the lib we have either to make it more agnostic or we can fork it and change a few things. But this also represent work and maintenance
mayhem it would be better to not add content resolution to Troi
That's why I though also o/
mayhem So, the lookup process then goes like this:
Looks good ! I wouldn't spend too much energy to try to match to files that are wrongly tagged. I would prefer to focus on having a clean database than to have to work with a dirty one but I understand this can be usefull anyway o/ and detuning is interesting o/