id3 0.4.0
Sign up to get free protection for your applications and to get access to all the features.
- data/LICENSE.html +146 -0
- data/README +23 -0
- data/docs/Class_AudioFile.html +110 -0
- data/docs/Class_Frame.html +125 -0
- data/docs/Class_Tag1.html +121 -0
- data/docs/Class_Tag2.html +167 -0
- data/docs/ID3-Standards/id3v2-00.html +1669 -0
- data/docs/ID3-Standards/id3v2-00.txt +1660 -0
- data/docs/ID3-Standards/id3v2.3.0.html +2033 -0
- data/docs/ID3-Standards/id3v2.3.0.txt +2025 -0
- data/docs/ID3-Standards/id3v2.4.0-changes.html +159 -0
- data/docs/ID3-Standards/id3v2.4.0-changes.txt +149 -0
- data/docs/ID3-Standards/id3v2.4.0-frames.html +1743 -0
- data/docs/ID3-Standards/id3v2.4.0-frames.txt +1732 -0
- data/docs/ID3-Standards/id3v2.4.0-structure.html +742 -0
- data/docs/ID3-Standards/id3v2.4.0-structure.txt +732 -0
- data/docs/ID3_comparison.html +2121 -0
- data/docs/ID3_comparison2.html +2043 -0
- data/docs/ID3v2_frames_comparison.html +2121 -0
- data/docs/ID3v2_frames_comparison.txt +197 -0
- data/docs/ID3v2_frames_overview.txt +60 -0
- data/docs/Module_ID3.html +146 -0
- data/docs/id3.html +245 -0
- data/docs/index.html +252 -0
- data/index.html +8 -0
- data/lib/hexdump.rb +113 -0
- data/lib/id3.rb +1177 -0
- data/lib/invert_hash.rb +105 -0
- metadata +75 -0
|
@@ -0,0 +1,2033 @@
|
|
|
1
|
+
<HTML>
|
|
2
|
+
<HEAD>
|
|
3
|
+
<TITLE>ID3 tag version 2.3.0</TITLE>
|
|
4
|
+
</HEAD>
|
|
5
|
+
<BODY BGCOLOR="#FFFFFF" TEXT="#000000" VLINK="#051271" LINK="#0000B1" ALINK="#A21600">
|
|
6
|
+
<PRE>
|
|
7
|
+
|
|
8
|
+
Informal standard M. Nilsson
|
|
9
|
+
Document: id3v2.3.0.txt 3rd February 1999
|
|
10
|
+
|
|
11
|
+
|
|
12
|
+
ID3 tag version 2.3.0
|
|
13
|
+
|
|
14
|
+
Status of this document
|
|
15
|
+
|
|
16
|
+
This document is an informal standard and replaces the ID3v2.2.0
|
|
17
|
+
standard [ID3v2]. The informal standard is released so that
|
|
18
|
+
implementors could have a set standard before a formal standard is
|
|
19
|
+
set. The formal standard will use another version or revision number
|
|
20
|
+
if not identical to what is described in this document. The contents
|
|
21
|
+
in this document may change for clarifications but never for added or
|
|
22
|
+
altered functionallity.
|
|
23
|
+
|
|
24
|
+
Distribution of this document is unlimited.
|
|
25
|
+
|
|
26
|
+
|
|
27
|
+
Abstract
|
|
28
|
+
|
|
29
|
+
This document describes the ID3v2.3.0, which is a more developed
|
|
30
|
+
version of the ID3v2 informal standard [ID3v2] (version 2.2.0),
|
|
31
|
+
evolved from the ID3 tagging system. The ID3v2 offers a flexible way
|
|
32
|
+
of storing information about an audio file within itself to determine
|
|
33
|
+
its origin and contents. The information may be technical
|
|
34
|
+
information, such as equalisation curves, as well as related meta
|
|
35
|
+
information, such as title, performer, copyright etc.
|
|
36
|
+
|
|
37
|
+
|
|
38
|
+
1. Table of contents
|
|
39
|
+
|
|
40
|
+
2. Conventions in this document
|
|
41
|
+
3. ID3v2 overview
|
|
42
|
+
3.1. ID3v2 header
|
|
43
|
+
3.2. ID3v2 extended header
|
|
44
|
+
3.3. ID3v2 frames overview
|
|
45
|
+
3.3.1. Frame header flags
|
|
46
|
+
3.3.2. Default flags
|
|
47
|
+
4. Declared ID3v2 frames
|
|
48
|
+
4.1. Unique file identifier
|
|
49
|
+
4.2. Text information frames
|
|
50
|
+
4.2.1. Text information frames - details
|
|
51
|
+
4.2.2. User defined text information frame
|
|
52
|
+
4.3. URL link frames
|
|
53
|
+
4.3.1. URL link frames - details
|
|
54
|
+
4.3.2. User defined URL link frame
|
|
55
|
+
4.4. Involved people list
|
|
56
|
+
4.5. Music CD Identifier
|
|
57
|
+
4.6. Event timing codes
|
|
58
|
+
4.7. MPEG location lookup table
|
|
59
|
+
4.8. Synced tempo codes
|
|
60
|
+
4.9. Unsychronised lyrics/text transcription
|
|
61
|
+
4.10. Synchronised lyrics/text
|
|
62
|
+
4.11. Comments
|
|
63
|
+
4.12. Relative volume adjustment
|
|
64
|
+
4.13. Equalisation
|
|
65
|
+
4.14. Reverb
|
|
66
|
+
4.15. Attached picture
|
|
67
|
+
4.16. General encapsulated object
|
|
68
|
+
4.17. Play counter
|
|
69
|
+
4.18. Popularimeter
|
|
70
|
+
4.19. Recommended buffer size
|
|
71
|
+
4.20. Audio encryption
|
|
72
|
+
4.21. Linked information
|
|
73
|
+
4.22. Position synchronisation frame
|
|
74
|
+
4.23. Terms of use
|
|
75
|
+
4.24. Ownership frame
|
|
76
|
+
4.25. Commercial frame
|
|
77
|
+
4.26. Encryption method registration
|
|
78
|
+
4.27. Group identification registration
|
|
79
|
+
4.28. Private frame
|
|
80
|
+
5. The 'unsynchronisation scheme'
|
|
81
|
+
6. Copyright
|
|
82
|
+
7. References
|
|
83
|
+
8. Appendix
|
|
84
|
+
A. Appendix A - Genre List from ID3v1
|
|
85
|
+
9. Author's Address
|
|
86
|
+
|
|
87
|
+
|
|
88
|
+
2. Conventions in this document
|
|
89
|
+
|
|
90
|
+
In the examples, text within "" is a text string exactly as it
|
|
91
|
+
appears in a file. Numbers preceded with $ are hexadecimal and
|
|
92
|
+
numbers preceded with % are binary. $xx is used to indicate a byte
|
|
93
|
+
with unknown content. %x is used to indicate a bit with unknown
|
|
94
|
+
content. The most significant bit (MSB) of a byte is called 'bit 7'
|
|
95
|
+
and the least significant bit (LSB) is called 'bit 0'.
|
|
96
|
+
|
|
97
|
+
A tag is the whole tag described in this document. A frame is a block
|
|
98
|
+
of information in the tag. The tag consists of a header, frames and
|
|
99
|
+
optional padding. A field is a piece of information; one value, a
|
|
100
|
+
string etc. A numeric string is a string that consists of the
|
|
101
|
+
characters 0-9 only.
|
|
102
|
+
|
|
103
|
+
|
|
104
|
+
3. ID3v2 overview
|
|
105
|
+
|
|
106
|
+
The two biggest design goals were to be able to implement ID3v2
|
|
107
|
+
without disturbing old software too much and that ID3v2 should be
|
|
108
|
+
as flexible and expandable as possible.
|
|
109
|
+
|
|
110
|
+
The first criterion is met by the simple fact that the MPEG [MPEG]
|
|
111
|
+
decoding software uses a syncsignal, embedded in the audiostream, to
|
|
112
|
+
'lock on to' the audio. Since the ID3v2 tag doesn't contain a valid
|
|
113
|
+
syncsignal, no software will attempt to play the tag. If, for any
|
|
114
|
+
reason, coincidence make a syncsignal appear within the tag it will
|
|
115
|
+
be taken care of by the 'unsynchronisation scheme' described in
|
|
116
|
+
section 5.
|
|
117
|
+
|
|
118
|
+
The second criterion has made a more noticeable impact on the design
|
|
119
|
+
of the ID3v2 tag. It is constructed as a container for several
|
|
120
|
+
information blocks, called frames, whose format need not be known to
|
|
121
|
+
the software that encounters them. At the start of every frame there
|
|
122
|
+
is an identifier that explains the frames' format and content, and a
|
|
123
|
+
size descriptor that allows software to skip unknown frames.
|
|
124
|
+
|
|
125
|
+
If a total revision of the ID3v2 tag should be needed, there is a
|
|
126
|
+
version number and a size descriptor in the ID3v2 header.
|
|
127
|
+
|
|
128
|
+
The ID3 tag described in this document is mainly targeted at files
|
|
129
|
+
encoded with MPEG-1/2 layer I, MPEG-1/2 layer II, MPEG-1/2 layer III
|
|
130
|
+
and MPEG-2.5, but may work with other types of encoded audio.
|
|
131
|
+
|
|
132
|
+
The bitorder in ID3v2 is most significant bit first (MSB). The
|
|
133
|
+
byteorder in multibyte numbers is most significant byte first (e.g.
|
|
134
|
+
$12345678 would be encoded $12 34 56 78).
|
|
135
|
+
|
|
136
|
+
It is permitted to include padding after all the final frame (at the
|
|
137
|
+
end of the ID3 tag), making the size of all the frames together
|
|
138
|
+
smaller than the size given in the head of the tag. A possible
|
|
139
|
+
purpose of this padding is to allow for adding a few additional
|
|
140
|
+
frames or enlarge existing frames within the tag without having to
|
|
141
|
+
rewrite the entire file. The value of the padding bytes must be $00.
|
|
142
|
+
|
|
143
|
+
|
|
144
|
+
3.1. ID3v2 header
|
|
145
|
+
|
|
146
|
+
The ID3v2 tag header, which should be the first information in the
|
|
147
|
+
file, is 10 bytes as follows:
|
|
148
|
+
|
|
149
|
+
ID3v2/file identifier "ID3"
|
|
150
|
+
ID3v2 version $03 00
|
|
151
|
+
ID3v2 flags %abc00000
|
|
152
|
+
ID3v2 size 4 * %0xxxxxxx
|
|
153
|
+
|
|
154
|
+
The first three bytes of the tag are always "ID3" to indicate that
|
|
155
|
+
this is an ID3v2 tag, directly followed by the two version bytes. The
|
|
156
|
+
first byte of ID3v2 version is it's major version, while the second
|
|
157
|
+
byte is its revision number. In this case this is ID3v2.3.0. All
|
|
158
|
+
revisions are backwards compatible while major versions are not. If
|
|
159
|
+
software with ID3v2.2.0 and below support should encounter version
|
|
160
|
+
three or higher it should simply ignore the whole tag. Version and
|
|
161
|
+
revision will never be $FF.
|
|
162
|
+
|
|
163
|
+
The version is followed by one the ID3v2 flags field, of which
|
|
164
|
+
currently only three flags are used.
|
|
165
|
+
|
|
166
|
+
|
|
167
|
+
a - Unsynchronisation
|
|
168
|
+
|
|
169
|
+
Bit 7 in the 'ID3v2 flags' indicates whether or not
|
|
170
|
+
unsynchronisation is used (see section 5 for details); a set bit
|
|
171
|
+
indicates usage.
|
|
172
|
+
|
|
173
|
+
|
|
174
|
+
b - Extended header
|
|
175
|
+
|
|
176
|
+
The second bit (bit 6) indicates whether or not the header is
|
|
177
|
+
followed by an extended header. The extended header is described in
|
|
178
|
+
section 3.2.
|
|
179
|
+
|
|
180
|
+
|
|
181
|
+
c - Experimental indicator
|
|
182
|
+
|
|
183
|
+
The third bit (bit 5) should be used as an 'experimental
|
|
184
|
+
indicator'. This flag should always be set when the tag is in an
|
|
185
|
+
experimental stage.
|
|
186
|
+
|
|
187
|
+
All the other flags should be cleared. If one of these undefined
|
|
188
|
+
flags are set that might mean that the tag is not readable for a
|
|
189
|
+
parser that does not know the flags function.
|
|
190
|
+
|
|
191
|
+
The ID3v2 tag size is encoded with four bytes where the most
|
|
192
|
+
significant bit (bit 7) is set to zero in every byte, making a total
|
|
193
|
+
of 28 bits. The zeroed bits are ignored, so a 257 bytes long tag is
|
|
194
|
+
represented as $00 00 02 01.
|
|
195
|
+
|
|
196
|
+
The ID3v2 tag size is the size of the complete tag after
|
|
197
|
+
unsychronisation, including padding, excluding the header but not
|
|
198
|
+
excluding the extended header (total tag size - 10). Only 28 bits
|
|
199
|
+
(representing up to 256MB) are used in the size description to avoid
|
|
200
|
+
the introducuction of 'false syncsignals'.
|
|
201
|
+
|
|
202
|
+
An ID3v2 tag can be detected with the following pattern:
|
|
203
|
+
$49 44 33 yy yy xx zz zz zz zz
|
|
204
|
+
Where yy is less than $FF, xx is the 'flags' byte and zz is less than
|
|
205
|
+
$80.
|
|
206
|
+
|
|
207
|
+
|
|
208
|
+
3.2. ID3v2 extended header
|
|
209
|
+
|
|
210
|
+
The extended header contains information that is not vital to the
|
|
211
|
+
correct parsing of the tag information, hence the extended header is
|
|
212
|
+
optional.
|
|
213
|
+
|
|
214
|
+
Extended header size $xx xx xx xx
|
|
215
|
+
Extended Flags $xx xx
|
|
216
|
+
Size of padding $xx xx xx xx
|
|
217
|
+
|
|
218
|
+
Where the 'Extended header size', currently 6 or 10 bytes, excludes
|
|
219
|
+
itself. The 'Size of padding' is simply the total tag size excluding
|
|
220
|
+
the frames and the headers, in other words the padding. The extended
|
|
221
|
+
header is considered separate from the header proper, and as such is
|
|
222
|
+
subject to unsynchronisation.
|
|
223
|
+
|
|
224
|
+
The extended flags are a secondary flag set which describes further
|
|
225
|
+
attributes of the tag. These attributes are currently defined as
|
|
226
|
+
follows
|
|
227
|
+
|
|
228
|
+
%x0000000 00000000
|
|
229
|
+
|
|
230
|
+
|
|
231
|
+
x - CRC data present
|
|
232
|
+
|
|
233
|
+
If this flag is set four bytes of CRC-32 data is appended to the
|
|
234
|
+
extended header. The CRC should be calculated before
|
|
235
|
+
unsynchronisation on the data between the extended header and the
|
|
236
|
+
padding, i.e. the frames and only the frames.
|
|
237
|
+
|
|
238
|
+
Total frame CRC $xx xx xx xx
|
|
239
|
+
|
|
240
|
+
|
|
241
|
+
3.3. ID3v2 frame overview
|
|
242
|
+
|
|
243
|
+
As the tag consists of a tag header and a tag body with one or more
|
|
244
|
+
frames, all the frames consists of a frame header followed by one or
|
|
245
|
+
more fields containing the actual information. The layout of the
|
|
246
|
+
frame header:
|
|
247
|
+
|
|
248
|
+
Frame ID $xx xx xx xx (four characters)
|
|
249
|
+
Size $xx xx xx xx
|
|
250
|
+
Flags $xx xx
|
|
251
|
+
|
|
252
|
+
The frame ID made out of the characters capital A-Z and 0-9.
|
|
253
|
+
Identifiers beginning with "X", "Y" and "Z" are for experimental use
|
|
254
|
+
and free for everyone to use, without the need to set the
|
|
255
|
+
experimental bit in the tag header. Have in mind that someone else
|
|
256
|
+
might have used the same identifier as you. All other identifiers are
|
|
257
|
+
either used or reserved for future use.
|
|
258
|
+
|
|
259
|
+
The frame ID is followed by a size descriptor, making a total header
|
|
260
|
+
size of ten bytes in every frame. The size is calculated as frame
|
|
261
|
+
size excluding frame header (frame size - 10).
|
|
262
|
+
|
|
263
|
+
In the frame header the size descriptor is followed by two flags
|
|
264
|
+
bytes. These flags are described in section 3.3.1.
|
|
265
|
+
|
|
266
|
+
There is no fixed order of the frames' appearance in the tag,
|
|
267
|
+
although it is desired that the frames are arranged in order of
|
|
268
|
+
significance concerning the recognition of the file. An example of
|
|
269
|
+
such order: UFID, TIT2, MCDI, TRCK ...
|
|
270
|
+
|
|
271
|
+
A tag must contain at least one frame. A frame must be at least 1
|
|
272
|
+
byte big, excluding the header.
|
|
273
|
+
|
|
274
|
+
If nothing else is said a string is represented as ISO-8859-1
|
|
275
|
+
[ISO-8859-1] characters in the range $20 - $FF. Such strings are
|
|
276
|
+
represented as <text string>, or <full text string> if newlines are
|
|
277
|
+
allowed, in the frame descriptions. All Unicode strings [UNICODE] use
|
|
278
|
+
16-bit unicode 2.0 (ISO/IEC 10646-1:1993, UCS-2). Unicode strings
|
|
279
|
+
must begin with the Unicode BOM ($FF FE or $FE FF) to identify the
|
|
280
|
+
byte order.
|
|
281
|
+
|
|
282
|
+
All numeric strings and URLs [URL] are always encoded as ISO-8859-1.
|
|
283
|
+
Terminated strings are terminated with $00 if encoded with ISO-8859-1
|
|
284
|
+
and $00 00 if encoded as unicode. If nothing else is said newline
|
|
285
|
+
character is forbidden. In ISO-8859-1 a new line is represented, when
|
|
286
|
+
allowed, with $0A only. Frames that allow different types of text
|
|
287
|
+
encoding have a text encoding description byte directly after the
|
|
288
|
+
frame size. If ISO-8859-1 is used this byte should be $00, if Unicode
|
|
289
|
+
is used it should be $01. Strings dependent on encoding is
|
|
290
|
+
represented as <text string according to encoding>, or <full text
|
|
291
|
+
string according to encoding> if newlines are allowed. Any empty
|
|
292
|
+
Unicode strings which are NULL-terminated may have the Unicode BOM
|
|
293
|
+
followed by a Unicode NULL ($FF FE 00 00 or $FE FF 00 00).
|
|
294
|
+
|
|
295
|
+
The three byte language field is used to describe the language of the
|
|
296
|
+
frame's content, according to ISO-639-2 [ISO-639-2].
|
|
297
|
+
|
|
298
|
+
All URLs [URL] may be relative, e.g. "picture.png", "../doc.txt".
|
|
299
|
+
|
|
300
|
+
If a frame is longer than it should be, e.g. having more fields than
|
|
301
|
+
specified in this document, that indicates that additions to the
|
|
302
|
+
frame have been made in a later version of the ID3v2 standard. This
|
|
303
|
+
is reflected by the revision number in the header of the tag.
|
|
304
|
+
|
|
305
|
+
|
|
306
|
+
3.3.1. Frame header flags
|
|
307
|
+
|
|
308
|
+
In the frame header the size descriptor is followed by two flags
|
|
309
|
+
bytes. All unused flags must be cleared. The first byte is for
|
|
310
|
+
'status messages' and the second byte is for encoding purposes. If an
|
|
311
|
+
unknown flag is set in the first byte the frame may not be changed
|
|
312
|
+
without the bit cleared. If an unknown flag is set in the second byte
|
|
313
|
+
it is likely to not be readable. The flags field is defined as
|
|
314
|
+
follows.
|
|
315
|
+
|
|
316
|
+
%abc00000 %ijk00000
|
|
317
|
+
|
|
318
|
+
|
|
319
|
+
a - Tag alter preservation
|
|
320
|
+
|
|
321
|
+
This flag tells the software what to do with this frame if it is
|
|
322
|
+
unknown and the tag is altered in any way. This applies to all
|
|
323
|
+
kinds of alterations, including adding more padding and reordering
|
|
324
|
+
the frames.
|
|
325
|
+
|
|
326
|
+
0 Frame should be preserved.
|
|
327
|
+
1 Frame should be discarded.
|
|
328
|
+
|
|
329
|
+
|
|
330
|
+
b - File alter preservation
|
|
331
|
+
|
|
332
|
+
This flag tells the software what to do with this frame if it is
|
|
333
|
+
unknown and the file, excluding the tag, is altered. This does not
|
|
334
|
+
apply when the audio is completely replaced with other audio data.
|
|
335
|
+
|
|
336
|
+
0 Frame should be preserved.
|
|
337
|
+
1 Frame should be discarded.
|
|
338
|
+
|
|
339
|
+
|
|
340
|
+
c - Read only
|
|
341
|
+
|
|
342
|
+
This flag, if set, tells the software that the contents of this
|
|
343
|
+
frame is intended to be read only. Changing the contents might
|
|
344
|
+
break something, e.g. a signature. If the contents are changed,
|
|
345
|
+
without knowledge in why the frame was flagged read only and
|
|
346
|
+
without taking the proper means to compensate, e.g. recalculating
|
|
347
|
+
the signature, the bit should be cleared.
|
|
348
|
+
|
|
349
|
+
|
|
350
|
+
i - Compression
|
|
351
|
+
|
|
352
|
+
This flag indicates whether or not the frame is compressed.
|
|
353
|
+
|
|
354
|
+
0 Frame is not compressed.
|
|
355
|
+
1 Frame is compressed using zlib [zlib] with 4 bytes for
|
|
356
|
+
'decompressed size' appended to the frame header.
|
|
357
|
+
|
|
358
|
+
|
|
359
|
+
j - Encryption
|
|
360
|
+
|
|
361
|
+
This flag indicates wether or not the frame is enrypted. If set
|
|
362
|
+
one byte indicating with which method it was encrypted will be
|
|
363
|
+
appended to the frame header. See section 4.26. for more
|
|
364
|
+
information about encryption method registration.
|
|
365
|
+
|
|
366
|
+
0 Frame is not encrypted.
|
|
367
|
+
1 Frame is encrypted.
|
|
368
|
+
|
|
369
|
+
|
|
370
|
+
k - Grouping identity
|
|
371
|
+
|
|
372
|
+
This flag indicates whether or not this frame belongs in a group
|
|
373
|
+
with other frames. If set a group identifier byte is added to the
|
|
374
|
+
frame header. Every frame with the same group identifier belongs
|
|
375
|
+
to the same group.
|
|
376
|
+
|
|
377
|
+
0 Frame does not contain group information
|
|
378
|
+
1 Frame contains group information
|
|
379
|
+
|
|
380
|
+
|
|
381
|
+
Some flags indicates that the frame header is extended with
|
|
382
|
+
additional information. This information will be added to the frame
|
|
383
|
+
header in the same order as the flags indicating the additions. I.e.
|
|
384
|
+
the four bytes of decompressed size will preceed the encryption
|
|
385
|
+
method byte. These additions to the frame header, while not included
|
|
386
|
+
in the frame header size but are included in the 'frame size' field,
|
|
387
|
+
are not subject to encryption or compression.
|
|
388
|
+
|
|
389
|
+
|
|
390
|
+
3.3.2. Default flags
|
|
391
|
+
|
|
392
|
+
The default settings for the frames described in this document can be
|
|
393
|
+
divided into the following classes. The flags may be set differently
|
|
394
|
+
if found more suitable by the software.
|
|
395
|
+
|
|
396
|
+
1. Discarded if tag is altered, discarded if file is altered.
|
|
397
|
+
|
|
398
|
+
None.
|
|
399
|
+
|
|
400
|
+
2. Discarded if tag is altered, preserved if file is altered.
|
|
401
|
+
|
|
402
|
+
None.
|
|
403
|
+
|
|
404
|
+
3. Preserved if tag is altered, discarded if file is altered.
|
|
405
|
+
|
|
406
|
+
AENC, ETCO, EQUA, MLLT, POSS, SYLT, SYTC, RVAD, TENC, TLEN, TSIZ
|
|
407
|
+
|
|
408
|
+
4. Preserved if tag is altered, preserved if file is altered.
|
|
409
|
+
|
|
410
|
+
The rest of the frames.
|
|
411
|
+
|
|
412
|
+
|
|
413
|
+
4. Declared ID3v2 frames
|
|
414
|
+
|
|
415
|
+
The following frames are declared in this draft.
|
|
416
|
+
|
|
417
|
+
4.21 AENC Audio encryption
|
|
418
|
+
4.15 APIC Attached picture
|
|
419
|
+
|
|
420
|
+
4.11 COMM Comments
|
|
421
|
+
4.25 COMR Commercial frame
|
|
422
|
+
|
|
423
|
+
4.26 ENCR Encryption method registration
|
|
424
|
+
4.13 EQUA Equalization
|
|
425
|
+
4.6 ETCO Event timing codes
|
|
426
|
+
|
|
427
|
+
4.16 GEOB General encapsulated object
|
|
428
|
+
4.27 GRID Group identification registration
|
|
429
|
+
|
|
430
|
+
4.4 IPLS Involved people list
|
|
431
|
+
|
|
432
|
+
4.21 LINK Linked information
|
|
433
|
+
|
|
434
|
+
4.5 MCDI Music CD identifier
|
|
435
|
+
4.7 MLLT MPEG location lookup table
|
|
436
|
+
|
|
437
|
+
4.24 OWNE Ownership frame
|
|
438
|
+
|
|
439
|
+
4.28. PRIV Private frame
|
|
440
|
+
4.17 PCNT Play counter
|
|
441
|
+
4.18 POPM Popularimeter
|
|
442
|
+
4.22 POSS Position synchronisation frame
|
|
443
|
+
|
|
444
|
+
4.19 RBUF Recommended buffer size
|
|
445
|
+
4.12 RVAD Relative volume adjustment
|
|
446
|
+
4.14 RVRB Reverb
|
|
447
|
+
|
|
448
|
+
4.10 SYLT Synchronized lyric/text
|
|
449
|
+
4.8 SYTC Synchronized tempo codes
|
|
450
|
+
|
|
451
|
+
4.2.1 TALB Album/Movie/Show title
|
|
452
|
+
4.2.1 TBPM BPM (beats per minute)
|
|
453
|
+
4.2.1 TCOM Composer
|
|
454
|
+
4.2.1 TCON Content type
|
|
455
|
+
4.2.1 TCOP Copyright message
|
|
456
|
+
4.2.1 TDAT Date
|
|
457
|
+
4.2.1 TDLY Playlist delay
|
|
458
|
+
4.2.1 TENC Encoded by
|
|
459
|
+
4.2.1 TEXT Lyricist/Text writer
|
|
460
|
+
4.2.1 TFLT File type
|
|
461
|
+
4.2.1 TIME Time
|
|
462
|
+
4.2.1 TIT1 Content group description
|
|
463
|
+
4.2.1 TIT2 Title/songname/content description
|
|
464
|
+
4.2.1 TIT3 Subtitle/Description refinement
|
|
465
|
+
4.2.1 TKEY Initial key
|
|
466
|
+
4.2.1 TLAN Language(s)
|
|
467
|
+
4.2.1 TLEN Length
|
|
468
|
+
4.2.1 TMED Media type
|
|
469
|
+
4.2.1 TOAL Original album/movie/show title
|
|
470
|
+
4.2.1 TOFN Original filename
|
|
471
|
+
4.2.1 TOLY Original lyricist(s)/text writer(s)
|
|
472
|
+
4.2.1 TOPE Original artist(s)/performer(s)
|
|
473
|
+
4.2.1 TORY Original release year
|
|
474
|
+
4.2.1 TOWN File owner/licensee
|
|
475
|
+
4.2.1 TPE1 Lead performer(s)/Soloist(s)
|
|
476
|
+
4.2.1 TPE2 Band/orchestra/accompaniment
|
|
477
|
+
4.2.1 TPE3 Conductor/performer refinement
|
|
478
|
+
4.2.1 TPE4 Interpreted, remixed, or otherwise modified by
|
|
479
|
+
4.2.1 TPOS Part of a set
|
|
480
|
+
4.2.1 TPUB Publisher
|
|
481
|
+
4.2.1 TRCK Track number/Position in set
|
|
482
|
+
4.2.1 TRDA Recording dates
|
|
483
|
+
4.2.1 TRSN Internet radio station name
|
|
484
|
+
4.2.1 TRSO Internet radio station owner
|
|
485
|
+
4.2.1 TSIZ Size
|
|
486
|
+
4.2.1 TSRC ISRC (international standard recording code)
|
|
487
|
+
4.2.1 TSSE Software/Hardware and settings used for encoding
|
|
488
|
+
4.2.1 TYER Year
|
|
489
|
+
4.2.2 TXXX User defined text information frame
|
|
490
|
+
|
|
491
|
+
4.1 UFID Unique file identifier
|
|
492
|
+
4.23 USER Terms of use
|
|
493
|
+
4.9 USLT Unsychronized lyric/text transcription
|
|
494
|
+
|
|
495
|
+
4.3.1 WCOM Commercial information
|
|
496
|
+
4.3.1 WCOP Copyright/Legal information
|
|
497
|
+
4.3.1 WOAF Official audio file webpage
|
|
498
|
+
4.3.1 WOAR Official artist/performer webpage
|
|
499
|
+
4.3.1 WOAS Official audio source webpage
|
|
500
|
+
4.3.1 WORS Official internet radio station homepage
|
|
501
|
+
4.3.1 WPAY Payment
|
|
502
|
+
4.3.1 WPUB Publishers official webpage
|
|
503
|
+
4.3.2 WXXX User defined URL link frame
|
|
504
|
+
|
|
505
|
+
<A NAME=UFID>
|
|
506
|
+
4.1. Unique file identifier</A>
|
|
507
|
+
|
|
508
|
+
This frame's purpose is to be able to identify the audio file in a
|
|
509
|
+
database that may contain more information relevant to the content.
|
|
510
|
+
Since standardisation of such a database is beyond this document, all
|
|
511
|
+
frames begin with a null-terminated string with a URL [URL]
|
|
512
|
+
containing an email address, or a link to a location where an email
|
|
513
|
+
address can be found, that belongs to the organisation responsible
|
|
514
|
+
for this specific database implementation. Questions regarding the
|
|
515
|
+
database should be sent to the indicated email address. The URL
|
|
516
|
+
should not be used for the actual database queries. The string
|
|
517
|
+
"http://www.id3.org/dummy/ufid.html" should be used for tests.
|
|
518
|
+
Software that isn't told otherwise may safely remove such frames. The
|
|
519
|
+
'Owner identifier' must be non-empty (more than just a termination).
|
|
520
|
+
The 'Owner identifier' is then followed by the actual identifier,
|
|
521
|
+
which may be up to 64 bytes. There may be more than one "UFID" frame
|
|
522
|
+
in a tag, but only one with the same 'Owner identifier'.
|
|
523
|
+
|
|
524
|
+
<Header for 'Unique file identifier', ID: "UFID">
|
|
525
|
+
Owner identifier <text string> $00
|
|
526
|
+
Identifier <up to 64 bytes binary data>
|
|
527
|
+
|
|
528
|
+
|
|
529
|
+
4.2. Text information frames
|
|
530
|
+
|
|
531
|
+
The text information frames are the most important frames, containing
|
|
532
|
+
information like artist, album and more. There may only be one text
|
|
533
|
+
information frame of its kind in an tag. If the textstring is
|
|
534
|
+
followed by a termination ($00 (00)) all the following information
|
|
535
|
+
should be ignored and not be displayed. All text frame identifiers
|
|
536
|
+
begin with "T". Only text frame identifiers begin with "T", with the
|
|
537
|
+
exception of the "TXXX" frame. All the text information frames have
|
|
538
|
+
the following format:
|
|
539
|
+
|
|
540
|
+
<Header for 'Text information frame', ID: "T000" - "TZZZ",
|
|
541
|
+
excluding "TXXX" described in 4.2.2.>
|
|
542
|
+
Text encoding $xx
|
|
543
|
+
Information <text string according to encoding>
|
|
544
|
+
|
|
545
|
+
|
|
546
|
+
4.2.1. Text information frames - details
|
|
547
|
+
|
|
548
|
+
<A NAME=TALB>TALB</A>
|
|
549
|
+
The 'Album/Movie/Show title' frame is intended for the title of the
|
|
550
|
+
recording(/source of sound) which the audio in the file is taken
|
|
551
|
+
from.
|
|
552
|
+
|
|
553
|
+
<A NAME=TBPM>TBPM</A>
|
|
554
|
+
The 'BPM' frame contains the number of beats per minute in the
|
|
555
|
+
mainpart of the audio. The BPM is an integer and represented as a
|
|
556
|
+
numerical string.
|
|
557
|
+
|
|
558
|
+
<A NAME=TCOM>TCOM</A>
|
|
559
|
+
The 'Composer(s)' frame is intended for the name of the composer(s).
|
|
560
|
+
They are seperated with the "/" character.
|
|
561
|
+
|
|
562
|
+
<A NAME=TCON>TCON</A>
|
|
563
|
+
The 'Content type', which previously was stored as a one byte numeric
|
|
564
|
+
value only, is now a numeric string. You may use one or several of
|
|
565
|
+
the types as ID3v1.1 did or, since the category list would be
|
|
566
|
+
impossible to maintain with accurate and up to date categories,
|
|
567
|
+
define your own.
|
|
568
|
+
|
|
569
|
+
References to the ID3v1 genres can be made by, as first byte, enter
|
|
570
|
+
"(" followed by a number from the genres list (appendix A.) and
|
|
571
|
+
ended with a ")" character. This is optionally followed by a
|
|
572
|
+
refinement, e.g. "(21)" or "(4)Eurodisco". Several references can be
|
|
573
|
+
made in the same frame, e.g. "(51)(39)". If the refinement should
|
|
574
|
+
begin with a "(" character it should be replaced with "((", e.g. "((I
|
|
575
|
+
can figure out any genre)" or "(55)((I think...)". The following new
|
|
576
|
+
content types is defined in ID3v2 and is implemented in the same way
|
|
577
|
+
as the numerig content types, e.g. "(RX)".
|
|
578
|
+
|
|
579
|
+
RX Remix
|
|
580
|
+
CR Cover
|
|
581
|
+
|
|
582
|
+
<A NAME=TCOP>TCOP</A>
|
|
583
|
+
The 'Copyright message' frame, which must begin with a year and a
|
|
584
|
+
space character (making five characters), is intended for the
|
|
585
|
+
copyright holder of the original sound, not the audio file itself.
|
|
586
|
+
The absence of this frame means only that the copyright information
|
|
587
|
+
is unavailable or has been removed, and must not be interpreted to
|
|
588
|
+
mean that the sound is public domain. Every time this field is
|
|
589
|
+
displayed the field must be preceded with "Copyright " (C) " ", where
|
|
590
|
+
(C) is one character showing a C in a circle.
|
|
591
|
+
|
|
592
|
+
<A NAME=TDAT>TDAT</A>
|
|
593
|
+
The 'Date' frame is a numeric string in the DDMM format containing
|
|
594
|
+
the date for the recording. This field is always four characters
|
|
595
|
+
long.
|
|
596
|
+
|
|
597
|
+
<A NAME=TDLY>TDLY</A>
|
|
598
|
+
The 'Playlist delay' defines the numbers of milliseconds of silence
|
|
599
|
+
between every song in a playlist. The player should use the "ETC"
|
|
600
|
+
frame, if present, to skip initial silence and silence at the end of
|
|
601
|
+
the audio to match the 'Playlist delay' time. The time is represented
|
|
602
|
+
as a numeric string.
|
|
603
|
+
|
|
604
|
+
<A NAME=TENC>TENC</A>
|
|
605
|
+
The 'Encoded by' frame contains the name of the person or
|
|
606
|
+
organisation that encoded the audio file. This field may contain a
|
|
607
|
+
copyright message, if the audio file also is copyrighted by the
|
|
608
|
+
encoder.
|
|
609
|
+
|
|
610
|
+
<A NAME=TEXT>TEXT</A>
|
|
611
|
+
The 'Lyricist(s)/Text writer(s)' frame is intended for the writer(s)
|
|
612
|
+
of the text or lyrics in the recording. They are seperated with the
|
|
613
|
+
"/" character.
|
|
614
|
+
|
|
615
|
+
<A NAME=TFLT>TFLT</A>
|
|
616
|
+
The 'File type' frame indicates which type of audio this tag defines.
|
|
617
|
+
The following type and refinements are defined:
|
|
618
|
+
|
|
619
|
+
MPG MPEG Audio
|
|
620
|
+
/1 MPEG 1/2 layer I
|
|
621
|
+
/2 MPEG 1/2 layer II
|
|
622
|
+
/3 MPEG 1/2 layer III
|
|
623
|
+
/2.5 MPEG 2.5
|
|
624
|
+
/AAC Advanced audio compression
|
|
625
|
+
VQF Transform-domain Weighted Interleave Vector Quantization
|
|
626
|
+
PCM Pulse Code Modulated audio
|
|
627
|
+
|
|
628
|
+
but other types may be used, not for these types though. This is used
|
|
629
|
+
in a similar way to the predefined types in the "TMED" frame, but
|
|
630
|
+
without parentheses. If this frame is not present audio type is
|
|
631
|
+
assumed to be "MPG".
|
|
632
|
+
|
|
633
|
+
<A NAME=TIME>TIME</A>
|
|
634
|
+
The 'Time' frame is a numeric string in the HHMM format containing
|
|
635
|
+
the time for the recording. This field is always four characters
|
|
636
|
+
long.
|
|
637
|
+
|
|
638
|
+
<A NAME=TIT1>TIT1</A>
|
|
639
|
+
The 'Content group description' frame is used if the sound belongs to
|
|
640
|
+
a larger category of sounds/music. For example, classical music is
|
|
641
|
+
often sorted in different musical sections (e.g. "Piano Concerto",
|
|
642
|
+
"Weather - Hurricane").
|
|
643
|
+
|
|
644
|
+
<A NAME=TIT2>TIT2</A>
|
|
645
|
+
The 'Title/Songname/Content description' frame is the actual name of
|
|
646
|
+
the piece (e.g. "Adagio", "Hurricane Donna").
|
|
647
|
+
|
|
648
|
+
<A NAME=TIT3>TIT3</A>
|
|
649
|
+
The 'Subtitle/Description refinement' frame is used for information
|
|
650
|
+
directly related to the contents title (e.g. "Op. 16" or "Performed
|
|
651
|
+
live at Wembley").
|
|
652
|
+
|
|
653
|
+
<A NAME=TKEY>TKEY</A>
|
|
654
|
+
The 'Initial key' frame contains the musical key in which the sound
|
|
655
|
+
starts. It is represented as a string with a maximum length of three
|
|
656
|
+
characters. The ground keys are represented with "A","B","C","D","E",
|
|
657
|
+
"F" and "G" and halfkeys represented with "b" and "#". Minor is
|
|
658
|
+
represented as "m". Example "Cbm". Off key is represented with an "o"
|
|
659
|
+
only.
|
|
660
|
+
|
|
661
|
+
<A NAME=TLAN>TLAN</A>
|
|
662
|
+
The 'Language(s)' frame should contain the languages of the text or
|
|
663
|
+
lyrics spoken or sung in the audio. The language is represented with
|
|
664
|
+
three characters according to ISO-639-2. If more than one language is
|
|
665
|
+
used in the text their language codes should follow according to
|
|
666
|
+
their usage.
|
|
667
|
+
|
|
668
|
+
<A NAME=TLEN>TLEN</A>
|
|
669
|
+
The 'Length' frame contains the length of the audiofile in
|
|
670
|
+
milliseconds, represented as a numeric string.
|
|
671
|
+
|
|
672
|
+
<A NAME=TMED>TMED</A>
|
|
673
|
+
The 'Media type' frame describes from which media the sound
|
|
674
|
+
originated. This may be a text string or a reference to the
|
|
675
|
+
predefined media types found in the list below. References are made
|
|
676
|
+
within "(" and ")" and are optionally followed by a text refinement,
|
|
677
|
+
e.g. "(MC) with four channels". If a text refinement should begin
|
|
678
|
+
with a "(" character it should be replaced with "((" in the same way
|
|
679
|
+
as in the "TCO" frame. Predefined refinements is appended after the
|
|
680
|
+
media type, e.g. "(CD/A)" or "(VID/PAL/VHS)".
|
|
681
|
+
|
|
682
|
+
DIG Other digital media
|
|
683
|
+
/A Analog transfer from media
|
|
684
|
+
|
|
685
|
+
ANA Other analog media
|
|
686
|
+
/WAC Wax cylinder
|
|
687
|
+
/8CA 8-track tape cassette
|
|
688
|
+
|
|
689
|
+
CD CD
|
|
690
|
+
/A Analog transfer from media
|
|
691
|
+
/DD DDD
|
|
692
|
+
/AD ADD
|
|
693
|
+
/AA AAD
|
|
694
|
+
|
|
695
|
+
LD Laserdisc
|
|
696
|
+
/A Analog transfer from media
|
|
697
|
+
|
|
698
|
+
TT Turntable records
|
|
699
|
+
/33 33.33 rpm
|
|
700
|
+
/45 45 rpm
|
|
701
|
+
/71 71.29 rpm
|
|
702
|
+
/76 76.59 rpm
|
|
703
|
+
/78 78.26 rpm
|
|
704
|
+
/80 80 rpm
|
|
705
|
+
|
|
706
|
+
MD MiniDisc
|
|
707
|
+
/A Analog transfer from media
|
|
708
|
+
|
|
709
|
+
DAT DAT
|
|
710
|
+
/A Analog transfer from media
|
|
711
|
+
/1 standard, 48 kHz/16 bits, linear
|
|
712
|
+
/2 mode 2, 32 kHz/16 bits, linear
|
|
713
|
+
/3 mode 3, 32 kHz/12 bits, nonlinear, low speed
|
|
714
|
+
/4 mode 4, 32 kHz/12 bits, 4 channels
|
|
715
|
+
/5 mode 5, 44.1 kHz/16 bits, linear
|
|
716
|
+
/6 mode 6, 44.1 kHz/16 bits, 'wide track' play
|
|
717
|
+
|
|
718
|
+
DCC DCC
|
|
719
|
+
/A Analog transfer from media
|
|
720
|
+
|
|
721
|
+
DVD DVD
|
|
722
|
+
/A Analog transfer from media
|
|
723
|
+
|
|
724
|
+
TV Television
|
|
725
|
+
/PAL PAL
|
|
726
|
+
/NTSC NTSC
|
|
727
|
+
/SECAM SECAM
|
|
728
|
+
|
|
729
|
+
VID Video
|
|
730
|
+
/PAL PAL
|
|
731
|
+
/NTSC NTSC
|
|
732
|
+
/SECAM SECAM
|
|
733
|
+
/VHS VHS
|
|
734
|
+
/SVHS S-VHS
|
|
735
|
+
/BETA BETAMAX
|
|
736
|
+
|
|
737
|
+
RAD Radio
|
|
738
|
+
/FM FM
|
|
739
|
+
/AM AM
|
|
740
|
+
/LW LW
|
|
741
|
+
/MW MW
|
|
742
|
+
|
|
743
|
+
TEL Telephone
|
|
744
|
+
/I ISDN
|
|
745
|
+
|
|
746
|
+
MC MC (normal cassette)
|
|
747
|
+
/4 4.75 cm/s (normal speed for a two sided cassette)
|
|
748
|
+
/9 9.5 cm/s
|
|
749
|
+
/I Type I cassette (ferric/normal)
|
|
750
|
+
/II Type II cassette (chrome)
|
|
751
|
+
/III Type III cassette (ferric chrome)
|
|
752
|
+
/IV Type IV cassette (metal)
|
|
753
|
+
|
|
754
|
+
REE Reel
|
|
755
|
+
/9 9.5 cm/s
|
|
756
|
+
/19 19 cm/s
|
|
757
|
+
/38 38 cm/s
|
|
758
|
+
/76 76 cm/s
|
|
759
|
+
/I Type I cassette (ferric/normal)
|
|
760
|
+
/II Type II cassette (chrome)
|
|
761
|
+
/III Type III cassette (ferric chrome)
|
|
762
|
+
/IV Type IV cassette (metal)
|
|
763
|
+
|
|
764
|
+
<A NAME=TOAL>TOAL</A>
|
|
765
|
+
The 'Original album/movie/show title' frame is intended for the title
|
|
766
|
+
of the original recording (or source of sound), if for example the
|
|
767
|
+
music in the file should be a cover of a previously released song.
|
|
768
|
+
|
|
769
|
+
<A NAME=TOFN>TOFN</A>
|
|
770
|
+
The 'Original filename' frame contains the preferred filename for the
|
|
771
|
+
file, since some media doesn't allow the desired length of the
|
|
772
|
+
filename. The filename is case sensitive and includes its suffix.
|
|
773
|
+
|
|
774
|
+
<A NAME=TOLY>TOLY</A>
|
|
775
|
+
The 'Original lyricist(s)/text writer(s)' frame is intended for the
|
|
776
|
+
text writer(s) of the original recording, if for example the music in
|
|
777
|
+
the file should be a cover of a previously released song. The text
|
|
778
|
+
writers are seperated with the "/" character.
|
|
779
|
+
|
|
780
|
+
<A NAME=TOPE>TOPE</A>
|
|
781
|
+
The 'Original artist(s)/performer(s)' frame is intended for the
|
|
782
|
+
performer(s) of the original recording, if for example the music in
|
|
783
|
+
the file should be a cover of a previously released song. The
|
|
784
|
+
performers are seperated with the "/" character.
|
|
785
|
+
|
|
786
|
+
<A NAME=TORY>TORY</A>
|
|
787
|
+
The 'Original release year' frame is intended for the year when the
|
|
788
|
+
original recording, if for example the music in the file should be a
|
|
789
|
+
cover of a previously released song, was released. The field is
|
|
790
|
+
formatted as in the "TYER" frame.
|
|
791
|
+
|
|
792
|
+
<A NAME=TOWN>TOWN</A>
|
|
793
|
+
The 'File owner/licensee' frame contains the name of the owner or
|
|
794
|
+
licensee of the file and it's contents.
|
|
795
|
+
|
|
796
|
+
<A NAME=TPE1>TPE1</A>
|
|
797
|
+
The 'Lead artist(s)/Lead performer(s)/Soloist(s)/Performing group' is
|
|
798
|
+
used for the main artist(s). They are seperated with the "/"
|
|
799
|
+
character.
|
|
800
|
+
|
|
801
|
+
<A NAME=TPE2>TPE2</A>
|
|
802
|
+
The 'Band/Orchestra/Accompaniment' frame is used for additional
|
|
803
|
+
information about the performers in the recording.
|
|
804
|
+
|
|
805
|
+
<A NAME=TPE3>TPE3</A>
|
|
806
|
+
The 'Conductor' frame is used for the name of the conductor.
|
|
807
|
+
|
|
808
|
+
<A NAME=TPE4>TPE4</A>
|
|
809
|
+
The 'Interpreted, remixed, or otherwise modified by' frame contains
|
|
810
|
+
more information about the people behind a remix and similar
|
|
811
|
+
interpretations of another existing piece.
|
|
812
|
+
|
|
813
|
+
<A NAME=TPOS>TPOS</A>
|
|
814
|
+
The 'Part of a set' frame is a numeric string that describes which
|
|
815
|
+
part of a set the audio came from. This frame is used if the source
|
|
816
|
+
described in the "TALB" frame is divided into several mediums, e.g. a
|
|
817
|
+
double CD. The value may be extended with a "/" character and a
|
|
818
|
+
numeric string containing the total number of parts in the set. E.g.
|
|
819
|
+
"1/2".
|
|
820
|
+
|
|
821
|
+
<A NAME=TPUB>TPUB</A>
|
|
822
|
+
The 'Publisher' frame simply contains the name of the label or
|
|
823
|
+
publisher.
|
|
824
|
+
|
|
825
|
+
<A NAME=TRCK>TRCK</A>
|
|
826
|
+
The 'Track number/Position in set' frame is a numeric string
|
|
827
|
+
containing the order number of the audio-file on its original
|
|
828
|
+
recording. This may be extended with a "/" character and a numeric
|
|
829
|
+
string containing the total numer of tracks/elements on the original
|
|
830
|
+
recording. E.g. "4/9".
|
|
831
|
+
|
|
832
|
+
<A NAME=TRDA>TRDA</A>
|
|
833
|
+
The 'Recording dates' frame is a intended to be used as complement to
|
|
834
|
+
the "TYER", "TDAT" and "TIME" frames. E.g. "4th-7th June, 12th June"
|
|
835
|
+
in combination with the "TYER" frame.
|
|
836
|
+
|
|
837
|
+
<A NAME=TRSN>TRSN</A>
|
|
838
|
+
The 'Internet radio station name' frame contains the name of the
|
|
839
|
+
internet radio station from which the audio is streamed.
|
|
840
|
+
|
|
841
|
+
<A NAME=TRSO>TRSO</A>
|
|
842
|
+
The 'Internet radio station owner' frame contains the name of the
|
|
843
|
+
owner of the internet radio station from which the audio is
|
|
844
|
+
streamed.
|
|
845
|
+
|
|
846
|
+
<A NAME=TSIZ>TSIZ</A>
|
|
847
|
+
The 'Size' frame contains the size of the audiofile in bytes,
|
|
848
|
+
excluding the ID3v2 tag, represented as a numeric string.
|
|
849
|
+
|
|
850
|
+
<A NAME=TSRC>TSRC</A>
|
|
851
|
+
The 'ISRC' frame should contain the International Standard Recording
|
|
852
|
+
Code [ISRC] (12 characters).
|
|
853
|
+
|
|
854
|
+
<A NAME=TSSE>TSSE</A>
|
|
855
|
+
The 'Software/Hardware and settings used for encoding' frame
|
|
856
|
+
includes the used audio encoder and its settings when the file was
|
|
857
|
+
encoded. Hardware refers to hardware encoders, not the computer on
|
|
858
|
+
which a program was run.
|
|
859
|
+
|
|
860
|
+
<A NAME=TYER>TYER</A>
|
|
861
|
+
The 'Year' frame is a numeric string with a year of the recording.
|
|
862
|
+
This frames is always four characters long (until the year 10000).
|
|
863
|
+
|
|
864
|
+
<A NAME=TXXX>
|
|
865
|
+
4.2.2. User defined text information frame</A>
|
|
866
|
+
|
|
867
|
+
This frame is intended for one-string text information concerning the
|
|
868
|
+
audiofile in a similar way to the other "T"-frames. The frame body
|
|
869
|
+
consists of a description of the string, represented as a terminated
|
|
870
|
+
string, followed by the actual string. There may be more than one
|
|
871
|
+
"TXXX" frame in each tag, but only one with the same description.
|
|
872
|
+
|
|
873
|
+
<Header for 'User defined text information frame', ID: "TXXX">
|
|
874
|
+
Text encoding $xx
|
|
875
|
+
Description <text string according to encoding> $00 (00)
|
|
876
|
+
Value <text string according to encoding>
|
|
877
|
+
|
|
878
|
+
|
|
879
|
+
4.3. URL link frames
|
|
880
|
+
|
|
881
|
+
With these frames dynamic data such as webpages with touring
|
|
882
|
+
information, price information or plain ordinary news can be added to
|
|
883
|
+
the tag. There may only be one URL [URL] link frame of its kind in an
|
|
884
|
+
tag, except when stated otherwise in the frame description. If the
|
|
885
|
+
textstring is followed by a termination ($00 (00)) all the following
|
|
886
|
+
information should be ignored and not be displayed. All URL link
|
|
887
|
+
frame identifiers begins with "W". Only URL link frame identifiers
|
|
888
|
+
begins with "W". All URL link frames have the following format:
|
|
889
|
+
|
|
890
|
+
<Header for 'URL link frame', ID: "W000" - "WZZZ", excluding "WXXX"
|
|
891
|
+
described in 4.3.2.>
|
|
892
|
+
URL <text string>
|
|
893
|
+
|
|
894
|
+
|
|
895
|
+
4.3.1. URL link frames - details
|
|
896
|
+
|
|
897
|
+
<A NAME=WCOM>WCOM</A>
|
|
898
|
+
The 'Commercial information' frame is a URL pointing at a webpage
|
|
899
|
+
with information such as where the album can be bought. There may be
|
|
900
|
+
more than one "WCOM" frame in a tag, but not with the same content.
|
|
901
|
+
|
|
902
|
+
<A NAME=WCOP>WCOP</A>
|
|
903
|
+
The 'Copyright/Legal information' frame is a URL pointing at a
|
|
904
|
+
webpage where the terms of use and ownership of the file is
|
|
905
|
+
described.
|
|
906
|
+
|
|
907
|
+
<A NAME=WOAF>WOAF</A>
|
|
908
|
+
The 'Official audio file webpage' frame is a URL pointing at a file
|
|
909
|
+
specific webpage.
|
|
910
|
+
|
|
911
|
+
<A NAME=WOAR>WOAR</A>
|
|
912
|
+
The 'Official artist/performer webpage' frame is a URL pointing at
|
|
913
|
+
the artists official webpage. There may be more than one "WOAR" frame
|
|
914
|
+
in a tag if the audio contains more than one performer, but not with
|
|
915
|
+
the same content.
|
|
916
|
+
|
|
917
|
+
<A NAME=WOAS>WOAS</A>
|
|
918
|
+
The 'Official audio source webpage' frame is a URL pointing at the
|
|
919
|
+
official webpage for the source of the audio file, e.g. a movie.
|
|
920
|
+
|
|
921
|
+
<A NAME=WORS>WORS</A>
|
|
922
|
+
The 'Official internet radio station homepage' contains a URL
|
|
923
|
+
pointing at the homepage of the internet radio station.
|
|
924
|
+
|
|
925
|
+
<A NAME=WPAY>WPAY</A>
|
|
926
|
+
The 'Payment' frame is a URL pointing at a webpage that will handle
|
|
927
|
+
the process of paying for this file.
|
|
928
|
+
|
|
929
|
+
<A NAME=WPUB>WPUB</A>
|
|
930
|
+
The 'Publishers official webpage' frame is a URL pointing at the
|
|
931
|
+
official wepage for the publisher.
|
|
932
|
+
|
|
933
|
+
<A NAME=WXXX>
|
|
934
|
+
4.3.2. User defined URL link frame</A>
|
|
935
|
+
|
|
936
|
+
This frame is intended for URL [URL] links concerning the audiofile
|
|
937
|
+
in a similar way to the other "W"-frames. The frame body consists
|
|
938
|
+
of a description of the string, represented as a terminated string,
|
|
939
|
+
followed by the actual URL. The URL is always encoded with ISO-8859-1
|
|
940
|
+
[ISO-8859-1]. There may be more than one "WXXX" frame in each tag,
|
|
941
|
+
but only one with the same description.
|
|
942
|
+
|
|
943
|
+
<Header for 'User defined URL link frame', ID: "WXXX">
|
|
944
|
+
Text encoding $xx
|
|
945
|
+
Description <text string according to encoding> $00 (00)
|
|
946
|
+
URL <text string>
|
|
947
|
+
|
|
948
|
+
<A NAME=IPLS>
|
|
949
|
+
4.4. Involved people list</A>
|
|
950
|
+
|
|
951
|
+
Since there might be a lot of people contributing to an audio file in
|
|
952
|
+
various ways, such as musicians and technicians, the 'Text
|
|
953
|
+
information frames' are often insufficient to list everyone involved
|
|
954
|
+
in a project. The 'Involved people list' is a frame containing the
|
|
955
|
+
names of those involved, and how they were involved. The body simply
|
|
956
|
+
contains a terminated string with the involvement directly followed
|
|
957
|
+
by a terminated string with the involvee followed by a new
|
|
958
|
+
involvement and so on. There may only be one "IPLS" frame in each
|
|
959
|
+
tag.
|
|
960
|
+
|
|
961
|
+
<Header for 'Involved people list', ID: "IPLS">
|
|
962
|
+
Text encoding $xx
|
|
963
|
+
People list strings <text strings according to encoding>
|
|
964
|
+
|
|
965
|
+
<A NAME=MCDI>
|
|
966
|
+
4.5. Music CD identifier</A>
|
|
967
|
+
|
|
968
|
+
This frame is intended for music that comes from a CD, so that the CD
|
|
969
|
+
can be identified in databases such as the CDDB [CDDB]. The frame
|
|
970
|
+
consists of a binary dump of the Table Of Contents, TOC, from the CD,
|
|
971
|
+
which is a header of 4 bytes and then 8 bytes/track on the CD plus 8
|
|
972
|
+
bytes for the 'lead out' making a maximum of 804 bytes. The offset to
|
|
973
|
+
the beginning of every track on the CD should be described with a
|
|
974
|
+
four bytes absolute CD-frame address per track, and not with absolute
|
|
975
|
+
time. This frame requires a present and valid "TRCK" frame, even if
|
|
976
|
+
the CD's only got one track. There may only be one "MCDI" frame in
|
|
977
|
+
each tag.
|
|
978
|
+
|
|
979
|
+
<Header for 'Music CD identifier', ID: "MCDI">
|
|
980
|
+
CD TOC <binary data>
|
|
981
|
+
|
|
982
|
+
<A NAME=ETCO>
|
|
983
|
+
4.6. Event timing codes</A>
|
|
984
|
+
|
|
985
|
+
This frame allows synchronisation with key events in a song or sound.
|
|
986
|
+
The header is:
|
|
987
|
+
|
|
988
|
+
<Header for 'Event timing codes', ID: "ETCO">
|
|
989
|
+
Time stamp format $xx
|
|
990
|
+
|
|
991
|
+
Where time stamp format is:
|
|
992
|
+
|
|
993
|
+
$01 Absolute time, 32 bit sized, using MPEG [MPEG] frames as unit
|
|
994
|
+
$02 Absolute time, 32 bit sized, using milliseconds as unit
|
|
995
|
+
|
|
996
|
+
Abolute time means that every stamp contains the time from the
|
|
997
|
+
beginning of the file.
|
|
998
|
+
|
|
999
|
+
Followed by a list of key events in the following format:
|
|
1000
|
+
|
|
1001
|
+
Type of event $xx
|
|
1002
|
+
Time stamp $xx (xx ...)
|
|
1003
|
+
|
|
1004
|
+
The 'Time stamp' is set to zero if directly at the beginning of the
|
|
1005
|
+
sound or after the previous event. All events should be sorted in
|
|
1006
|
+
chronological order. The type of event is as follows:
|
|
1007
|
+
|
|
1008
|
+
$00 padding (has no meaning)
|
|
1009
|
+
$01 end of initial silence
|
|
1010
|
+
$02 intro start
|
|
1011
|
+
$03 mainpart start
|
|
1012
|
+
$04 outro start
|
|
1013
|
+
$05 outro end
|
|
1014
|
+
$06 verse start
|
|
1015
|
+
$07 refrain start
|
|
1016
|
+
$08 interlude start
|
|
1017
|
+
$09 theme start
|
|
1018
|
+
$0A variation start
|
|
1019
|
+
$0B key change
|
|
1020
|
+
$0C time change
|
|
1021
|
+
$0D momentary unwanted noise (Snap, Crackle & Pop)
|
|
1022
|
+
$0E sustained noise
|
|
1023
|
+
$0F sustained noise end
|
|
1024
|
+
$10 intro end
|
|
1025
|
+
$11 mainpart end
|
|
1026
|
+
$12 verse end
|
|
1027
|
+
$13 refrain end
|
|
1028
|
+
$14 theme end
|
|
1029
|
+
|
|
1030
|
+
$15-$DF reserved for future use
|
|
1031
|
+
|
|
1032
|
+
$E0-$EF not predefined sync 0-F
|
|
1033
|
+
|
|
1034
|
+
$F0-$FC reserved for future use
|
|
1035
|
+
|
|
1036
|
+
$FD audio end (start of silence)
|
|
1037
|
+
$FE audio file ends
|
|
1038
|
+
$FF one more byte of events follows (all the following bytes with
|
|
1039
|
+
the value $FF have the same function)
|
|
1040
|
+
|
|
1041
|
+
Terminating the start events such as "intro start" is not required.
|
|
1042
|
+
The 'Not predefined sync's ($E0-EF) are for user events. You might
|
|
1043
|
+
want to synchronise your music to something, like setting of an
|
|
1044
|
+
explosion on-stage, turning on your screensaver etc.
|
|
1045
|
+
|
|
1046
|
+
There may only be one "ETCO" frame in each tag.
|
|
1047
|
+
|
|
1048
|
+
<A NAME=MLLT>
|
|
1049
|
+
4.7. MPEG location lookup table</A>
|
|
1050
|
+
|
|
1051
|
+
To increase performance and accuracy of jumps within a MPEG [MPEG]
|
|
1052
|
+
audio file, frames with timecodes in different locations in the file
|
|
1053
|
+
might be useful. The ID3v2 frame includes references that the
|
|
1054
|
+
software can use to calculate positions in the file. After the frame
|
|
1055
|
+
header is a descriptor of how much the 'frame counter' should
|
|
1056
|
+
increase for every reference. If this value is two then the first
|
|
1057
|
+
reference points out the second frame, the 2nd reference the 4th
|
|
1058
|
+
frame, the 3rd reference the 6th frame etc. In a similar way the
|
|
1059
|
+
'bytes between reference' and 'milliseconds between reference' points
|
|
1060
|
+
out bytes and milliseconds respectively.
|
|
1061
|
+
|
|
1062
|
+
Each reference consists of two parts; a certain number of bits, as
|
|
1063
|
+
defined in 'bits for bytes deviation', that describes the difference
|
|
1064
|
+
between what is said in 'bytes between reference' and the reality and
|
|
1065
|
+
a certain number of bits, as defined in 'bits for milliseconds
|
|
1066
|
+
deviation', that describes the difference between what is said in
|
|
1067
|
+
'milliseconds between reference' and the reality. The number of bits
|
|
1068
|
+
in every reference, i.e. 'bits for bytes deviation'+'bits for
|
|
1069
|
+
milliseconds deviation', must be a multiple of four. There may only
|
|
1070
|
+
be one "MLLT" frame in each tag.
|
|
1071
|
+
|
|
1072
|
+
<Header for 'Location lookup table', ID: "MLLT">
|
|
1073
|
+
MPEG frames between reference $xx xx
|
|
1074
|
+
Bytes between reference $xx xx xx
|
|
1075
|
+
Milliseconds between reference $xx xx xx
|
|
1076
|
+
Bits for bytes deviation $xx
|
|
1077
|
+
Bits for milliseconds dev. $xx
|
|
1078
|
+
|
|
1079
|
+
Then for every reference the following data is included;
|
|
1080
|
+
|
|
1081
|
+
Deviation in bytes %xxx....
|
|
1082
|
+
Deviation in milliseconds %xxx....
|
|
1083
|
+
|
|
1084
|
+
<A NAME=SYTC>
|
|
1085
|
+
4.8. Synchronised tempo codes</A>
|
|
1086
|
+
|
|
1087
|
+
For a more accurate description of the tempo of a musical piece this
|
|
1088
|
+
frame might be used. After the header follows one byte describing
|
|
1089
|
+
which time stamp format should be used. Then follows one or more
|
|
1090
|
+
tempo codes. Each tempo code consists of one tempo part and one time
|
|
1091
|
+
part. The tempo is in BPM described with one or two bytes. If the
|
|
1092
|
+
first byte has the value $FF, one more byte follows, which is added
|
|
1093
|
+
to the first giving a range from 2 - 510 BPM, since $00 and $01 is
|
|
1094
|
+
reserved. $00 is used to describe a beat-free time period, which is
|
|
1095
|
+
not the same as a music-free time period. $01 is used to indicate one
|
|
1096
|
+
single beat-stroke followed by a beat-free period.
|
|
1097
|
+
|
|
1098
|
+
The tempo descriptor is followed by a time stamp. Every time the
|
|
1099
|
+
tempo in the music changes, a tempo descriptor may indicate this for
|
|
1100
|
+
the player. All tempo descriptors should be sorted in chronological
|
|
1101
|
+
order. The first beat-stroke in a time-period is at the same time as
|
|
1102
|
+
the beat description occurs. There may only be one "SYTC" frame in
|
|
1103
|
+
each tag.
|
|
1104
|
+
|
|
1105
|
+
<Header for 'Synchronised tempo codes', ID: "SYTC">
|
|
1106
|
+
Time stamp format $xx
|
|
1107
|
+
Tempo data <binary data>
|
|
1108
|
+
|
|
1109
|
+
Where time stamp format is:
|
|
1110
|
+
|
|
1111
|
+
$01 Absolute time, 32 bit sized, using MPEG [MPEG] frames as unit
|
|
1112
|
+
$02 Absolute time, 32 bit sized, using milliseconds as unit
|
|
1113
|
+
|
|
1114
|
+
Abolute time means that every stamp contains the time from the
|
|
1115
|
+
beginning of the file.
|
|
1116
|
+
|
|
1117
|
+
<A NAME=USLT>
|
|
1118
|
+
4.9. Unsychronised lyrics/text transcription</A>
|
|
1119
|
+
|
|
1120
|
+
This frame contains the lyrics of the song or a text transcription of
|
|
1121
|
+
other vocal activities. The head includes an encoding descriptor and
|
|
1122
|
+
a content descriptor. The body consists of the actual text. The
|
|
1123
|
+
'Content descriptor' is a terminated string. If no descriptor is
|
|
1124
|
+
entered, 'Content descriptor' is $00 (00) only. Newline characters
|
|
1125
|
+
are allowed in the text. There may be more than one 'Unsynchronised
|
|
1126
|
+
lyrics/text transcription' frame in each tag, but only one with the
|
|
1127
|
+
same language and content descriptor.
|
|
1128
|
+
|
|
1129
|
+
<Header for 'Unsynchronised lyrics/text transcription', ID: "USLT">
|
|
1130
|
+
Text encoding $xx
|
|
1131
|
+
Language $xx xx xx
|
|
1132
|
+
Content descriptor <text string according to encoding> $00 (00)
|
|
1133
|
+
Lyrics/text <full text string according to encoding>
|
|
1134
|
+
|
|
1135
|
+
<A NAME=SYLT>
|
|
1136
|
+
4.10. Synchronised lyrics/text</A>
|
|
1137
|
+
|
|
1138
|
+
This is another way of incorporating the words, said or sung lyrics,
|
|
1139
|
+
in the audio file as text, this time, however, in sync with the
|
|
1140
|
+
audio. It might also be used to describing events e.g. occurring on a
|
|
1141
|
+
stage or on the screen in sync with the audio. The header includes a
|
|
1142
|
+
content descriptor, represented with as terminated textstring. If no
|
|
1143
|
+
descriptor is entered, 'Content descriptor' is $00 (00) only.
|
|
1144
|
+
|
|
1145
|
+
<Header for 'Synchronised lyrics/text', ID: "SYLT">
|
|
1146
|
+
Text encoding $xx
|
|
1147
|
+
Language $xx xx xx
|
|
1148
|
+
Time stamp format $xx
|
|
1149
|
+
Content type $xx
|
|
1150
|
+
Content descriptor <text string according to encoding> $00 (00)
|
|
1151
|
+
|
|
1152
|
+
|
|
1153
|
+
Encoding: $00 ISO-8859-1 [ISO-8859-1] character set is used => $00
|
|
1154
|
+
is sync identifier.
|
|
1155
|
+
$01 Unicode [UNICODE] character set is used => $00 00 is
|
|
1156
|
+
sync identifier.
|
|
1157
|
+
|
|
1158
|
+
Content type: $00 is other
|
|
1159
|
+
$01 is lyrics
|
|
1160
|
+
$02 is text transcription
|
|
1161
|
+
$03 is movement/part name (e.g. "Adagio")
|
|
1162
|
+
$04 is events (e.g. "Don Quijote enters the stage")
|
|
1163
|
+
$05 is chord (e.g. "Bb F Fsus")
|
|
1164
|
+
$06 is trivia/'pop up' information
|
|
1165
|
+
|
|
1166
|
+
Time stamp format is:
|
|
1167
|
+
|
|
1168
|
+
$01 Absolute time, 32 bit sized, using MPEG [MPEG] frames as unit
|
|
1169
|
+
$02 Absolute time, 32 bit sized, using milliseconds as unit
|
|
1170
|
+
|
|
1171
|
+
Abolute time means that every stamp contains the time from the
|
|
1172
|
+
beginning of the file.
|
|
1173
|
+
|
|
1174
|
+
The text that follows the frame header differs from that of the
|
|
1175
|
+
unsynchronised lyrics/text transcription in one major way. Each
|
|
1176
|
+
syllable (or whatever size of text is considered to be convenient by
|
|
1177
|
+
the encoder) is a null terminated string followed by a time stamp
|
|
1178
|
+
denoting where in the sound file it belongs. Each sync thus has the
|
|
1179
|
+
following structure:
|
|
1180
|
+
|
|
1181
|
+
Terminated text to be synced (typically a syllable)
|
|
1182
|
+
Sync identifier (terminator to above string) $00 (00)
|
|
1183
|
+
Time stamp $xx (xx ...)
|
|
1184
|
+
|
|
1185
|
+
The 'time stamp' is set to zero or the whole sync is omitted if
|
|
1186
|
+
located directly at the beginning of the sound. All time stamps
|
|
1187
|
+
should be sorted in chronological order. The sync can be considered
|
|
1188
|
+
as a validator of the subsequent string.
|
|
1189
|
+
|
|
1190
|
+
Newline ($0A) characters are allowed in all "SYLT" frames and should
|
|
1191
|
+
be used after every entry (name, event etc.) in a frame with the
|
|
1192
|
+
content type $03 - $04.
|
|
1193
|
+
|
|
1194
|
+
A few considerations regarding whitespace characters: Whitespace
|
|
1195
|
+
separating words should mark the beginning of a new word, thus
|
|
1196
|
+
occurring in front of the first syllable of a new word. This is also
|
|
1197
|
+
valid for new line characters. A syllable followed by a comma should
|
|
1198
|
+
not be broken apart with a sync (both the syllable and the comma
|
|
1199
|
+
should be before the sync).
|
|
1200
|
+
|
|
1201
|
+
An example: The "USLT" passage
|
|
1202
|
+
|
|
1203
|
+
"Strangers in the night" $0A "Exchanging glances"
|
|
1204
|
+
|
|
1205
|
+
would be "SYLT" encoded as:
|
|
1206
|
+
|
|
1207
|
+
"Strang" $00 xx xx "ers" $00 xx xx " in" $00 xx xx " the" $00 xx xx
|
|
1208
|
+
" night" $00 xx xx 0A "Ex" $00 xx xx "chang" $00 xx xx "ing" $00 xx
|
|
1209
|
+
xx "glan" $00 xx xx "ces" $00 xx xx
|
|
1210
|
+
|
|
1211
|
+
There may be more than one "SYLT" frame in each tag, but only one
|
|
1212
|
+
with the same language and content descriptor.
|
|
1213
|
+
|
|
1214
|
+
<A NAME=COMM>
|
|
1215
|
+
4.11. Comments</A>
|
|
1216
|
+
|
|
1217
|
+
This frame is indended for any kind of full text information that
|
|
1218
|
+
does not fit in any other frame. It consists of a frame header
|
|
1219
|
+
followed by encoding, language and content descriptors and is ended
|
|
1220
|
+
with the actual comment as a text string. Newline characters are
|
|
1221
|
+
allowed in the comment text string. There may be more than one
|
|
1222
|
+
comment frame in each tag, but only one with the same language and
|
|
1223
|
+
content descriptor.
|
|
1224
|
+
|
|
1225
|
+
<Header for 'Comment', ID: "COMM">
|
|
1226
|
+
Text encoding $xx
|
|
1227
|
+
Language $xx xx xx
|
|
1228
|
+
Short content descrip. <text string according to encoding> $00 (00)
|
|
1229
|
+
The actual text <full text string according to encoding>
|
|
1230
|
+
|
|
1231
|
+
<A NAME=RVAD>
|
|
1232
|
+
4.12. Relative volume adjustment</A>
|
|
1233
|
+
|
|
1234
|
+
This is a more subjective function than the previous ones. It allows
|
|
1235
|
+
the user to say how much he wants to increase/decrease the volume on
|
|
1236
|
+
each channel while the file is played. The purpose is to be able to
|
|
1237
|
+
align all files to a reference volume, so that you don't have to
|
|
1238
|
+
change the volume constantly. This frame may also be used to balance
|
|
1239
|
+
adjust the audio. If the volume peak levels are known then this could
|
|
1240
|
+
be described with the 'Peak volume right' and 'Peak volume left'
|
|
1241
|
+
field. If Peakvolume is not known these fields could be left zeroed
|
|
1242
|
+
or, if no other data follows, be completely omitted. There may only
|
|
1243
|
+
be one "RVAD" frame in each tag.
|
|
1244
|
+
|
|
1245
|
+
<Header for 'Relative volume adjustment', ID: "RVAD">
|
|
1246
|
+
Increment/decrement %00xxxxxx
|
|
1247
|
+
Bits used for volume descr. $xx
|
|
1248
|
+
Relative volume change, right $xx xx (xx ...)
|
|
1249
|
+
Relative volume change, left $xx xx (xx ...)
|
|
1250
|
+
Peak volume right $xx xx (xx ...)
|
|
1251
|
+
Peak volume left $xx xx (xx ...)
|
|
1252
|
+
|
|
1253
|
+
In the increment/decrement field bit 0 is used to indicate the right
|
|
1254
|
+
channel and bit 1 is used to indicate the left channel. 1 is
|
|
1255
|
+
increment and 0 is decrement.
|
|
1256
|
+
|
|
1257
|
+
The 'bits used for volume description' field is normally $10 (16
|
|
1258
|
+
bits) for MPEG 2 layer I, II and III [MPEG] and MPEG 2.5. This value
|
|
1259
|
+
may not be $00. The volume is always represented with whole bytes,
|
|
1260
|
+
padded in the beginning (highest bits) when 'bits used for volume
|
|
1261
|
+
description' is not a multiple of eight.
|
|
1262
|
+
|
|
1263
|
+
This datablock is then optionally followed by a volume definition for
|
|
1264
|
+
the left and right back channels. If this information is appended to
|
|
1265
|
+
the frame the first two channels will be treated as front channels.
|
|
1266
|
+
In the increment/decrement field bit 2 is used to indicate the right
|
|
1267
|
+
back channel and bit 3 for the left back channel.
|
|
1268
|
+
|
|
1269
|
+
Relative volume change, right back $xx xx (xx ...)
|
|
1270
|
+
Relative volume change, left back $xx xx (xx ...)
|
|
1271
|
+
Peak volume right back $xx xx (xx ...)
|
|
1272
|
+
Peak volume left back $xx xx (xx ...)
|
|
1273
|
+
|
|
1274
|
+
If the center channel adjustment is present the following is appended
|
|
1275
|
+
to the existing frame, after the left and right back channels. The
|
|
1276
|
+
center channel is represented by bit 4 in the increase/decrease
|
|
1277
|
+
field.
|
|
1278
|
+
|
|
1279
|
+
Relative volume change, center $xx xx (xx ...)
|
|
1280
|
+
Peak volume center $xx xx (xx ...)
|
|
1281
|
+
|
|
1282
|
+
If the bass channel adjustment is present the following is appended
|
|
1283
|
+
to the existing frame, after the center channel. The bass channel is
|
|
1284
|
+
represented by bit 5 in the increase/decrease field.
|
|
1285
|
+
|
|
1286
|
+
Relative volume change, bass $xx xx (xx ...)
|
|
1287
|
+
Peak volume bass $xx xx (xx ...)
|
|
1288
|
+
|
|
1289
|
+
<A NAME=EQUA>
|
|
1290
|
+
4.13. Equalisation</A>
|
|
1291
|
+
|
|
1292
|
+
This is another subjective, alignment frame. It allows the user to
|
|
1293
|
+
predefine an equalisation curve within the audio file. There may only
|
|
1294
|
+
be one "EQUA" frame in each tag.
|
|
1295
|
+
|
|
1296
|
+
<Header of 'Equalisation', ID: "EQUA">
|
|
1297
|
+
Adjustment bits $xx
|
|
1298
|
+
|
|
1299
|
+
The 'adjustment bits' field defines the number of bits used for
|
|
1300
|
+
representation of the adjustment. This is normally $10 (16 bits) for
|
|
1301
|
+
MPEG 2 layer I, II and III [MPEG] and MPEG 2.5. This value may not be
|
|
1302
|
+
$00.
|
|
1303
|
+
|
|
1304
|
+
This is followed by 2 bytes + ('adjustment bits' rounded up to the
|
|
1305
|
+
nearest byte) for every equalisation band in the following format,
|
|
1306
|
+
giving a frequency range of 0 - 32767Hz:
|
|
1307
|
+
|
|
1308
|
+
Increment/decrement %x (MSB of the Frequency)
|
|
1309
|
+
Frequency (lower 15 bits)
|
|
1310
|
+
Adjustment $xx (xx ...)
|
|
1311
|
+
|
|
1312
|
+
The increment/decrement bit is 1 for increment and 0 for decrement.
|
|
1313
|
+
The equalisation bands should be ordered increasingly with reference
|
|
1314
|
+
to frequency. All frequencies don't have to be declared. The
|
|
1315
|
+
equalisation curve in the reading software should be interpolated
|
|
1316
|
+
between the values in this frame. Three equal adjustments for three
|
|
1317
|
+
subsequent frequencies. A frequency should only be described once in
|
|
1318
|
+
the frame.
|
|
1319
|
+
|
|
1320
|
+
<A NAME=RVRB>
|
|
1321
|
+
4.14. Reverb</A>
|
|
1322
|
+
|
|
1323
|
+
Yet another subjective one. You may here adjust echoes of different
|
|
1324
|
+
kinds. Reverb left/right is the delay between every bounce in ms.
|
|
1325
|
+
Reverb bounces left/right is the number of bounces that should be
|
|
1326
|
+
made. $FF equals an infinite number of bounces. Feedback is the
|
|
1327
|
+
amount of volume that should be returned to the next echo bounce. $00
|
|
1328
|
+
is 0%, $FF is 100%. If this value were $7F, there would be 50% volume
|
|
1329
|
+
reduction on the first bounce, 50% of that on the second and so on.
|
|
1330
|
+
Left to left means the sound from the left bounce to be played in the
|
|
1331
|
+
left speaker, while left to right means sound from the left bounce to
|
|
1332
|
+
be played in the right speaker.
|
|
1333
|
+
|
|
1334
|
+
'Premix left to right' is the amount of left sound to be mixed in the
|
|
1335
|
+
right before any reverb is applied, where $00 id 0% and $FF is 100%.
|
|
1336
|
+
'Premix right to left' does the same thing, but right to left.
|
|
1337
|
+
Setting both premix to $FF would result in a mono output (if the
|
|
1338
|
+
reverb is applied symmetric). There may only be one "RVRB" frame in
|
|
1339
|
+
each tag.
|
|
1340
|
+
|
|
1341
|
+
<Header for 'Reverb', ID: "RVRB">
|
|
1342
|
+
Reverb left (ms) $xx xx
|
|
1343
|
+
Reverb right (ms) $xx xx
|
|
1344
|
+
Reverb bounces, left $xx
|
|
1345
|
+
Reverb bounces, right $xx
|
|
1346
|
+
Reverb feedback, left to left $xx
|
|
1347
|
+
Reverb feedback, left to right $xx
|
|
1348
|
+
Reverb feedback, right to right $xx
|
|
1349
|
+
Reverb feedback, right to left $xx
|
|
1350
|
+
Premix left to right $xx
|
|
1351
|
+
Premix right to left $xx
|
|
1352
|
+
|
|
1353
|
+
<A NAME=APIC>
|
|
1354
|
+
4.15. Attached picture</A>
|
|
1355
|
+
|
|
1356
|
+
This frame contains a picture directly related to the audio file.
|
|
1357
|
+
Image format is the MIME type and subtype [MIME] for the image. In
|
|
1358
|
+
the event that the MIME media type name is omitted, "image/" will be
|
|
1359
|
+
implied. The "image/png" [PNG] or "image/jpeg" [JFIF] picture format
|
|
1360
|
+
should be used when interoperability is wanted. Description is a
|
|
1361
|
+
short description of the picture, represented as a terminated
|
|
1362
|
+
textstring. The description has a maximum length of 64 characters,
|
|
1363
|
+
but may be empty. There may be several pictures attached to one file,
|
|
1364
|
+
each in their individual "APIC" frame, but only one with the same
|
|
1365
|
+
content descriptor. There may only be one picture with the picture
|
|
1366
|
+
type declared as picture type $01 and $02 respectively. There is the
|
|
1367
|
+
possibility to put only a link to the image file by using the 'MIME
|
|
1368
|
+
type' "-->" and having a complete URL [URL] instead of picture data.
|
|
1369
|
+
The use of linked files should however be used sparingly since there
|
|
1370
|
+
is the risk of separation of files.
|
|
1371
|
+
|
|
1372
|
+
<Header for 'Attached picture', ID: "APIC">
|
|
1373
|
+
Text encoding $xx
|
|
1374
|
+
MIME type <text string> $00
|
|
1375
|
+
Picture type $xx
|
|
1376
|
+
Description <text string according to encoding> $00 (00)
|
|
1377
|
+
Picture data <binary data>
|
|
1378
|
+
|
|
1379
|
+
|
|
1380
|
+
Picture type: $00 Other
|
|
1381
|
+
$01 32x32 pixels 'file icon' (PNG only)
|
|
1382
|
+
$02 Other file icon
|
|
1383
|
+
$03 Cover (front)
|
|
1384
|
+
$04 Cover (back)
|
|
1385
|
+
$05 Leaflet page
|
|
1386
|
+
$06 Media (e.g. lable side of CD)
|
|
1387
|
+
$07 Lead artist/lead performer/soloist
|
|
1388
|
+
$08 Artist/performer
|
|
1389
|
+
$09 Conductor
|
|
1390
|
+
$0A Band/Orchestra
|
|
1391
|
+
$0B Composer
|
|
1392
|
+
$0C Lyricist/text writer
|
|
1393
|
+
$0D Recording Location
|
|
1394
|
+
$0E During recording
|
|
1395
|
+
$0F During performance
|
|
1396
|
+
$10 Movie/video screen capture
|
|
1397
|
+
$11 A bright coloured fish
|
|
1398
|
+
$12 Illustration
|
|
1399
|
+
$13 Band/artist logotype
|
|
1400
|
+
$14 Publisher/Studio logotype
|
|
1401
|
+
|
|
1402
|
+
<A NAME=GEOB>
|
|
1403
|
+
4.16. General encapsulated object</A>
|
|
1404
|
+
|
|
1405
|
+
In this frame any type of file can be encapsulated. After the header,
|
|
1406
|
+
'Frame size' and 'Encoding' follows 'MIME type' [MIME] represented as
|
|
1407
|
+
as a terminated string encoded with ISO 8859-1 [ISO-8859-1]. The
|
|
1408
|
+
filename is case sensitive and is encoded as 'Encoding'. Then follows
|
|
1409
|
+
a content description as terminated string, encoded as 'Encoding'.
|
|
1410
|
+
The last thing in the frame is the actual object. The first two
|
|
1411
|
+
strings may be omitted, leaving only their terminations. MIME type is
|
|
1412
|
+
always an ISO-8859-1 text string. There may be more than one "GEOB"
|
|
1413
|
+
frame in each tag, but only one with the same content descriptor.
|
|
1414
|
+
|
|
1415
|
+
<Header for 'General encapsulated object', ID: "GEOB">
|
|
1416
|
+
Text encoding $xx
|
|
1417
|
+
MIME type <text string> $00
|
|
1418
|
+
Filename <text string according to encoding> $00 (00)
|
|
1419
|
+
Content description <text string according to enc�ding> $00 (00)
|
|
1420
|
+
Encapsulated object <binary data>
|
|
1421
|
+
|
|
1422
|
+
<A NAME=PCNT>
|
|
1423
|
+
4.17. Play counter</A>
|
|
1424
|
+
|
|
1425
|
+
This is simply a counter of the number of times a file has been
|
|
1426
|
+
played. The value is increased by one every time the file begins to
|
|
1427
|
+
play. There may only be one "PCNT" frame in each tag. When the
|
|
1428
|
+
counter reaches all one's, one byte is inserted in front of the
|
|
1429
|
+
counter thus making the counter eight bits bigger. The counter must
|
|
1430
|
+
be at least 32-bits long to begin with.
|
|
1431
|
+
|
|
1432
|
+
<Header for 'Play counter', ID: "PCNT">
|
|
1433
|
+
Counter $xx xx xx xx (xx ...)
|
|
1434
|
+
|
|
1435
|
+
<A NAME=POPM>
|
|
1436
|
+
4.18. Popularimeter</A>
|
|
1437
|
+
|
|
1438
|
+
The purpose of this frame is to specify how good an audio file is.
|
|
1439
|
+
Many interesting applications could be found to this frame such as a
|
|
1440
|
+
playlist that features better audiofiles more often than others or it
|
|
1441
|
+
could be used to profile a person's taste and find other 'good' files
|
|
1442
|
+
by comparing people's profiles. The frame is very simple. It contains
|
|
1443
|
+
the email address to the user, one rating byte and a four byte play
|
|
1444
|
+
counter, intended to be increased with one for every time the file is
|
|
1445
|
+
played. The email is a terminated string. The rating is 1-255 where
|
|
1446
|
+
1 is worst and 255 is best. 0 is unknown. If no personal counter is
|
|
1447
|
+
wanted it may be omitted. When the counter reaches all one's, one
|
|
1448
|
+
byte is inserted in front of the counter thus making the counter
|
|
1449
|
+
eight bits bigger in the same away as the play counter ("PCNT").
|
|
1450
|
+
There may be more than one "POPM" frame in each tag, but only one
|
|
1451
|
+
with the same email address.
|
|
1452
|
+
|
|
1453
|
+
<Header for 'Popularimeter', ID: "POPM">
|
|
1454
|
+
Email to user <text string> $00
|
|
1455
|
+
Rating $xx
|
|
1456
|
+
Counter $xx xx xx xx (xx ...)
|
|
1457
|
+
|
|
1458
|
+
<A NAME=RBUF>
|
|
1459
|
+
4.19. Recommended buffer size</A>
|
|
1460
|
+
|
|
1461
|
+
Sometimes the server from which a audio file is streamed is aware of
|
|
1462
|
+
transmission or coding problems resulting in interruptions in the
|
|
1463
|
+
audio stream. In these cases, the size of the buffer can be
|
|
1464
|
+
recommended by the server using this frame. If the 'embedded info
|
|
1465
|
+
flag' is true (1) then this indicates that an ID3 tag with the
|
|
1466
|
+
maximum size described in 'Buffer size' may occur in the audiostream.
|
|
1467
|
+
In such case the tag should reside between two MPEG [MPEG] frames, if
|
|
1468
|
+
the audio is MPEG encoded. If the position of the next tag is known,
|
|
1469
|
+
'offset to next tag' may be used. The offset is calculated from the
|
|
1470
|
+
end of tag in which this frame resides to the first byte of the
|
|
1471
|
+
header in the next. This field may be omitted. Embedded tags are
|
|
1472
|
+
generally not recommended since this could render unpredictable
|
|
1473
|
+
behaviour from present software/hardware.
|
|
1474
|
+
|
|
1475
|
+
For applications like streaming audio it might be an idea to embed
|
|
1476
|
+
tags into the audio stream though. If the clients connects to
|
|
1477
|
+
individual connections like HTTP and there is a possibility to begin
|
|
1478
|
+
every transmission with a tag, then this tag should include a
|
|
1479
|
+
'recommended buffer size' frame. If the client is connected to a
|
|
1480
|
+
arbitrary point in the stream, such as radio or multicast, then the
|
|
1481
|
+
'recommended buffer size' frame should be included in every tag.
|
|
1482
|
+
Every tag that is picked up after the initial/first tag is to be
|
|
1483
|
+
considered as an update of the previous one. E.g. if there is a
|
|
1484
|
+
"TIT2" frame in the first received tag and one in the second tag,
|
|
1485
|
+
then the first should be 'replaced' with the second.
|
|
1486
|
+
|
|
1487
|
+
The 'Buffer size' should be kept to a minimum. There may only be one
|
|
1488
|
+
"RBUF" frame in each tag.
|
|
1489
|
+
|
|
1490
|
+
<Header for 'Recommended buffer size', ID: "RBUF">
|
|
1491
|
+
Buffer size $xx xx xx
|
|
1492
|
+
Embedded info flag %0000000x
|
|
1493
|
+
Offset to next tag $xx xx xx xx
|
|
1494
|
+
|
|
1495
|
+
<A NAME=AENC>
|
|
1496
|
+
4.20. Audio encryption</A>
|
|
1497
|
+
|
|
1498
|
+
This frame indicates if the actual audio stream is encrypted, and by
|
|
1499
|
+
whom. Since standardisation of such encrypion scheme is beyond this
|
|
1500
|
+
document, all "AENC" frames begin with a terminated string with a
|
|
1501
|
+
URL containing an email address, or a link to a location where an
|
|
1502
|
+
email address can be found, that belongs to the organisation
|
|
1503
|
+
responsible for this specific encrypted audio file. Questions
|
|
1504
|
+
regarding the encrypted audio should be sent to the email address
|
|
1505
|
+
specified. If a $00 is found directly after the 'Frame size' and the
|
|
1506
|
+
audiofile indeed is encrypted, the whole file may be considered
|
|
1507
|
+
useless.
|
|
1508
|
+
|
|
1509
|
+
After the 'Owner identifier', a pointer to an unencrypted part of the
|
|
1510
|
+
audio can be specified. The 'Preview start' and 'Preview length' is
|
|
1511
|
+
described in frames. If no part is unencrypted, these fields should
|
|
1512
|
+
be left zeroed. After the 'preview length' field follows optionally a
|
|
1513
|
+
datablock required for decryption of the audio. There may be more
|
|
1514
|
+
than one "AENC" frames in a tag, but only one with the same 'Owner
|
|
1515
|
+
identifier'.
|
|
1516
|
+
|
|
1517
|
+
<Header for 'Audio encryption', ID: "AENC">
|
|
1518
|
+
Owner identifier <text string> $00
|
|
1519
|
+
Preview start $xx xx
|
|
1520
|
+
Preview length $xx xx
|
|
1521
|
+
Encryption info <binary data>
|
|
1522
|
+
|
|
1523
|
+
<A NAME=LINK>
|
|
1524
|
+
4.21. Linked information</A>
|
|
1525
|
+
|
|
1526
|
+
To keep space waste as low as possible this frame may be used to link
|
|
1527
|
+
information from another ID3v2 tag that might reside in another audio
|
|
1528
|
+
file or alone in a binary file. It is recommended that this method is
|
|
1529
|
+
only used when the files are stored on a CD-ROM or other
|
|
1530
|
+
circumstances when the risk of file seperation is low. The frame
|
|
1531
|
+
contains a frame identifier, which is the frame that should be linked
|
|
1532
|
+
into this tag, a URL [URL] field, where a reference to the file where
|
|
1533
|
+
the frame is given, and additional ID data, if needed. Data should be
|
|
1534
|
+
retrieved from the first tag found in the file to which this link
|
|
1535
|
+
points. There may be more than one "LINK" frame in a tag, but only
|
|
1536
|
+
one with the same contents. A linked frame is to be considered as
|
|
1537
|
+
part of the tag and has the same restrictions as if it was a physical
|
|
1538
|
+
part of the tag (i.e. only one "RVRB" frame allowed, whether it's
|
|
1539
|
+
linked or not).
|
|
1540
|
+
|
|
1541
|
+
<Header for 'Linked information', ID: "LINK">
|
|
1542
|
+
Frame identifier $xx xx xx
|
|
1543
|
+
URL <text string> $00
|
|
1544
|
+
ID and additional data <text string(s)>
|
|
1545
|
+
|
|
1546
|
+
Frames that may be linked and need no additional data are "IPLS",
|
|
1547
|
+
"MCID", "ETCO", "MLLT", "SYTC", "RVAD", "EQUA", "RVRB", "RBUF", the
|
|
1548
|
+
text information frames and the URL link frames.
|
|
1549
|
+
|
|
1550
|
+
The "TXXX", "APIC", "GEOB" and "AENC" frames may be linked with
|
|
1551
|
+
the content descriptor as additional ID data.
|
|
1552
|
+
|
|
1553
|
+
The "COMM", "SYLT" and "USLT" frames may be linked with three bytes
|
|
1554
|
+
of language descriptor directly followed by a content descriptor as
|
|
1555
|
+
additional ID data.
|
|
1556
|
+
|
|
1557
|
+
<A NAME=POSS>
|
|
1558
|
+
4.22. Position synchronisation frame</A>
|
|
1559
|
+
|
|
1560
|
+
This frame delivers information to the listener of how far into the
|
|
1561
|
+
audio stream he picked up; in effect, it states the time offset of
|
|
1562
|
+
the first frame in the stream. The frame layout is:
|
|
1563
|
+
|
|
1564
|
+
<Head for 'Position synchronisation', ID: "POSS">
|
|
1565
|
+
Time stamp format $xx
|
|
1566
|
+
Position $xx (xx ...)
|
|
1567
|
+
|
|
1568
|
+
Where time stamp format is:
|
|
1569
|
+
|
|
1570
|
+
$01 Absolute time, 32 bit sized, using MPEG frames as unit
|
|
1571
|
+
$02 Absolute time, 32 bit sized, using milliseconds as unit
|
|
1572
|
+
|
|
1573
|
+
and position is where in the audio the listener starts to receive,
|
|
1574
|
+
i.e. the beginning of the next frame. If this frame is used in the
|
|
1575
|
+
beginning of a file the value is always 0. There may only be one
|
|
1576
|
+
"POSS" frame in each tag.
|
|
1577
|
+
|
|
1578
|
+
<A NAME=USER>
|
|
1579
|
+
4.23. Terms of use frame</A>
|
|
1580
|
+
|
|
1581
|
+
This frame contains a brief description of the terms of use and
|
|
1582
|
+
ownership of the file. More detailed information concerning the legal
|
|
1583
|
+
terms might be available through the "WCOP" frame. Newlines are
|
|
1584
|
+
allowed in the text. There may only be one "USER" frame in a tag.
|
|
1585
|
+
|
|
1586
|
+
<Header for 'Terms of use frame', ID: "USER">
|
|
1587
|
+
Text encoding $xx
|
|
1588
|
+
Language $xx xx xx
|
|
1589
|
+
The actual text <text string according to encoding>
|
|
1590
|
+
|
|
1591
|
+
<A NAME=OWNE>
|
|
1592
|
+
4.24. Ownership frame</A>
|
|
1593
|
+
|
|
1594
|
+
The ownership frame might be used as a reminder of a made transaction
|
|
1595
|
+
or, if signed, as proof. Note that the "USER" and "TOWN" frames are
|
|
1596
|
+
good to use in conjunction with this one. The frame begins, after the
|
|
1597
|
+
frame ID, size and encoding fields, with a 'price payed' field. The
|
|
1598
|
+
first three characters of this field contains the currency used for
|
|
1599
|
+
the transaction, encoded according to ISO 4217 [ISO-4217] alphabetic
|
|
1600
|
+
currency code. Concatenated to this is the actual price payed, as a
|
|
1601
|
+
numerical string using "." as the decimal separator. Next is an 8
|
|
1602
|
+
character date string (YYYYMMDD) followed by a string with the name
|
|
1603
|
+
of the seller as the last field in the frame. There may only be one
|
|
1604
|
+
"OWNE" frame in a tag.
|
|
1605
|
+
|
|
1606
|
+
<Header for 'Ownership frame', ID: "OWNE">
|
|
1607
|
+
Text encoding $xx
|
|
1608
|
+
Price payed <text string> $00
|
|
1609
|
+
Date of purch. <text string>
|
|
1610
|
+
Seller <text string according to encoding>
|
|
1611
|
+
|
|
1612
|
+
<A NAME=COMR>
|
|
1613
|
+
4.25. Commercial frame</A>
|
|
1614
|
+
|
|
1615
|
+
This frame enables several competing offers in the same tag by
|
|
1616
|
+
bundling all needed information. That makes this frame rather complex
|
|
1617
|
+
but it's an easier solution than if one tries to achieve the same
|
|
1618
|
+
result with several frames. The frame begins, after the frame ID,
|
|
1619
|
+
size and encoding fields, with a price string field. A price is
|
|
1620
|
+
constructed by one three character currency code, encoded according
|
|
1621
|
+
to ISO 4217 [ISO-4217] alphabetic currency code, followed by a
|
|
1622
|
+
numerical value where "." is used as decimal seperator. In the price
|
|
1623
|
+
string several prices may be concatenated, seperated by a "/"
|
|
1624
|
+
character, but there may only be one currency of each type.
|
|
1625
|
+
|
|
1626
|
+
The price string is followed by an 8 character date string in the
|
|
1627
|
+
format YYYYMMDD, describing for how long the price is valid. After
|
|
1628
|
+
that is a contact URL, with which the user can contact the seller,
|
|
1629
|
+
followed by a one byte 'received as' field. It describes how the
|
|
1630
|
+
audio is delivered when bought according to the following list:
|
|
1631
|
+
|
|
1632
|
+
$00 Other
|
|
1633
|
+
$01 Standard CD album with other songs
|
|
1634
|
+
$02 Compressed audio on CD
|
|
1635
|
+
$03 File over the Internet
|
|
1636
|
+
$04 Stream over the Internet
|
|
1637
|
+
$05 As note sheets
|
|
1638
|
+
$06 As note sheets in a book with other sheets
|
|
1639
|
+
$07 Music on other media
|
|
1640
|
+
$08 Non-musical merchandise
|
|
1641
|
+
|
|
1642
|
+
Next follows a terminated string with the name of the seller followed
|
|
1643
|
+
by a terminated string with a short description of the product. The
|
|
1644
|
+
last thing is the ability to include a company logotype. The first of
|
|
1645
|
+
them is the 'Picture MIME type' field containing information about
|
|
1646
|
+
which picture format is used. In the event that the MIME media type
|
|
1647
|
+
name is omitted, "image/" will be implied. Currently only "image/png"
|
|
1648
|
+
and "image/jpeg" are allowed. This format string is followed by the
|
|
1649
|
+
binary picture data. This two last fields may be omitted if no
|
|
1650
|
+
picture is to attach.
|
|
1651
|
+
|
|
1652
|
+
<Header for 'Commercial frame', ID: "COMR">
|
|
1653
|
+
Text encoding $xx
|
|
1654
|
+
Price string <text string> $00
|
|
1655
|
+
Valid until <text string>
|
|
1656
|
+
Contact URL <text string> $00
|
|
1657
|
+
Received as $xx
|
|
1658
|
+
Name of seller <text string according to encoding> $00 (00)
|
|
1659
|
+
Description <text string according to encoding> $00 (00)
|
|
1660
|
+
Picture MIME type <string> $00
|
|
1661
|
+
Seller logo <binary data>
|
|
1662
|
+
|
|
1663
|
+
<A NAME=ENCR>
|
|
1664
|
+
4.26. Encryption method registration</A>
|
|
1665
|
+
|
|
1666
|
+
To identify with which method a frame has been encrypted the
|
|
1667
|
+
encryption method must be registered in the tag with this frame. The
|
|
1668
|
+
'Owner identifier' is a null-terminated string with a URL [URL]
|
|
1669
|
+
containing an email address, or a link to a location where an email
|
|
1670
|
+
address can be found, that belongs to the organisation responsible
|
|
1671
|
+
for this specific encryption method. Questions regarding the
|
|
1672
|
+
encryption method should be sent to the indicated email address. The
|
|
1673
|
+
'Method symbol' contains a value that is associated with this method
|
|
1674
|
+
throughout the whole tag. Values below $80 are reserved. The 'Method
|
|
1675
|
+
symbol' may optionally be followed by encryption specific data. There
|
|
1676
|
+
may be several "ENCR" frames in a tag but only one containing the
|
|
1677
|
+
same symbol and only one containing the same owner identifier. The
|
|
1678
|
+
method must be used somewhere in the tag. See section 3.3.1, flag j
|
|
1679
|
+
for more information.
|
|
1680
|
+
|
|
1681
|
+
<Header for 'Encryption method registration', ID: "ENCR">
|
|
1682
|
+
Owner identifier <text string> $00
|
|
1683
|
+
Method symbol $xx
|
|
1684
|
+
Encryption data <binary data>
|
|
1685
|
+
|
|
1686
|
+
<A NAME=GRID>
|
|
1687
|
+
4.27. Group identification registration</A>
|
|
1688
|
+
|
|
1689
|
+
This frame enables grouping of otherwise unrelated frames. This can
|
|
1690
|
+
be used when some frames are to be signed. To identify which frames
|
|
1691
|
+
belongs to a set of frames a group identifier must be registered in
|
|
1692
|
+
the tag with this frame. The 'Owner identifier' is a null-terminated
|
|
1693
|
+
string with a URL [URL] containing an email address, or a link to a
|
|
1694
|
+
location where an email address can be found, that belongs to the
|
|
1695
|
+
organisation responsible for this grouping. Questions regarding the
|
|
1696
|
+
grouping should be sent to the indicated email address. The 'Group
|
|
1697
|
+
symbol' contains a value that associates the frame with this group
|
|
1698
|
+
throughout the whole tag. Values below $80 are reserved. The 'Group
|
|
1699
|
+
symbol' may optionally be followed by some group specific data, e.g.
|
|
1700
|
+
a digital signature. There may be several "GRID" frames in a tag but
|
|
1701
|
+
only one containing the same symbol and only one containing the same
|
|
1702
|
+
owner identifier. The group symbol must be used somewhere in the tag.
|
|
1703
|
+
See section 3.3.1, flag j for more information.
|
|
1704
|
+
|
|
1705
|
+
<Header for 'Group ID registration', ID: "GRID">
|
|
1706
|
+
Owner identifier <text string> $00
|
|
1707
|
+
Group symbol $xx
|
|
1708
|
+
Group dependent data <binary data>
|
|
1709
|
+
|
|
1710
|
+
<A NAME=PRIV>
|
|
1711
|
+
4.28. Private frame</A>
|
|
1712
|
+
|
|
1713
|
+
This frame is used to contain information from a software producer
|
|
1714
|
+
that its program uses and does not fit into the other frames. The
|
|
1715
|
+
frame consists of an 'Owner identifier' string and the binary data.
|
|
1716
|
+
The 'Owner identifier' is a null-terminated string with a URL [URL]
|
|
1717
|
+
containing an email address, or a link to a location where an email
|
|
1718
|
+
address can be found, that belongs to the organisation responsible
|
|
1719
|
+
for the frame. Questions regarding the frame should be sent to the
|
|
1720
|
+
indicated email address. The tag may contain more than one "PRIV"
|
|
1721
|
+
frame but only with different contents. It is recommended to keep the
|
|
1722
|
+
number of "PRIV" frames as low as possible.
|
|
1723
|
+
|
|
1724
|
+
<Header for 'Private frame', ID: "PRIV">
|
|
1725
|
+
Owner identifier <text string> $00
|
|
1726
|
+
The private data <binary data>
|
|
1727
|
+
|
|
1728
|
+
<A NAME=unsync>
|
|
1729
|
+
5. The 'unsynchronisation scheme'</A>
|
|
1730
|
+
|
|
1731
|
+
The only purpose of the 'unsynchronisation scheme' is to make the
|
|
1732
|
+
ID3v2 tag as compatible as possible with existing software. There is
|
|
1733
|
+
no use in 'unsynchronising' tags if the file is only to be processed
|
|
1734
|
+
by new software. Unsynchronisation may only be made with MPEG 2 layer
|
|
1735
|
+
I, II and III and MPEG 2.5 files.
|
|
1736
|
+
|
|
1737
|
+
Whenever a false synchronisation is found within the tag, one zeroed
|
|
1738
|
+
byte is inserted after the first false synchronisation byte. The
|
|
1739
|
+
format of a correct sync that should be altered by ID3 encoders is as
|
|
1740
|
+
follows:
|
|
1741
|
+
|
|
1742
|
+
%11111111 111xxxxx
|
|
1743
|
+
|
|
1744
|
+
And should be replaced with:
|
|
1745
|
+
|
|
1746
|
+
%11111111 00000000 111xxxxx
|
|
1747
|
+
|
|
1748
|
+
This has the side effect that all $FF 00 combinations have to be
|
|
1749
|
+
altered, so they won't be affected by the decoding process. Therefore
|
|
1750
|
+
all the $FF 00 combinations have to be replaced with the $FF 00 00
|
|
1751
|
+
combination during the unsynchronisation.
|
|
1752
|
+
|
|
1753
|
+
To indicate usage of the unsynchronisation, the first bit in 'ID3
|
|
1754
|
+
flags' should be set. This bit should only be set if the tag
|
|
1755
|
+
contains a, now corrected, false synchronisation. The bit should
|
|
1756
|
+
only be clear if the tag does not contain any false synchronisations.
|
|
1757
|
+
|
|
1758
|
+
Do bear in mind, that if a compression scheme is used by the encoder,
|
|
1759
|
+
the unsynchronisation scheme should be applied *afterwards*. When
|
|
1760
|
+
decoding a compressed, 'unsynchronised' file, the 'unsynchronisation
|
|
1761
|
+
scheme' should be parsed first, decompression afterwards.
|
|
1762
|
+
|
|
1763
|
+
If the last byte in the tag is $FF, and there is a need to eliminate
|
|
1764
|
+
false synchronisations in the tag, at least one byte of padding
|
|
1765
|
+
should be added.
|
|
1766
|
+
|
|
1767
|
+
|
|
1768
|
+
6. Copyright
|
|
1769
|
+
|
|
1770
|
+
Copyright (C) Martin Nilsson 1998. All Rights Reserved.
|
|
1771
|
+
|
|
1772
|
+
This document and translations of it may be copied and furnished to
|
|
1773
|
+
others, and derivative works that comment on or otherwise explain it
|
|
1774
|
+
or assist in its implementation may be prepared, copied, published
|
|
1775
|
+
and distributed, in whole or in part, without restriction of any
|
|
1776
|
+
kind, provided that a reference to this document is included on all
|
|
1777
|
+
such copies and derivative works. However, this document itself may
|
|
1778
|
+
not be modified in any way and reissued as the original document.
|
|
1779
|
+
|
|
1780
|
+
The limited permissions granted above are perpetual and will not be
|
|
1781
|
+
revoked.
|
|
1782
|
+
|
|
1783
|
+
This document and the information contained herein is provided on an
|
|
1784
|
+
"AS IS" basis and THE AUTHORS DISCLAIMS ALL WARRANTIES, EXPRESS OR
|
|
1785
|
+
IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
|
|
1786
|
+
THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
|
|
1787
|
+
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
|
|
1788
|
+
|
|
1789
|
+
|
|
1790
|
+
7. References
|
|
1791
|
+
|
|
1792
|
+
[CDDB] Compact Disc Data Base
|
|
1793
|
+
|
|
1794
|
+
<url:http://www.cddb.com>
|
|
1795
|
+
|
|
1796
|
+
[ID3v2] Martin Nilsson, "ID3v2 informal standard".
|
|
1797
|
+
|
|
1798
|
+
<url:http://www.id3.org/id3v2-00.txt>
|
|
1799
|
+
|
|
1800
|
+
[ISO-639-2] ISO/FDIS 639-2.
|
|
1801
|
+
Codes for the representation of names of languages, Part 2: Alpha-3
|
|
1802
|
+
code. Technical committee / subcommittee: TC 37 / SC 2
|
|
1803
|
+
|
|
1804
|
+
[ISO-4217] ISO 4217:1995.
|
|
1805
|
+
Codes for the representation of currencies and funds.
|
|
1806
|
+
Technical committee / subcommittee: TC 68
|
|
1807
|
+
|
|
1808
|
+
[ISO-8859-1] ISO/IEC DIS 8859-1.
|
|
1809
|
+
8-bit single-byte coded graphic character sets, Part 1: Latin
|
|
1810
|
+
alphabet No. 1. Technical committee / subcommittee: JTC 1 / SC 2
|
|
1811
|
+
|
|
1812
|
+
[ISRC] ISO 3901:1986
|
|
1813
|
+
International Standard Recording Code (ISRC).
|
|
1814
|
+
Technical committee / subcommittee: TC 46 / SC 9
|
|
1815
|
+
|
|
1816
|
+
[JFIF] JPEG File Interchange Format, version 1.02
|
|
1817
|
+
|
|
1818
|
+
<url:http://www.w3.org/Graphics/JPEG/jfif.txt>
|
|
1819
|
+
|
|
1820
|
+
[MIME] Freed, N. and N. Borenstein, "Multipurpose Internet Mail
|
|
1821
|
+
Extensions (MIME) Part One: Format of Internet Message Bodies",
|
|
1822
|
+
RFC 2045, November 1996.
|
|
1823
|
+
|
|
1824
|
+
<url:ftp://ftp.isi.edu/in-notes/rfc2045.txt>
|
|
1825
|
+
|
|
1826
|
+
[MPEG] ISO/IEC 11172-3:1993.
|
|
1827
|
+
Coding of moving pictures and associated audio for digital storage
|
|
1828
|
+
media at up to about 1,5 Mbit/s, Part 3: Audio.
|
|
1829
|
+
Technical committee / subcommittee: JTC 1 / SC 29
|
|
1830
|
+
and
|
|
1831
|
+
ISO/IEC 13818-3:1995
|
|
1832
|
+
Generic coding of moving pictures and associated audio information,
|
|
1833
|
+
Part 3: Audio.
|
|
1834
|
+
Technical committee / subcommittee: JTC 1 / SC 29
|
|
1835
|
+
and
|
|
1836
|
+
ISO/IEC DIS 13818-3
|
|
1837
|
+
Generic coding of moving pictures and associated audio information,
|
|
1838
|
+
Part 3: Audio (Revision of ISO/IEC 13818-3:1995)
|
|
1839
|
+
|
|
1840
|
+
|
|
1841
|
+
[PNG] Portable Network Graphics, version 1.0
|
|
1842
|
+
|
|
1843
|
+
<url:http://www.w3.org/TR/REC-png-multi.html>
|
|
1844
|
+
|
|
1845
|
+
[UNICODE] ISO/IEC 10646-1:1993.
|
|
1846
|
+
Universal Multiple-Octet Coded Character Set (UCS), Part 1:
|
|
1847
|
+
Architecture and Basic Multilingual Plane.
|
|
1848
|
+
Technical committee / subcommittee: JTC 1 / SC 2
|
|
1849
|
+
|
|
1850
|
+
<url:http://www.unicode.org>
|
|
1851
|
+
|
|
1852
|
+
[URL] T. Berners-Lee, L. Masinter & M. McCahill, "Uniform Resource
|
|
1853
|
+
Locators (URL).", RFC 1738, December 1994.
|
|
1854
|
+
|
|
1855
|
+
<url:ftp://ftp.isi.edu/in-notes/rfc1738.txt>
|
|
1856
|
+
|
|
1857
|
+
[ZLIB] P. Deutsch, Aladdin Enterprises & J-L. Gailly, "ZLIB
|
|
1858
|
+
Compressed
|
|
1859
|
+
Data Format Specification version 3.3", RFC 1950, May 1996.
|
|
1860
|
+
|
|
1861
|
+
<url:ftp://ftp.isi.edu/in-notes/rfc1950.txt>
|
|
1862
|
+
|
|
1863
|
+
|
|
1864
|
+
8. Appendix
|
|
1865
|
+
|
|
1866
|
+
<A NAME=id3v1genreid>
|
|
1867
|
+
A. Appendix A - Genre List from ID3v1</A>
|
|
1868
|
+
|
|
1869
|
+
The following genres is defined in ID3v1
|
|
1870
|
+
|
|
1871
|
+
0.Blues
|
|
1872
|
+
1.Classic Rock
|
|
1873
|
+
2.Country
|
|
1874
|
+
3.Dance
|
|
1875
|
+
4.Disco
|
|
1876
|
+
5.Funk
|
|
1877
|
+
6.Grunge
|
|
1878
|
+
7.Hip-Hop
|
|
1879
|
+
8.Jazz
|
|
1880
|
+
9.Metal
|
|
1881
|
+
10.New Age
|
|
1882
|
+
11.Oldies
|
|
1883
|
+
12.Other
|
|
1884
|
+
13.Pop
|
|
1885
|
+
14.R&B
|
|
1886
|
+
15.Rap
|
|
1887
|
+
16.Reggae
|
|
1888
|
+
17.Rock
|
|
1889
|
+
18.Techno
|
|
1890
|
+
19.Industrial
|
|
1891
|
+
20.Alternative
|
|
1892
|
+
21.Ska
|
|
1893
|
+
22.Death Metal
|
|
1894
|
+
23.Pranks
|
|
1895
|
+
24.Soundtrack
|
|
1896
|
+
25.Euro-Techno
|
|
1897
|
+
26.Ambient
|
|
1898
|
+
27.Trip-Hop
|
|
1899
|
+
28.Vocal
|
|
1900
|
+
29.Jazz+Funk
|
|
1901
|
+
30.Fusion
|
|
1902
|
+
31.Trance
|
|
1903
|
+
32.Classical
|
|
1904
|
+
33.Instrumental
|
|
1905
|
+
34.Acid
|
|
1906
|
+
35.House
|
|
1907
|
+
36.Game
|
|
1908
|
+
37.Sound Clip
|
|
1909
|
+
38.Gospel
|
|
1910
|
+
39.Noise
|
|
1911
|
+
40.AlternRock
|
|
1912
|
+
41.Bass
|
|
1913
|
+
42.Soul
|
|
1914
|
+
43.Punk
|
|
1915
|
+
44.Space
|
|
1916
|
+
45.Meditative
|
|
1917
|
+
46.Instrumental Pop
|
|
1918
|
+
47.Instrumental Rock
|
|
1919
|
+
48.Ethnic
|
|
1920
|
+
49.Gothic
|
|
1921
|
+
50.Darkwave
|
|
1922
|
+
51.Techno-Industrial
|
|
1923
|
+
52.Electronic
|
|
1924
|
+
53.Pop-Folk
|
|
1925
|
+
54.Eurodance
|
|
1926
|
+
55.Dream
|
|
1927
|
+
56.Southern Rock
|
|
1928
|
+
57.Comedy
|
|
1929
|
+
58.Cult
|
|
1930
|
+
59.Gangsta
|
|
1931
|
+
60.Top 40
|
|
1932
|
+
61.Christian Rap
|
|
1933
|
+
62.Pop/Funk
|
|
1934
|
+
63.Jungle
|
|
1935
|
+
64.Native American
|
|
1936
|
+
65.Cabaret
|
|
1937
|
+
66.New Wave
|
|
1938
|
+
67.Psychadelic
|
|
1939
|
+
68.Rave
|
|
1940
|
+
69.Showtunes
|
|
1941
|
+
70.Trailer
|
|
1942
|
+
71.Lo-Fi
|
|
1943
|
+
72.Tribal
|
|
1944
|
+
73.Acid Punk
|
|
1945
|
+
74.Acid Jazz
|
|
1946
|
+
75.Polka
|
|
1947
|
+
76.Retro
|
|
1948
|
+
77.Musical
|
|
1949
|
+
78.Rock & Roll
|
|
1950
|
+
79.Hard Rock
|
|
1951
|
+
|
|
1952
|
+
The following genres are Winamp extensions
|
|
1953
|
+
|
|
1954
|
+
80.Folk
|
|
1955
|
+
81.Folk-Rock
|
|
1956
|
+
82.National Folk
|
|
1957
|
+
83.Swing
|
|
1958
|
+
84.Fast Fusion
|
|
1959
|
+
85.Bebob
|
|
1960
|
+
86.Latin
|
|
1961
|
+
87.Revival
|
|
1962
|
+
88.Celtic
|
|
1963
|
+
89.Bluegrass
|
|
1964
|
+
90.Avantgarde
|
|
1965
|
+
91.Gothic Rock
|
|
1966
|
+
92.Progressive Rock
|
|
1967
|
+
93.Psychedelic Rock
|
|
1968
|
+
94.Symphonic Rock
|
|
1969
|
+
95.Slow Rock
|
|
1970
|
+
96.Big Band
|
|
1971
|
+
97.Chorus
|
|
1972
|
+
98.Easy Listening
|
|
1973
|
+
99.Acoustic
|
|
1974
|
+
100.Humour
|
|
1975
|
+
101.Speech
|
|
1976
|
+
102.Chanson
|
|
1977
|
+
103.Opera
|
|
1978
|
+
104.Chamber Music
|
|
1979
|
+
105.Sonata
|
|
1980
|
+
106.Symphony
|
|
1981
|
+
107.Booty Bass
|
|
1982
|
+
108.Primus
|
|
1983
|
+
109.Porn Groove
|
|
1984
|
+
110.Satire
|
|
1985
|
+
111.Slow Jam
|
|
1986
|
+
112.Club
|
|
1987
|
+
113.Tango
|
|
1988
|
+
114.Samba
|
|
1989
|
+
115.Folklore
|
|
1990
|
+
116.Ballad
|
|
1991
|
+
117.Power Ballad
|
|
1992
|
+
118.Rhythmic Soul
|
|
1993
|
+
119.Freestyle
|
|
1994
|
+
120.Duet
|
|
1995
|
+
121.Punk Rock
|
|
1996
|
+
122.Drum Solo
|
|
1997
|
+
123.Acapella
|
|
1998
|
+
124.Euro-House
|
|
1999
|
+
125.Dance Hall
|
|
2000
|
+
|
|
2001
|
+
|
|
2002
|
+
9. Author's Address
|
|
2003
|
+
|
|
2004
|
+
Written by
|
|
2005
|
+
|
|
2006
|
+
Martin Nilsson
|
|
2007
|
+
Rydsv�gen 246 C. 30
|
|
2008
|
+
S-584 34 Link�ping
|
|
2009
|
+
Sweden
|
|
2010
|
+
|
|
2011
|
+
Email: nilsson@id3.org
|
|
2012
|
+
|
|
2013
|
+
|
|
2014
|
+
Edited by
|
|
2015
|
+
|
|
2016
|
+
Dirk Mahoney
|
|
2017
|
+
57 Pechey Street
|
|
2018
|
+
Chermside Q
|
|
2019
|
+
Australia 4032
|
|
2020
|
+
|
|
2021
|
+
Email: dirk@id3.org
|
|
2022
|
+
|
|
2023
|
+
|
|
2024
|
+
Johan Sundstr�m
|
|
2025
|
+
Als�ttersgatan 5 A. 34
|
|
2026
|
+
S-584 35 Link�ping
|
|
2027
|
+
Sweden
|
|
2028
|
+
|
|
2029
|
+
Email: johan@id3.org
|
|
2030
|
+
|
|
2031
|
+
</PRE>
|
|
2032
|
+
</BODY>
|
|
2033
|
+
</HTML>
|