View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0004383 | MMW v4 | Properties/Auto-Tools | public | 2008-02-08 23:10 | 2009-06-15 18:28 |
| Reporter | peke | Assigned To | |||
| Priority | none | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | no change required | ||
| Summary | 0004383: Multiple MP3 metadata Tags are not read correctly | ||||
| Description | According To MP3 ID3v2 Standard metadata is Located on the beginning of MP3 files. In some cases some tagging application writes multiple ID3 metadata frames or even custom metadata frames. MediaMonkey Do not have any problems with reading all metadata frames, but only last one is used for filling library info. Example file uploaded to FTP Contain three Metadata Frames. Sorted from beginning of file: 1. ID3v2 That have correct Metadata updated by unknown application 2. PRIV WM/WMContent included in first ID3v2 Most likely Added by WMP, but WMP11 I have tested did not add it when I tried to replicate 3. Another ID3v2 metadata with invalid values MediaMonkey reads all Of Them and uses Second ID3v2 to add track to library which is invalid as first one is updated and correct. I'm certain that this is not MM fault as mediamonkey correctly clears all tag data from file. | ||||
| Additional Information | Related Support Ticket Info http://www.mediamonkey.com/support/staff/index.php?_m=tickets&_a=viewticket&ticketid=45&offset=5 | ||||
| Tags | No tags attached. | ||||
| Fixed in build | |||||
|
|
I'm Assuming that possible best solution would be that MM reads all metadata and on end apply first one. Rewriting Tag in MM fixes corrupted metadata structure and writes only 1 ID3v2 tag including PRIV WM frames |
|
|
I reviewed the file posted by user and it really contains 2 ID3v2 tags. Since it's quite strange and uncommon situation, I'm leaving it as is, since it isn't even clear which aproach (i.e. prefer the first or the second tag) is better. |
|
|
I Totally agree. If this case repeats, we should Suggest user to clean/save Tags in MM and Re-tag with Mm or app of his choice. |
