ID3v1.1: Difference between revisions
(categorization) |
Beardgoggles (talk | contribs) m (Updated See also/External links) |
||
| (5 intermediate revisions by 5 users not shown) | |||
| Line 1: | Line 1: | ||
{|align="right" border="0" cellpadding="5" | |||
| | |||
{|class="wikitable" style="margin-top: 0;" | |||
{| align= | |- | ||
! Field name !! Characters/bytes | |||
|- | |||
| Song title || 30 characters | | Song title || 30 characters | ||
|- | |- | ||
| Line 17: | Line 19: | ||
| Genre || 1 byte | | Genre || 1 byte | ||
|} | |} | ||
|[[Image:id3v1.1_blocks.png|frame|center|Example ID3v1.1 Tag]] | |||
|} | |||
Although [[ID3v1]] may well be easy to implement for programmers, it sure is frustrating for those with their own creative ideas. Since the ID3v1 tag had a fixed size and no space marked "Reserved for future use", there isn't really room for that much improvement, if you want to maintain compatibility with existing software. | |||
A person who discovered a way was Michael Mutschler, who made a quite clever improvement on ID3v1. Since all non-filled fields must be padded with zeroed bytes, it is a good assumption that all ID3v1 readers will stop reading the field when they encounter a zeroed byte. If the second last byte of a field is zeroed and the last one isn't, we have an extra byte to fill with information. As the comments field is too short to write anything useful, the '''ID3v1.1''' standard declares that this field should be 28 characters, that the next byte always should be zero and that the last byte before the genre byte should contain which track on the CD this music comes from. | |||
{{panel|This material is copyrighted © [http://id3.org/Copyright Martin Nilsson].}} | |||
== | ==See also== | ||
* [[ID3v1]] | * [[ID3v1]] | ||
* [[ID3v2]] | * [[ID3v2]] | ||
==External links== | |||
* [https://id3.org/ID3v1#What_is_ID3v1.1.3F What is ID3v1.1?] | |||
[[Category:Metadata]] | |||
[[Category:MP3]] | |||
[[Category:Technical]] | [[Category:Technical]] | ||
Latest revision as of 09:33, 11 June 2022
|
 |
Although ID3v1 may well be easy to implement for programmers, it sure is frustrating for those with their own creative ideas. Since the ID3v1 tag had a fixed size and no space marked "Reserved for future use", there isn't really room for that much improvement, if you want to maintain compatibility with existing software.
A person who discovered a way was Michael Mutschler, who made a quite clever improvement on ID3v1. Since all non-filled fields must be padded with zeroed bytes, it is a good assumption that all ID3v1 readers will stop reading the field when they encounter a zeroed byte. If the second last byte of a field is zeroed and the last one isn't, we have an extra byte to fill with information. As the comments field is too short to write anything useful, the ID3v1.1 standard declares that this field should be 28 characters, that the next byte always should be zero and that the last byte before the genre byte should contain which track on the CD this music comes from.
This material is copyrighted © Martin Nilsson.