>> Like I said at the start of my thread, where composer data has been >> entered, it's very inconsistent. > >thats a different argument. its one thing to say "no composer tag at >all" and another to say inaccurate tags. > "where data HAS been entered". Usually, I find that composer is not entered for popular music in these metadata sources. When it is present, it's inconsistent. I think there's one metadata source that puts the original artist/composer in the ENSEMBLE tag. Tagging/metadata sources are a mess, especially seeing many are at the mercy of submissions/updates from users.
It's a bit irrelevant whether users get tags untreated from metadata sources, or enter their own metadata. I was merely offering an alternative; not suggesting that people had to tag like that. i.e. if you browse an artist, you see everything that the artist has involvement with. I have raised several enhancement requests in the past suggesting that more control over this may be useful, just as is being suggested in this thread. For example, I'd quite like the view of albums relating to an artist to be grouped by involvement type, so you'd see main albums for an artist, then compilations the artist appears on, then where he's a composer, conductor, etc. Logitech appear to have no interest in making such improvements; most enhancements for ways of browsing music have sat unassigned for many years with no target. My point was that if a user doesn't want to see albums where an artist was a composer on someone else's album, don't add the composer tag to such albums. For the albums where they may want to see such albums appear, do add the composer tag. There is no choice with that part. Instead of losing the information totally, pop the original artist into another tag, such as ORIGARTIST, and use CustomBrowse to view and browse you music library, with more control over what is displayed. For users that rip & tag using metadata sources that do sometimes provide composer tags, and don't review/fix their tags, they will likely find their browsing experience somewhat of a let down. Because the metadata sources are not consistent with how the content of the composer tag is entered. >SBS isn't designed for what YOU do. I really don't understand you. I never said it was; I've tailored it to suit my needs, and I try to share knowledge such that it may be useful for others. Just in case you are unaware, SBS isn't designed for what YOU do/want either. >SBS should be designed, to the extent it can be, to handle what vast >marketshare apps do by default. > Which makes me laugh, because there isn't a one solution fits all; you should know that by now. It's flexibility that allows the user to adapt the software/tags to get the most out of it. No music browsing app will ever be perfect to everyone. Each "vast marketshare app" does things differently, to some degree, because there is no standard way to represent music, and thus no standard way to browse it. >a vote? are you serious? you want a vote of a tiny skewed pool of >forum users? how about COMMON SENSE? Come on! Of course I wasn't serious. Like I said, I wasn't interested, but I thought you might be... I'm always against futile voting, because a forum does not have a representative audience. >if i tell you that all the major marketshare apps do it this way, what >percentage of folks do you think >bother to EVER even look at composer tags??? I would think a percentage closely approaching 0, which is why I suggest removing the data tag if it doesn't have the desired effect when browsing the music library (or rather moving it to another tag for safe keeping). _______________________________________________ beta mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/beta
