View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0022357 | MMW 5 | Tagging / organizing (properties / auto-tools) | public | 2026-09-24 20:40 | 2026-09-29 15:08 |
| Reporter | rusty | Assigned To | |||
| Priority | urgent | Severity | major | Reproducibility | always |
| Status | feedback | Resolution | open | ||
| Product Version | 2027.0 | ||||
| Target Version | 2027.0 | ||||
| Summary | 0022357: Duplicate functionality: 'Update tags' vs 'Remove & rewrite tags & artwork' | ||||
| Description | 'Update tags...' is designed for updating tags when they're out of sync with the library. 'Remove & rewrite tags & artwork' seems to do the same thing except that it also ensures that artwork is saved according to defined artwork settings. Why not just combine these functions into: 'Update tags & artwork' [Removes current tags and rewrites metadata & artwork according to settings] Or am I misunderstanding this? | ||||
| Tags | No tags attached. | ||||
| Fixed in build | |||||
|
|
They overlap, but removing existing tags is a significant difference: --> Update tags writes library metadata through the normal tag writer. It also handles artwork, but doesn’t first erase the tags or force existing artwork into the current storage configuration. --> Remove & rewrite tags & artwork explicitly strips tags, rebuilds them, reorganizes artwork according to the current embedded/external storage setting, and cleans up unused external artwork files. Replacing ordinary updates with the second operation could discard file-only metadata that MediaMonkey cannot reconstruct. I’d combine the UI, while keeping both behaviors: “Update tags & artwork…”, with an unchecked “Remove existing tags and rebuild artwork storage using current settings” option. Normal updates would remain the default. |
|
|
Sounds reasonable. Can I assume that: - whether the 'Remove existing tags....' option is checked or not, that after this operation is completed for all files that Files to Edit > DB/Tag mismatch will not contain any files? - that if 'Remove existing tags...' option is checked, that after this operation is completed for all files in Files to Edit > Inconsistent Artwork will not contain any files? Lastly: if this option cleans up/rewrites artwork according to the settings in Options > Tags & Playlists > Artwork, then what is the main usecase for the functionality at 0021575? |
|
|
Assigned to Michal to review as it was implemented by him in course of 0014064 |
|
|
Re Empty DB/Tag mismatch after this operation - yes, if all tags were written successfully Re Inconsistent Artwork - no, these are different things. This overview compares the first image across tracks within the same album: the artwork type, storage method, description, path, and image format. The storage rebuild processes each track individually and does not unify its artwork with the other tracks in the album. For example, differences in artwork descriptions or a missing image for some tracks in the album may remain. |
