If the cataloging and display of local artist images ends up working well, is there a chance that it could be incorporated into the base server, rather than a plugin? IMO, the ideal would be to make it a part of the standard library scanning.
I'm tempted to say no. IMHO the main code should be as lean as possible. I'd even be tempted to disable some of the default plugins. Because plugin authors should take care of their own code. (that includes me) We've seen many great contributions show up, which sooner or later were abandoned. If they had become part of the main code, everybody would nowadays point at me, because I'm the remaining maintainer.
I like the idea of using a single folder for all contributor images, but not if it means that album artwork would also be searched for in that folder. It might require a new artwork folder pref.
Sounds reasonable.
The scanner would also need to search for images for albumartist, composer (if they appear in the artist list - I don't remember) and any other tags from which contributors are compiled in the database.
The contributors table includes them all. I came to realize when I saw the plugin download images for artists I've never seen in my list, as they were only on some sampler. There's a contributors table, and a mapping of contributors and roles for every track (iirc).
You'll need to create and publish some standard rules for character substitutions of illegal characters in names so that a filename can be derived from all names. For instance, if I have the artist
And that's the big pain point in this. Typos, different spellings etc. can be a big pain in the but for this kind of job. That's why the artist.jpg in an album folder has its validity still...
-- Michael _______________________________________________ plugins mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/plugins
