View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0005347 | MMW v4 | Framework: Tagging | public | 2009-03-02 14:05 | 2022-04-29 01:06 |
| Reporter | peke | Assigned To | |||
| Priority | urgent | Severity | trivial | Reproducibility | have not tried |
| Status | closed | Resolution | fixed | ||
| Product Version | 3.1 | ||||
| Target Version | 4.1 | Fixed in Version | 4.1 | ||
| Summary | 0005347: WAV metadata Track Number 'itrk' not supported on some devices | ||||
| Description | In the Past lowercase WAV metadata tags indicated non-standard fields, but also some devices assumed that itrk is uppercase like in ID3 tags (WMP) and other apps (like MM) made case insensitive support for itrk. Note: Another example is that iriver H10 does support WAVE audio playback and recognizes song information in LIST/INFO chunk: title (INAM); artist (IART); album (IPRD); genre (IGNR); year (ICRD); and lowercase track number (itrk). | ||||
| Additional Information | eSupport Ticket: DFU-548033 Additional Links: http://forum.dbpoweramp.com/showthread.php?t=9366 http://www.digital-inn.de/135305-post3.html | ||||
| Tags | todoc-KB | ||||
| Fixed in build | 1600 | ||||
|
|
Changed track metadata for WAV files to save uppercase 'ITRK' for compatibility reasons. |
|
|
I need a bit of clarification: Peke, I don't quite understand the rationale for the change. As I understand (just from reading the bug): itrk: is used by many devices and is the format used by dbpoweramp ITRK: is used by ARCUS device and WMP So if we switch from itrk to ITRK (as has been done in build 1225), won't it fix compatibility for ARCUS devices but break compatibility in many other cases/devices? I would suggest that at this stage the best solution is: 1) One that would allow MM to read both itrkc and ITRK 2)i) One that would allow MM to write both (I don't know if that's possible) ii) If 2i) isn't possible, then we should leave MM as it has always been, but add an .ini switch that makes this configurable Normally I wouldn't mind making a change from itrk to ITRK during the beta cycle in order to solicit user feedback, however, we're so close to release that we might not discover any serious problems that this change might cause. |
|
|
I've asked Jiri over IM what to do as MM is not case sensitive when reading metadata headers (will read 'itrk' and 'ITRK') which is made for compatibility with all other apps. As Microsoft is made that standard it looks that 'ITRK' is officially included and we just follow standard. Even this is low risk change and to exclude all issues I've made 2ii) as solution and 'UpperCaseITRK' in '[WAVTagging]' section to control Plugin behavior using values 1 = True (Default) and 0 = False. |
|
|
Fixed by using 2ii) 'UpperCaseITRK' .ini Setting has been added to control compatibility of Track# Tag field in various applications and hardware devices. Default is UpperCase due compatibility with WMP. |
|
|
Set lowercase by default due the backward compatibility, which means that users that need Uppercase 'itrk' will need to set 'UpperCaseITRK=1' in '[WAVTagging]' section of MediaMonkey.ini |
|
|
Closing I've added KB Article to describe functionality: http://www.mediamonkey.com/support/index.php?_m=knowledgebase&_a=viewarticle&kbarticleid=126 |
|
|
UpperCaseITRK=2 should be added which would write in both lower and uppercase. |
|
|
Looks like this would be the best default value - providing it doesn't cause a problem to any commonly used application or device. |
|
|
Fixed in build 1600. UpperCaseITRK=2 is the default value. |
|
|
Verified 1605 |
|
|
Verified 1615 |
