Bugzilla – Bug 11369
Album sort order "artist, album" does not work for albums for which ALBUMARTIST is set
Last modified: 2011-11-06 23:23:32 UTC
When setting the album sort order in the settings of the controller to "artist, album" in the browse album menu the albums should be grouped by artist. However, this does not work for albums which are of a specific artist but on which some songs have "guest" artists. For example, I have an album of Akon which comprises a song of Akon and Zion. All songs are tagged with ARTIST=Akon except this one song which is tagged with ARTIST=Akon & Zion (I have & set as separator). To define this album as Akon album I have set ALBUMARTIST=Akon for all songs. While this album is correctly shown under artist Akon when browsing by artists it is not grouped to my other Akon albums when browsing by album. Instead it is sorted within the other Various Artists albums.
Steven to reproduce and assign
Moving to the product SqueezePlay because this bug appears to apply to any player based on that application code. Feel free to move it back if it's specific to the original product.
Need to investigate if this is a SqueezePlay issue or a SqueezeCenter issue. Changing to New Schema for now.
this bug sounds like it may be a dupe of this bug: bug 10760 i want to say that SBS has a fundamental design flaw. a user should NOT have to decide between whether or not the artist tag, or albumartist tag will fill out the SBS DB field of "artist" what instead should happen, is that BOTH tags are read and stored in the DB, and the user can then decide via the ui, which field they want to use to browse. (ie. "artist, year, album" would use the artist tag, while "albumartist, year, album" would use the AA tag. thats the only sensible way) the way things are today, i can NOT browse a list of all my artist tags in SBS, b/c all my tracks have AA tags on them. this is the way that WMP and winamp tag by default, AND the way they work best. SBS should stop trying to out-think the user or other apps, and instead get back to a "one for one" mapping style and allow the user to decide which tag to browse by. the current system is just ridiculously flawed and complex, especially where VA and comps are involved. comp logic shouldn't even be on by default, let alone mandatory!
> i want to say that SBS has a fundamental design flaw. A user should NOT have > to decide between whether or not the artist tag, or albumartist tag will fill > out the SBS DB field of "artist" > There isn't a fundamental design flaw. There isn't SBS DB field of "artist" - there are several "artist" fields, depending on the type of artist. They are scanned and held correctly in a well designed DB Schema. There are some inconsistencies between SqueezePlay and anything else (classic players, WebUI, etc), where SqueezePlay is inferior (should be changed to do the same as the other UI's). > what instead should happen, is that BOTH tags are read and stored in the DB > They are. > and the user can then decide via the ui, which field they want to use to > browse. (ie. "artist, year, album" would use the artist tag, while > "albumartist, year, album" would use the AA tag. thats the only sensible way) > No, that's not sensible. The sort order choice is about sorting albums, so it is only sensible to sort by album artist - that's what "artist" in this context means. How would an album be sorted by track artist if there are different track artists? It wouldn't make sense. And if you Browse Artists, it will list any artist record that you instruct it to list through settings. i.e. it is configurable whether to include/exclude Bands/Orchestra, Composer, Conductor or artists that only ever appear on albums as guests. > the way things are today, i can NOT browse a list of all my artist tags in SBS, > b/c all my tracks have AA tags on them. Yes you can - Browse Artists, with SBS configured to list all artists (includes track artists). > SBS should stop trying to out-think the user or other apps, and instead get > back to a "one for one" mapping style and allow the user to decide which tag to > browse by. the current system is just ridiculously flawed and complex, > especially where VA and comps are involved. comp logic shouldn't even be on by > default, let alone mandatory! > It's not - SBS is perfectly sensible. You should stop spamming multiple bug reports with your message, as it has very little to do with the bug reports.
Alan, i thought this might be inside the scope of onebrowser
Unassigned bugs cannot have a priority.