View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0021880 | MMW 5 | Tagging / organizing (properties / auto-tools) | public | 2025-11-27 23:08 | 2025-12-04 23:01 |
| Reporter | rusty | Assigned To | |||
| Priority | urgent | Severity | major | Reproducibility | always |
| Status | resolved | Resolution | fixed | ||
| Product Version | 2024.2 | ||||
| Target Version | 2024.2.1 | Fixed in Version | 2024.2.1 | ||
| Summary | 0021880: Rating albums isn't immediate, and unexpectedly deletes track ratings | ||||
| Description | While testing 0019994, I noticed that: 1) As Petr indicated at 0019994:0071740, when the user changes the rating for an album, the album rating doesn't change. The user must click the artwork or refresh the view for the change to display. This is unexpected--the change should be reflected right away. 2) Changing the rating of an album causes all of the tracks on that album to be changed to the new rating. This is also unexpected. I might have expected that an album rating would be applied, but not that all of the tracks would be edited. | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 3300 | ||||
|
|
Re. 2) What I'm referring to is that when you right-click on an album (e.g. in Music > Albums [Grid]) and choose My Rating, it could be surprising to the user if all of the tracks are edited with the new rating. i.e. when multi-selecting tracks and editing in Properties (or via the Preview window) it's obvious that multiple tracks are going to be edited. But in the Album view, the user might think that the Album rating is going to be edited rather than individual track ratings. A simple solution would be to notify the user as in the Album Art dialeg. e.g. Apply to all files in the Album/Series ? (this is an existing string) [OK] [Cancel] |
|
|
Fixed in build 3300. I used standard existing dialog "Are you sure that you want to modify %d files ?" in case more than 1 file is going to be updated. This is more accurate and more in line with what is really happening, as such rating change is not bound only to one album, this possibility is also in other part of UI - users can change rating on any "icon" representing some group of tracks, like artist, genre or album, it is different from what "Apply to all files in the Album/Series" do. I think such way it makes sense. |
|
|
I agree with dialog but this still do not address issue when user wants to change only Album Rating not rating for all files in album, eg. When user loves the album generally and would like to rate it 5 stars so that he can use Album Rating in Auto playlists to list all Albums with 5 stars, but he still do not like 1 track from album as 5 stars but 3 stars or and wants to keep some of them unrated so that they do not popup on Auto Playlist of tracks with 5 stars? My solution from ~0080093 should resolve both and then it is only UI change eg. "If Album Rating is <101 then Album rating is auto calculated; else if Album Rating is (>999 and <1101) then It is Manual settings; else Recalculate Album rating;" |
|
|
But this would change the current basic logic and introduce new complications, inconsistencies, and confusion. For example, editing the properties of an album = editing the properties of all tracks in the album. If the user also changes the rating, should it update the rating for all tracks, or only the album rating? If it affects only the album rating, then how should the user change the rating of all tracks in the album at once? When clicking on "My Rating" for any artist - should that change the rating of all his/her tracks, or should it also change all related album ratings to manual? Or should we introduce artist ratings as well? And composer ratings? And genre ratings? Otherwise it would be inconsistent. How would we return an album rating back to being averaged automatically? Also, changing the rating of a single track will affect the rating of the whole album. But if the album has a manual rating, it would not change, which could be really confusing. If we decide to change this logic, it is also necessary to consider how it affects related logic in other parts of the application. For me, keeping the average makes the most sense and is the most consistent approach. By the way, if a user really likes an album but dislikes one song on it, then the album cannot truly be a "5-star" album, since it contains a weaker track. Assigning this to Rusty to think about. Anyway, nothing to change in the 2024.2 versions. |
|
|
The original reason for the issue is resolved, so I'm tagging this as resolved. Peke, if you think that we need to re-introduce the old Album-rating feature, then that would be a separate issue. BUT I agree with Michal that this probably doesn't make sense any longer given how MM works. |
