View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0022424 | MMW 5 | Tagging / organizing (properties / auto-tools) | public | 2026-10-15 02:23 | 2026-10-15 02:23 |
| Reporter | lowlander | Assigned To | |||
| Priority | immediate | Severity | major | Reproducibility | have not tried |
| Status | assigned | Resolution | open | ||
| Platform | Windows | OS | - | OS Version | 11 |
| Product Version | 2027.0 | ||||
| Target Version | 2027.0 | ||||
| Summary | 0022424: MediaMonkey overwrites new tags | ||||
| Description | MediaMonkey 2027 introduced new tags like Compilation Flag which can be existing tags in the users files. MediaMonkey is unaware of the values of these new tags as the user hasn't rescanned. Now if the users edits any field those new tags can get overwritten (ie. Compilation = True in user files tags gets changed to False as MediaMonkey doesn't have this set). Rescanning files will often not pick up the new tags as most users would only rescan files with changed timestamp 1. MediaMonkey should on any update, check if that update brings support to new tags to an existing user Library. ie. this should be from any version to any version update. 2. MediaMonkey should offer to rescan files for the newly supported tags. 2a. The first option should be to rescan files and only update the newly supported tags from file 2b. The second option should be to rescan all tags 3. Rescan should smartly only rescan file type(s) for which the new tag(s) are supported. 4. Rescan should be offered on first run after update. Ideally it would resume on restart of MM if it hadn't completed. | ||||
| Tags | No tags attached. | ||||
| Fixed in build | |||||
