View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0004318 | MMW v4 | Properties/Auto-Tools | public | 2008-01-21 20:48 | 2008-01-22 17:28 |
| Reporter | rusty | Assigned To | |||
| Priority | urgent | Severity | feature | Reproducibility | always |
| Status | feedback | Resolution | open | ||
| Product Version | 3.0 | ||||
| Summary | 0004318: No way to clean tags without overwriting other custom tags | ||||
| Description | Many users have tracks that have: 1) tags from MM 2) tags from other apps that aren't supported by MM 3) tag in either of the above 2 categories that have null characters (see attached jpeg) MM currently allows users to sync tags, and this fixes item 3) but it overwrites tags in item 2). What is needed for advanced users is a means of fixing 3) without overwriting item 2). Possible solution: Add another option to the Sync Tags operation e.g.: ( ) Synch tags and delete non-MediaMonkey tags (o) Synch tags without deleting non-MediaMonkey tags Both operations would delete all 'null' characters wherever they appear, and the user would have the choice as to whether to retain custom tags. ON THE OTHER HAND: I'm not sure if the above is the best solution since MM tag operations will generally overwrite custom tags anyhow. So perhaps the best solution is to change MM in general so that it recognizes that other tags do exist and never overwrite them (and perhaps add support for editing them). please comment... | ||||
| Additional Information | sample file posted to ftp | ||||
| Tags | No tags attached. | ||||
| Attached Files | |||||
| Fixed in build | |||||
|
|
I agree that since MM is supposed to be a very advanced tool for tagging purposes, issues related to particularly to non-MM tags should be resolved somehow. I would suggest to: 1. Let user to show _all_ fields present in tags of given file, i.e. something like in foobar where user can edit/enter pretty much anything that could be entered in tags. 2. Add scripting interfaces so that this functionality would be accessible from scripts and script authors could easily write something like 'Process all tracks and delete any non-standard fields' or anything similar. re. 1. Question is where to place it within MM interface. It could possibly be somehow accessible from the default properties dialog, maybe be another tab there. Another option is to make this switchable, i.e. either show Properties dialog as currently is and when user would need some advanced operations, he could switch to a detailed view with all fields. Alternatively, we could skip implementation of 1 and only implement 2, which would give script authors a chance to implement something like 1. Note: For purposes of advanced tag editing I don't consider ID3v1 important any longer, it's getting more and more outdated and so we could consider that every track has only one type of tag and expose user to any other complication. |
|
|
Re. 1. I agree that it should just be another tab in the Properties UI that either: a) covers any fields not present in the other tabs b) covers all non Art fields I don't think that there's a need to set a different 'mode' of operation, though. I would just make the tabs persistent i.e. if the dialog should open with the last used tab selected by default (this is a feature that I've often wished for anyhow). Re. ID3v1: I don't think we should eliminate support just yet--in this tab it should just work exactly the way ID3v1 works in the rest of MM (i.e. id3v1 is ignored if ID3v2 tag exists). |
|
|
1. Ok, I'd probably choose b) or both a&b) switchable by a checkbox. ID3v1: Sure, I didn't mean to remove ID3v1 support, I just mean that in case some ID3v1 field differs from ID3v2, user wouldn't see this represented in UI in any way, he would see ID3v2 field value only (be it artist, album or anything else). |
