View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0015226 | MMW 5 | Sync | public | 2018-11-29 11:15 | 2020-03-30 22:31 |
| Reporter | Ludek | Assigned To | |||
| Priority | urgent | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | reopened | ||
| Product Version | 5.0 | ||||
| Target Version | 5.0 | Fixed in Version | 5.0 | ||
| Summary | 0015226: Synchronize tags feature is confusing with regard to cloud tracks in MM library | ||||
| Description | The old 'Synchronize tags' appears in context menu for library tracks (be it local, cloud or cloud+local). This is confusing as users expect that using the feature on cloud tracks rather synchronizes track metadata between MM database and cloud database. I would suggest to either remove it from MM5 or make it available only for local tracks (not paired with cloud copy) and make it available only when Options > Library > Tags & Playlists > [x] Update tags when editing properties is unchecked. And it that case the terminology needs to be changed to understand what the feature is doing. | ||||
| Additional Information | http://www.mediamonkey.com/forum/viewtopic.php?f=30&t=90486&e=1&view=unread#p452822 | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 2199 | ||||
|
|
I think that the most confusing aspect of this feature is the word 'synchronize'. But if we change that word, we also need to change the 'Unsynchronized tags' node. Perhaps we can change it to 'Update tags' and the node name to 'Out-of-date tags'. As to hiding the functionality when it isn't relevant, I agree. i.e. show it only for Local/Networked tracks (not for UPnP, cloud, MMS). |
|
|
OK, I changed the terminology (+showing it only for local tracks) in 2140. But I think that the menu "Update tags" is still confusing for the library+cloud tracks (local tracks linked with a cloud location). So question is: shouldn't we remove this item from right-click menu entirely when Options > Library > Tags & Playlists > [x] Update tags when editing properties is checked? Or maybe better -- we could leave the item only for the tracks in the 'Out-of-date tags' node (where user can also see which tags are out-of-date), don't you think? |
|
|
Wouldn't removing the menu option in cases where it applies be even more confusing? i.e. if the user wants to update the tags for a track (whether that track has a copy in the cloud or not) it would be confusing if the menu option was unavailable. We might want to update the Tooltip to indicate 'Update tags of selected local or network-based tracks...' btw, the problem that you're describing is similar to the one we'd discussed regarding deletion of tracks at 0015209 (namely which track is the operation is intended to apply to). I suppose that in this case, the operation should apply to whichever tracks it's relevant for. i.e. any tracks that are local or network-based. |
|
|
I think that in case of the default choice: Options > Library > Tags & Playlists > [x] Update tags when editing properties there is no need for the "Update tags" menu item as the tags are _always_ automatically updated when editing properties, so the item does nothing (from the user perspective). So I guess that the only place where the item is really needed is in the 'Out-of-date tags' node, in that case the item should be the very first item (which isn't currently) ? BTW: I am testing MM4 and in MM4 the item "Synchronize tags" is only available in the "Unsynchronized tags" node, so what is the point of doing this differently in MM5 ? |
|
|
Unified with MM4 in the build 2140. |
|
|
Re-opened: Users have no idea what the "Out-of-date tags" node means, see: https://www.mediamonkey.com/forum/viewtopic.php?f=30&t=95091 We should review the wording and/or add a tooltip describing that the node actually shows differences between metadata in the database (versus metadata in file tags). |
|
|
How about: Out-of-date tags --> DB / Tag mismatches Tooltip: This finds all tracks with tags that don't match the database, highlighting the mismatched values. If tracks don't show highlighted fields, try enabling additional columns. |
|
|
Sounds good, added in 2199 |
|
|
Verified 2200. |
