View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000170 | MMW v4 | Properties/Auto-Tools | public | 2003-02-27 19:31 | 2007-09-11 17:05 |
| Reporter | rusty | Assigned To | |||
| Priority | low | Severity | major | Reproducibility | always |
| Status | feedback | Resolution | open | ||
| Summary | 0000170: MM is useless for ID3v1 users / Allow user to set which tags to use when conflict exists | ||||
| Description | As documented in bug #164, it is often unclear to the advanced user where property information is gotten from when individual fields in v1 and v2 tags conflict. There should be an explicit configuration item that allows the user to configure which tag to use in the event of a conflict between fields. This could be implemented as follows within the tag settings dialog: --If ID3v1 tag doesn't match ID3v2 tag---- | (o) Use ID3v1 info | ( ) Use ID3v2 info ------------------------------------------ Note: when we implement this, we'll likely have to re-arrange this dialog somewhat, into 2 sections, 1 for reading tags, and 1 for writing tags. | ||||
| Tags | No tags attached. | ||||
| Fixed in build | |||||
|
|
I set priority to low, because this is the kind of bug that isn't necessary to solve now. |
|
|
Changing to 'normal' - it should be fixed if we have time since it provides some much needed transparency to the user. |
|
|
Changed the title of the bug to reflect the findings of #1258. Essentially, if the user configures MM to write ID3v1 tags, then the information displayed in the Library and My Computer nodes is not at all reflective of any edits that the user makes to the library. There are 2 possible approaches to resolving this problem: 1) Make scan order reflective of tag writing (or allow the user to set whether to scan v1 or v2 tags first) 2) Force deletion of ID3v2 fields if MM is configured to only write v1 fields. I think that the first approach makes a lot more sense. |
