Difference between revisions of "ID3v1.1"

From Hydrogenaudio Knowledgebase
Jump to: navigation, search
m (Updated See also/External links)
 
(6 intermediate revisions by 5 users not shown)
Line 1: Line 1:
[[ID3v1]] may well be easy to implement for programmers, but 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.
+
{|align="right" border="0" cellpadding="5"
 
+
|
<center>[[Image:id3v1.1_blocks.png|frame|center|Example ID3v1.1 Tag]]</center>
+
{|class="wikitable" style="margin-top: 0;"
{| align=center border="1" cellpadding="5" cellspacing="0"
+
|-
 +
! 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.
  
One who found a way out was Michael Mutschler who made a quite clever improvement on [[ID3v1]]. Since all non-filled fields must be padded with zeroed bytes its 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 to short to write anything useful in 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.
+
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].}}
  
==Additional Reading==
+
==See also==
 
* [[ID3v1]]
 
* [[ID3v1]]
 
* [[ID3v2]]
 
* [[ID3v2]]
  
 +
==External links==
 +
* [https://id3.org/ID3v1#What_is_ID3v1.1.3F What is ID3v1.1?]
  
==Copyright==
+
[[Category:Metadata]]
This material is copyrighted by [http://www.id3.org/copy.html Martin Nilsson], taken from [http://www.id3.org/id3v1.html ID3 made easy ].
+
[[Category:MP3]]
 +
[[Category:Technical]]

Latest revision as of 09:33, 11 June 2022

Field name Characters/bytes
Song title 30 characters
Artist 30 characters
Album 30 characters
Year 4 characters
Comment 28 characters
Album track 2 characters
Genre 1 byte
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.

See also

External links