[unfaesed]

@DaveBlake I get what your saying, trying to get two different systems to work together, past history, everybody wanting to do it there way and why won't it just work? Sounds like the story of the human race.


@DaveBlake wrote

Would love to provide a filtering facility as rich (or richer) than Foobar, however the 10ft/controlled by TV remote GUI of Kodi makes that much harder to present to the user nicely. As a data guy I want to empower the user to all the clever filtering a relational db can do, but the UI side is hard within current (and ancient) Kodi GUI engine components.

I don't quite get this bit however. Kodi already uses tag fields and rule/filter fields (could you not just add more to each list). It just means the list/s you scroll through with your remote is/are longer. Or do I not understand this?


@DaveBlake wrote

One non-standard (e.g. not in the Id3 v2.4 tag standard or commonly used) tag that Kodi does process from scanning tags from music files is RELEASETYPE/TXXX:MusicBrainz Album Type (eg. album, single, ep, compilation, soundtrack etc). This is stored for albums and referred to in Kodi as type (the name releasetype was already being used for something else).

Yes I had considered that, give up on release status and put Bootleg under releasetype (I walked away in frustration when I discovered that <rule field="releasestatus" didn't work). My object was to get away from bastardised tags (instead I'd just be exchanging one method for another). Don't think that I've given up however, I shall keep on playing around with it all.

Cheers