View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0002613 | MMW v4 | Properties/Auto-Tools | public | 2006-08-25 13:31 | 2007-07-16 20:00 |
| Reporter | rusty | Assigned To | |||
| Priority | urgent | Severity | feature | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Fixed in Version | 3.0 | ||||
| Summary | 0002613: ID3 V2.4 tagging support | ||||
| Description | MM does not yet support ID3 V2.4 tags. Need to investigate what is involved to add this. We'd probably want to add: -Support for reading such tags -Configurable support for writing such tags (i.e. let the user choose v2.3 or v2.4). | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 1035 | ||||
|
|
MM already reads ID3v2.4 tags. As for writing, I'm not sure if it's necessary to give user the choice which format to write, whether it's really important for anybody. |
|
|
Most recent discussion: http://www.id3.org/id3v2.4.0-changes.txt describes a number of concrete differences between v2.3 and v2.4 and they involve fields that MM uses. This implies that some additional work is required to support writing of ID3v2.3 and ID3v2.4 (examples: year, original release year, involved people list, etc.). Jiri: Due to poor planning in ID3v2 design, my plan isn't to write ID3v2.3 or 2.4 _exactly_ according to specs, but rather write a combination of both (marked by v2.3 for a better compatibility). The reason is that if we choose either of the versions, users would complain - e.g. if we choose 2.4, TYER (year) field would be missing and so some apps wouldn't show it, similar problems would happen with 2.3. So we will rather write a mixture of both versions, i.e. frames from 2.3 and 2.4 which will ensure the best compatibility as possible. We need to document exactly what we're supporting for each field and include this information in the online help. |
|
|
Assigning to Peke to review ID3v2.4 specs and suggest frames that we don't write at all, or write incompletely. Jiri will complete the specs then based on this. See MP3Manage.pas for list of frame we read/write to mp3 files and Id3lib.pas for mapping of frame names to ID3v2 4 letter codes. |
|
|
Most of the work was already done in issue 0002953, so setting this as resolved. The only thing we could possibly add is a support for writing ID3v2.4 tags (configurable vs. ID3v2.3 tags). |
|
|
Closing as dup. |
