0002851: Album Art View: Albums must be grouped by Album+AlbumArtist - MantisBT

ID	Project	Category	View Status	Date Submitted	Last Update

0002851	MMW v4	Main Panel/Toolbars/Menus	public	2007-02-21 13:15	2008-11-26 06:00

Reporter	petr	Assigned To
Priority	urgent	Severity	minor	Reproducibility	always
Status	assigned	Resolution	reopened
Product Version	3.0

Summary	0002851: Album Art View: Albums must be grouped by Album+AlbumArtist
Description	Albums must be grouped by Album+AlbumArtist instead of Album+Artist.
Tags	No tags attached.

Fixed in build

petr 2007-02-21 13:15 developer ~0008623	solved

rusty 2007-02-27 20:02 administrator ~0008652 Last edited: 2007-04-12 21:12	This change is actually an incomplete fix since the problem is a bit more severe than originally described. The problem is essentially the same as that described in 1477, except that it's far worse in Album Art views because Album Art views can: a) predispose the user to view albums by _Album Artist_ (rather than Artist) -- this was partially resolved in the original fix b) make the user expect to see all the tracks on a given album when selecting an Album Artist -- this issue is still open for some cases To review the current situation: Track View ---------- Nodes: \|\| Result of selecting the node ------------------------------------------------------------------------------- Artist Node \|\| All tracks are displayed sorted by Artist as expected --<Artist> \|\| Tracks by Artist are displayed are displayed as expected --<Album Artist> \|\| Tracks by Album Artist are displayed UNLESS Album Artist \|= Track Artist (bug 1477) --<Album> \|\| Tracks on Album are displayed The above behaviour, makes it clear that d&d: -of a track from one Artist to Another, changes the Artist for the track (and the Album Artist if all tracks on the album are dragged) -of an album from one Artist to Another, changes the Album Artist (and the Artist if Album Artist=Artist) With a downside that in cases where an Album contains tracks by someone other than the Album Artist, that track doesn't appear in the list of tracks by the Album Artist (since if it were to appear, it would imply that the track is by the _Artist_). Album Art View -------------- Nodes: \|\| Result of selecting the node ------------------------------------------------------------------------------- Artist Node \|\| All Albums displayed sorted by Album Artist (previous bug fix) HOWEVER, the header shows that the sort is by Artist rather than Album Artist. Thus it's confusing where to find tracks for which Album Artist \|= Artist! ==>1) New Album Artist heading should be added ==>2) Default sort/grouping should be by Album Artist / Album --<Artist> \|\| Albums containing the Artist in question are displayed as expected --<Album Artist> \|\| Albums by the Album Artist are displayed but tracks for which Album Artist \|= Artist don't show up! This is very confusing in an Album Art view since the user expects all the tracks in the Album to appear. ==>3) See below --<Album> \|\| Tracks on Album are displayed correctly 3) A possible solution to this that wouldn't require the addition of a new node for Album Artist is as follows (this applies to both Track Views and Album Art Views): -'Artist' in the tree can represent both 'Artist' and 'Album Artist' -If the user selects an <Artist> node, then the Tracklist would return tracks where Artist or Album Artist = <Artist> -If the user wants to sort/group by <Artist> or <Album Artist> they just enable the relevant fields -If the user drags a track or an Album to a new Artist, a dialog appears asking: Select which fields you want to update with <Artist> ( ) Album Artist ( ) Track Artist (o) Album Artist and Track Artist [OK] [Cancel] It's debatable whether this dialog is required in all cases (e.g. if Album Artist=Track Artist).

rusty 2007-04-12 21:13 administrator ~0008992	Jiri, please review this. It's a fairly complex issue and may require a significant change.

jiri 2007-04-13 13:27 administrator ~0009000	As for 3), it probably makes sense to update Artist nodes to show both tracks where given artist is either Track Artist or Album Artist. (technically it's probably just about changing SQL in TreeManage.pas that reads content of Artist nodes - but be careful there, the SQL is also used in Device Configuration dialog and so its construction is a little more complex) As for the dialog, it's probably necessary to implement it and show upon d&d. However, I wouldn't show it in case all tracks being dragged have Track Artist=Album Artist.