View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0005876 | MMW v4 | Framework: Tagging | public | 2009-07-13 12:28 | 2014-12-10 11:55 |
| Reporter | user_chrisjj | Assigned To | |||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | feedback | Resolution | reopened | ||
| Platform | Windows | OS | XP | OS Version | - |
| Target Version | 4.1 | ||||
| Summary | 0005876: Adding Disc# total can make nonsense format | ||||
| Description | See http://www.mediamonkey.com/forum/viewtopic.php?f=7&t=41311 This occurs in the Now Playing window and Mizery_made reports it also occurs in the library. | ||||
| Tags | No tags attached. | ||||
| Fixed in build | |||||
| related to | 0005758 | closed | Ludek | Track Properties: Presing Delete do not remove selected Album Art from list |
| related to | 0007245 | closed | Ludek | 1345: Auto-Tag from Filename <Disc#> doesn't support non-numeric values |
| related to | 0005878 | assigned | jiri | MM hides the /n part (disc qty) of WM/PartOfSet and ID3 TPOS (discnumber) |
| child of | 0004920 | assigned | Ludek | Support for Total # Discs and Tracks |
|
|
As I explained in the forum post, I don't think it's a bug. We must introduce Total Track and Disc # fields in MM 4.0. |
|
|
(Forum http://www.mediamonkey.com/forum/viewtopic.php?f=7&t=41311& . If nonsense format doesn't make it a bug, perhaps the fact that MM writes non-compliant TPOS does. |
|
|
No, really, it isn't non-compliant. MM simply currently doesn't support Total Disc # field and so if you enter '1/2' it's understood as an other possible Disc # (like '1', 'A', 'I', 'I,II' or whatever). So writing it back to ID3 in the form it's currently written is perfectly logical and correct. |
|
|
> No, really, it isn't non-compliant. ... if you enter '1/2' it's understood as > an other possible Disc # (like '1', 'A', 'I', 'I,II' or whatever) That's non-compliant - ID3v2 does not allow ""'A', 'I', 'I,II' or whatever". |
|
|
That's right, non-numerical strings aren't officially allowed in ID3v2 Disc # field, but for obvious reasons (mainly because they are perfectly legal in other tagging formats) we support them. |
|
|
>That's right, non-numerical strings aren't officially allowed in ID3v2 Disc # field Hence they are non-compliant and your "isn't non-compliant" is incorrect. > we support them. That doesn't make them compliant. |
|
|
Reassigning to Ludek for MM5 |
|
|
Assigned back to Jiri. |
