View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0006067 | MMW v4 | Help / Docs / Localization | public | 2009-10-20 18:54 | 2009-10-23 20:41 |
| Reporter | user_chrisjj | Assigned To | |||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | resolved | Resolution | won't fix | ||
| Platform | Windows | OS | XP | OS Version | - |
| Target Version | 3.1.2 | ||||
| Summary | 0006067: Help incorrect for FLAC Album Artist standard | ||||
| Description | Help, About Track Properties says: [code] OGG / FLAC Album Artist Yes (ALBUMARTIST, [ALBUM ARTIST], [ENSEMBLE]) [/code] whereas actually this behaviour is non-standard (as confirmed by Dev Peke at http://www.mediamonkey.com/forum/viewtopic.php?p=227863#p227863) The Help should say No rather than Yes. Reported at http://www.mediamonkey.com/forum/viewtopic.php?f=7&t=43659 | ||||
| Tags | No tags attached. | ||||
| Fixed in build | |||||
|
|
This actually is according to standard. i.e. the fact that MM supports several additional custom fields in addition to the standard doesn't make it non-standard. i'll verify that the help is as clear as possible, though. |
|
|
> the fact that MM supports several additional custom fields in > addition to the standard doesn't make it non-standard. Sure, but the fact that it duplicates the same value across multiple fields does make it non-standard. The standard encourages e.g.: ARTIST=Dizzy Gillespie ARTIST=Sonny Rollins ARTIST=Sonny Stitt with DIFFERENT values but MM is writing the SAME value to multiple equivalent comments, causing the problem: http://www.mediamonkey.com/forum/viewtopic.php?p=227863#p225544 I have FLAC files that I have imported that when I look at the tags in dbpoweramp shows the album artist twice with a semi-colon in between. For example "Madonna;Madonna". |
|
|
I think that MM does adhere to the standards, and that the problem here is that there are multiple defacto standards. So I don't think that this is a problem with the online help, but I do think that there's merit to the suggestion in the forum that MM should allow users to choose what tag or tags should be mapped to which fields. Closing, but I'm going to reference this in another feature bug re. field/tag mapping. |
