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-24 13:09 |
| Reporter | lowlander | Assigned To | |||
| Priority | urgent | Severity | major | Reproducibility | have not tried |
| Status | resolved | Resolution | fixed | ||
| Platform | Windows | OS | - | OS Version | 11 |
| Product Version | 2027.0 | ||||
| Target Version | 2027.0 | Fixed in Version | 2027.0 | ||
| Summary | 0022424: MediaMonkey can overwrite tags that are newly supported | ||||
| 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 | 3528 | ||||
|
|
Fixed in build 3527. It offers rescan during DB update, which reads and adds new tags (preserves already existing, if saved to DB before). In case user skips this. or does not finish this, he/she can do it again using Files to Edit -> DB / Tag mismatches. Currently it means Synced lyrics, Energy, Language and Compilation flag. |
|
|
"or does not finish this, he/she can do it again using Files to Edit -> DB / Tag mismatches" How exactly does this work. Loading this node, did not offer to restart the scanning. |
|
|
I somehow automatically thought it is possible to sync/rescan from files to DB in "DB / Tag mismatches", but it seems it is not, we have only the direction from DB to files, my fault. I will try to somehow save state before closing and implement automatic resume after restart. Or ask user, whether to continue previous rescan. |
|
|
Fixed in build 3528. The upgrade rescan now saves its progress when the app closes and every 20 seconds (so it doesn't lose all progress in case of a crash). It also automatically resumes scanning one minute after the app starts. If the user declines the rescan, it is skipped. They can still run a regular manual rescan of all file locations later. Test note - you need older DB version for this to test, lower than 5.1.16 (version is saved in table DBInfo, you can edit it manually e.g. using SQLiteStudio, if needed) |
