by Barry4679 » Mon Aug 31, 2020 9:51 pm
thanks for response
rusty wrote: ↑Mon Aug 31, 2020 1:40 pm
Re. the fact that Summary isn't configurable: I agree that it should be--it's just something that we deferred because it would be different depending on both conent Type and View.
Re. the ability to (re)configure sort order from/on non-displayed fields, you can do so by configuring the View (rather than sorting within the view). This approach was taken for Views in which fields aren't displayed.
Ok, but was an unfortunate choice IMO ... there is already a mechanism for handling differences due to different content type, ie. as deployed for the Track Summary column ... and I don't understand why changes of View creates complications ... ie. the column is either visible or not visible, and where is visible, can be served by a single layout config
My personal view is that the underlying issue is probably that the MM design team doesn't seem to include people whose focus is upon Albums, rather than just collections of Tracks ... examples
- Album Artist is not a 1st class citizen in Browser view for Media Tree collections
- AlbumArtist column is default configured to be invisible for collections ... no way to alter this default
- no columns at track level for consensus album_play_count or date_last_played_for_album ... so no way to create an autoplaylist to queue whole albums, where the criteria includes factors like "album I have played < 3 times" or "album I have not heard for a year"
- "Top 10 Albums Played" in the Library Statistic Report is sequenced from a Track Players' POV ... ie something like sum of (track duration * play count), rather than being sequenced by album play count
- grid footer summary shows stats for number of tracks, total duration and total megabytes, but not number of albums
- and the situation is worse in MMA ... can explain if you are interested .. I have MMA, but don't use it, because tools like Bubble UPnP, are better for Album focused people
rusty wrote: ↑Mon Aug 31, 2020 1:40 pm
Re. the 'Summary' column appearing/disappearing, it appears whenever the user chooses a view that's grouped 'by Album'. This approach (forcing UI elements related to Grouping when Grouping is enabled), but there's a lot of room to improve the manner in which grouping (and Views) is configured.
My point was that if I have the album grid set to be sorted by Release Date, you could presume that I am interested in this info ... but you don't display the date for me, and I can't adjust the configuration.
I agree that there is room for improvement in the column appearing|disappearing behaviour (vs being enabled|disabled) in the various config dboxes.
My overall view is that I am very pleased with the many improvements in MM5, but am disappointed that MM has still has limited utility for an album focused collector|listener.
thanks for response
[quote=rusty post_id=472221 time=1598899222 user_id=182]
Re. the fact that Summary isn't configurable: I agree that it should be--it's just something that we deferred because it would be different depending on both conent Type and View.
Re. the ability to (re)configure sort order from/on non-displayed fields, you can do so by configuring the View (rather than sorting within the view). This approach was taken for Views in which fields aren't displayed.
[/quote]
Ok, but was an unfortunate choice IMO ... there is already a mechanism for handling differences due to different content type, ie. as deployed for the Track Summary column ... and I don't understand why changes of View creates complications ... ie. the column is either visible or not visible, and where is visible, can be served by a single layout config
My personal view is that the underlying issue is probably that the MM design team doesn't seem to include people whose focus is upon Albums, rather than just collections of Tracks ... examples
[list]Album Artist is not a 1st class citizen in Browser view for Media Tree collections [/list]
[list]AlbumArtist column is default configured to be invisible for collections ... no way to alter this default[/list]
[list]no columns at track level for consensus album_play_count or date_last_played_for_album ... so no way to create an autoplaylist to queue whole albums, where the criteria includes factors like "album I have played < 3 times" or "album I have not heard for a year" [/list]
[list]"Top 10 Albums Played" in the Library Statistic Report is sequenced from a Track Players' POV ... ie something like sum of (track duration * play count), rather than being sequenced by album play count[/list]
[list]grid footer summary shows stats for number of tracks, total duration and total megabytes, but not number of albums[/list]
[list]and the situation is worse in MMA ... can explain if you are interested .. I have MMA, but don't use it, because tools like Bubble UPnP, are better for Album focused people[/list]
[quote=rusty post_id=472221 time=1598899222 user_id=182]
Re. the 'Summary' column appearing/disappearing, it appears whenever the user chooses a view that's grouped 'by Album'. This approach (forcing UI elements related to Grouping when Grouping is enabled), but there's a lot of room to improve the manner in which grouping (and Views) is configured.
[/quote]
My point was that if I have the album grid set to be sorted by Release Date, you could presume that I am interested in this info ... but you don't display the date for me, and I can't adjust the configuration.
I agree that there is room for improvement in the column appearing|disappearing behaviour (vs being enabled|disabled) in the various config dboxes.
My overall view is that I am very pleased with the many improvements in MM5, but am disappointed that MM has still has limited utility for an album focused collector|listener.
