Bug 17031 - ENH: user defined strings could classify tracks as being Compilations [comps] to SBS
: ENH: user defined strings could classify tracks as being Compilations [comps]...
Status: NEW
Product: Logitech Media Server
Classification: Unclassified
Component: Scanner
: unspecified
: All All
: -- normal with 3 votes (vote)
: ---
Assigned To: Unassigned bug - please assign me!
: Compilations
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2011-03-06 07:07 UTC by Mike Walsh
Modified: 2011-03-06 07:21 UTC (History)
2 users (show)

See Also:
Category: Feature


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mike Walsh 2011-03-06 07:07:31 UTC
there are only two ways to classify something as a Comp [Compilation] to SBS:

1. add an explicit comp tag to your files, like TCMP=1 or Compilation=1
2. leave all the tags representing "album artist" blank on albums which otherwise have at least one "artist" tag mismatch.

both of those methods are fine for those users to whom they apply, but they are not a complete solution.  here's why:

taking #2 first, it is VERY important to note, that many, many apps ALWAYS assign an "album artist" value to the tags, Comp or not; such as WMP##, winamp, etc... as well as many tagging sources such as AMG and Gracenote.  that represents a very significant marketshare.

that means, for those users, the SBS VA auto-detection logic is USELESS, its defeated out of the box.  so, many users will come to SBS with files that are correctly tagged, but that SBS fails to classify properly as comps.  this will be confusing.  (and thanks to bug 9523 some will be hidden!)

now looking at #1, those same apps that created the files and put AA tags on everything typically do NOT read or write explicit comp tags!  comp tags are basically an itunes creation.  joe blow user will not want to get yet another app (like the geek techy mp3tag) that they then need to learn and configure just to set comp tags for sbs on their otherwise correctly tagged files.  (and even if they do add comp tags, some apps like winamp will later strip out unsupported frames if winamp updates the tag!)

the solution is to allow the user to define strings to SBS that SBS is then to recognize as meaning "this is a comp."  the option in the SBS settings would be very similar to "Guess Tag Format" (which works well when there is a pattern match).

so, just like "Guess Tag Format" a user could void the entries altogether if they wanted to defeat the feature; or they could define however many strings they wanted, such as "Various Artists" for SBS to recognize and use to classify whatever as a comp.  this way also lets users define strings in their own language.

i use many different AA strings, like for classical and soundtracks and so on, that indicate to me such and such is a comp.  i would like to be able to have SBS do the same.

and while i support bug 15604 and hope to see it implemented soon, it is not a full fix for bug 9523 / this bug, in that while AA VA items would reappear in home>artists, SBS itself would still not know what is a comp!  in other words, the point of this bug/feature enh, is to be able to classify things as comp whatever their AA value may be, (as per the user), and regardless of other bugs or issues.

finally, while i think it would be sensible to have at least "Various Artists" as the lone default entry in my proposed feature, i would also be fine with having it blank (i.e. defeated).

thank you.