View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0013513 | MMW v4 | Framework: Tagging | public | 2016-09-09 07:52 | 2016-11-10 19:02 |
| Reporter | michal | Assigned To | |||
| Priority | immediate | Severity | minor | Reproducibility | sometimes |
| Status | closed | Resolution | fixed | ||
| Product Version | 4.1.14 | ||||
| Target Version | 4.1.14 | Fixed in Version | 4.1.14 | ||
| Summary | 0013513: MM sometimes do not read track and disc number tags udpated by other tagging apps from M4A/MP4 | ||||
| Description | There are some situations, where some other tagging app like MP3Tag changes track or disc number, but MM still reads old values. I have found out, that it can happen in case M4A files already contain udta.Xtra atom with metadata (it is written and preferred by Windows Explorer in Windows 7), this atom is not updated by MP3Tag. MM should always prefer standard M4A tags, they are preferred in Win Explorer in Windows 10 too. | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 1809 | ||||
|
|
Fixed in build 1809. |
|
|
Verified current fix in 1809 now standard metadata is prefered over udta.Xtra. Can you please clarify what write rules MMW uses now as of 1809 in terms when both exist and/or udta.Xtra do not exist for backward compatibility With Windows 7 |
|
|
MMW always updates udta.Xtra atom, in case it is already present in the file. It does not create it by default, but this default can be overridden by setting "WriteWMTags" to true in "MP4Tagging" section of MediaMonkey.ini. |
|
|
Thank you for clarification. Closing |
|
|
Just one correction - MM creates Xtra atom by default (so metadata are read by Windows Explorer in Windows 7), this can be suppressed by setting mentioned parameter WriteWMTags to 0. |
