Wow, this topic really does get people going, doesn't it! The thing is, there really isn't any need for consensus to be reached on exactly how to use the tags (especially that most contentious of all, ARTIST!).
All we need is a system which allows us to use a variety of tags in a flexible way - then we can all be happy. This was more-or-less what I tried to do two years ago in writing a bunch of enhancement requests (2696 to 2701), though I guess my thinking may have moved on a little since then. Feel free to add your votes to the considerable total there already. To be happy, we need: (1) the ability to use a wider variety of tags, as fully participating entities in the database (ie not using the rather odd "contributor" model within the database today). Possibly a standardised list like COMPOSER/CONDUCTOR/PERFORMER/BAND/OPUS/WORK etc, maybe with the option to define your own. Yes, I know you can kind of do this with Custom Scan but you are limited with what you can do as this is a plugin and not integral to the server software (2) having got the tags in, you want to be able to use the data for browsing, displaying and especially searching (please don't get me started on the half-baked "advanced" search that we have at the moment!!). For browsing that means a multi-level browse of tags in an arbitrary sequence (rather like the filtering options that you get in some online shops). For searching that means being able to search for arbitrary combinations of (partial) values in any combination of tags. I'd want to be able to do most of that from both the remote UI and the web interface, BTW. (3) optionally (though it may not be necessary given the above), there is the idea floated in this thread of having a setting somewhere that allows you to declare which tag you want to be used for ARTIST, ALBUM etc - though I think I prefer Robin's idea of fixing this in the tags themselves. Now, if we had all that we wouldn't need to debate how to use ARTIST because you could use it how you like. But this really has to be done in the server itself, not in plugins, as it requires changes to the database. erland's plugins are very clever but are inherently limited by the way they have to be implemented. </rant> Ceejay -- ceejay ------------------------------------------------------------------------ ceejay's Profile: http://forums.slimdevices.com/member.php?userid=148 View this thread: http://forums.slimdevices.com/showthread.php?t=43851 _______________________________________________ ripping mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/ripping
