id3 0.4.0

Sign up to get free protection for your applications and to get access to all the features.
@@ -0,0 +1,1732 @@
1
+ Informal standard M. Nilsson
2
+ Document: id3v2.4.0-frames.txt 1st November 2000
3
+
4
+
5
+ ID3 tag version 2.4.0 - Native Frames
6
+
7
+ Status of this document
8
+
9
+ This document is an informal standard and replaces the ID3v2.3.0
10
+ standard [ID3v2]. A formal standard will use another revision number
11
+ even if the content is identical to document. The contents in this
12
+ document may change for clarifications but never for added or altered
13
+ functionallity.
14
+
15
+ Distribution of this document is unlimited.
16
+
17
+
18
+ Abstract
19
+
20
+ This document describes the frames natively supported by ID3v2.4.0,
21
+ which is a revised version of the ID3v2 informal standard [ID3v2.3.0]
22
+ version 2.3.0. The ID3v2 offers a flexible way of storing audio meta
23
+ information within audio file itself. The information may be
24
+ technical information, such as equalisation curves, as well as title,
25
+ performer, copyright etc.
26
+
27
+ ID3v2.4.0 is meant to be as close as possible to ID3v2.3.0 in order
28
+ to allow for implementations to be revised as easily as possible.
29
+
30
+
31
+ 1. Table of contents
32
+
33
+ 2. Conventions in this document
34
+ 3. Default flags
35
+ 4. Declared ID3v2 frames
36
+ 4.1. Unique file identifier
37
+ 4.2. Text information frames
38
+ 4.2.1. Identification frames
39
+ 4.2.2. Involved persons frames
40
+ 4.2.3. Derived and subjective properties frames
41
+ 4.2.4. Rights and license frames
42
+ 4.2.5. Other text frames
43
+ 4.2.6. User defined text information frame
44
+ 4.3. URL link frames
45
+ 4.3.1. URL link frames - details
46
+ 4.3.2. User defined URL link frame
47
+ 4.4. Music CD Identifier
48
+ 4.5. Event timing codes
49
+ 4.6. MPEG location lookup table
50
+ 4.7. Synced tempo codes
51
+ 4.8. Unsynchronised lyrics/text transcription
52
+ 4.9. Synchronised lyrics/text
53
+ 4.10. Comments
54
+ 4.11. Relative volume adjustment (2)
55
+ 4.12. Equalisation (2)
56
+ 4.13. Reverb
57
+ 4.14. Attached picture
58
+ 4.15. General encapsulated object
59
+ 4.16. Play counter
60
+ 4.17. Popularimeter
61
+ 4.18. Recommended buffer size
62
+ 4.19. Audio encryption
63
+ 4.20. Linked information
64
+ 4.21. Position synchronisation frame
65
+ 4.22. Terms of use
66
+ 4.23. Ownership frame
67
+ 4.24. Commercial frame
68
+ 4.25. Encryption method registration
69
+ 4.26. Group identification registration
70
+ 4.27. Private frame
71
+ 4.28. Signature frame
72
+ 4.29. Seek frame
73
+ 4.30. Audio seek point index
74
+ 5. Copyright
75
+ 6. References
76
+ 7. Appendix
77
+ A. Appendix A - Genre List from ID3v1
78
+ 8. Author's Address
79
+
80
+
81
+ 2. Conventions in this document
82
+
83
+ Text within "" is a text string exactly as it appears in a tag.
84
+ Numbers preceded with $ are hexadecimal and numbers preceded with %
85
+ are binary. $xx is used to indicate a byte with unknown content. %x
86
+ is used to indicate a bit with unknown content. The most significant
87
+ bit (MSB) of a byte is called 'bit 7' and the least significant bit
88
+ (LSB) is called 'bit 0'.
89
+
90
+ A tag is the whole tag described the ID3v2 main structure document
91
+ [ID3v2-strct]. A frame is a block of information in the tag. The tag
92
+ consists of a header, frames and optional padding. A field is a piece
93
+ of information; one value, a string etc. A numeric string is a string
94
+ that consists of the characters "0123456789" only.
95
+
96
+ The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
97
+ "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
98
+ document are to be interpreted as described in RFC 2119 [KEYWORDS].
99
+
100
+
101
+ 3. Default flags
102
+
103
+ The default settings for the frames described in this document can be
104
+ divided into the following classes. The flags may be set differently
105
+ if found more suitable by the software.
106
+
107
+ 1. Discarded if tag is altered, discarded if file is altered.
108
+
109
+ None.
110
+
111
+ 2. Discarded if tag is altered, preserved if file is altered.
112
+
113
+ None.
114
+
115
+ 3. Preserved if tag is altered, discarded if file is altered.
116
+
117
+ ASPI, AENC, ETCO, EQU2, MLLT, POSS, SEEK, SYLT, SYTC, RVA2, TENC,
118
+ TLEN
119
+
120
+ 4. Preserved if tag is altered, preserved if file is altered.
121
+
122
+ The rest of the frames.
123
+
124
+
125
+ 4. Declared ID3v2 frames
126
+
127
+ The following frames are declared in this draft.
128
+
129
+ 4.19 AENC Audio encryption
130
+ 4.14 APIC Attached picture
131
+ 4.30 ASPI Audio seek point index
132
+
133
+ 4.10 COMM Comments
134
+ 4.24 COMR Commercial frame
135
+
136
+ 4.25 ENCR Encryption method registration
137
+ 4.12 EQU2 Equalisation (2)
138
+ 4.5 ETCO Event timing codes
139
+
140
+ 4.15 GEOB General encapsulated object
141
+ 4.26 GRID Group identification registration
142
+
143
+ 4.20 LINK Linked information
144
+
145
+ 4.4 MCDI Music CD identifier
146
+ 4.6 MLLT MPEG location lookup table
147
+
148
+ 4.23 OWNE Ownership frame
149
+
150
+ 4.27 PRIV Private frame
151
+ 4.16 PCNT Play counter
152
+ 4.17 POPM Popularimeter
153
+ 4.21 POSS Position synchronisation frame
154
+
155
+ 4.18 RBUF Recommended buffer size
156
+ 4.11 RVA2 Relative volume adjustment (2)
157
+ 4.13 RVRB Reverb
158
+
159
+ 4.29 SEEK Seek frame
160
+ 4.28 SIGN Signature frame
161
+ 4.9 SYLT Synchronised lyric/text
162
+ 4.7 SYTC Synchronised tempo codes
163
+
164
+ 4.2.1 TALB Album/Movie/Show title
165
+ 4.2.3 TBPM BPM (beats per minute)
166
+ 4.2.2 TCOM Composer
167
+ 4.2.3 TCON Content type
168
+ 4.2.4 TCOP Copyright message
169
+ 4.2.5 TDEN Encoding time
170
+ 4.2.5 TDLY Playlist delay
171
+ 4.2.5 TDOR Original release time
172
+ 4.2.5 TDRC Recording time
173
+ 4.2.5 TDRL Release time
174
+ 4.2.5 TDTG Tagging time
175
+ 4.2.2 TENC Encoded by
176
+ 4.2.2 TEXT Lyricist/Text writer
177
+ 4.2.3 TFLT File type
178
+ 4.2.2 TIPL Involved people list
179
+ 4.2.1 TIT1 Content group description
180
+ 4.2.1 TIT2 Title/songname/content description
181
+ 4.2.1 TIT3 Subtitle/Description refinement
182
+ 4.2.3 TKEY Initial key
183
+ 4.2.3 TLAN Language(s)
184
+ 4.2.3 TLEN Length
185
+ 4.2.2 TMCL Musician credits list
186
+ 4.2.3 TMED Media type
187
+ 4.2.3 TMOO Mood
188
+ 4.2.1 TOAL Original album/movie/show title
189
+ 4.2.5 TOFN Original filename
190
+ 4.2.2 TOLY Original lyricist(s)/text writer(s)
191
+ 4.2.2 TOPE Original artist(s)/performer(s)
192
+ 4.2.4 TOWN File owner/licensee
193
+ 4.2.2 TPE1 Lead performer(s)/Soloist(s)
194
+ 4.2.2 TPE2 Band/orchestra/accompaniment
195
+ 4.2.2 TPE3 Conductor/performer refinement
196
+ 4.2.2 TPE4 Interpreted, remixed, or otherwise modified by
197
+ 4.2.1 TPOS Part of a set
198
+ 4.2.4 TPRO Produced notice
199
+ 4.2.4 TPUB Publisher
200
+ 4.2.1 TRCK Track number/Position in set
201
+ 4.2.4 TRSN Internet radio station name
202
+ 4.2.4 TRSO Internet radio station owner
203
+ 4.2.5 TSOA Album sort order
204
+ 4.2.5 TSOP Performer sort order
205
+ 4.2.5 TSOT Title sort order
206
+ 4.2.1 TSRC ISRC (international standard recording code)
207
+ 4.2.5 TSSE Software/Hardware and settings used for encoding
208
+ 4.2.1 TSST Set subtitle
209
+ 4.2.2 TXXX User defined text information frame
210
+
211
+ 4.1 UFID Unique file identifier
212
+ 4.22 USER Terms of use
213
+ 4.8 USLT Unsynchronised lyric/text transcription
214
+
215
+ 4.3.1 WCOM Commercial information
216
+ 4.3.1 WCOP Copyright/Legal information
217
+ 4.3.1 WOAF Official audio file webpage
218
+ 4.3.1 WOAR Official artist/performer webpage
219
+ 4.3.1 WOAS Official audio source webpage
220
+ 4.3.1 WORS Official Internet radio station homepage
221
+ 4.3.1 WPAY Payment
222
+ 4.3.1 WPUB Publishers official webpage
223
+ 4.3.2 WXXX User defined URL link frame
224
+
225
+
226
+ 4.1. Unique file identifier
227
+
228
+ This frame's purpose is to be able to identify the audio file in a
229
+ database, that may provide more information relevant to the content.
230
+ Since standardisation of such a database is beyond this document, all
231
+ UFID frames begin with an 'owner identifier' field. It is a null-
232
+ terminated string with a URL [URL] containing an email address, or a
233
+ link to a location where an email address can be found, that belongs
234
+ to the organisation responsible for this specific database
235
+ implementation. Questions regarding the database should be sent to
236
+ the indicated email address. The URL should not be used for the
237
+ actual database queries. The string
238
+ "<a href="http://www.id3lib.org/id3/dummy/ufid.html">http://www.id3lib.org/id3/dummy/ufid.html</a>" should be used for tests. The
239
+ 'Owner identifier' must be non-empty (more than just a termination).
240
+ The 'Owner identifier' is then followed by the actual identifier,
241
+ which may be up to 64 bytes. There may be more than one "UFID" frame
242
+ in a tag, but only one with the same 'Owner identifier'.
243
+
244
+ <Header for 'Unique file identifier', ID: "UFID">
245
+ Owner identifier <text string> $00
246
+ Identifier <up to 64 bytes binary data>
247
+
248
+
249
+ 4.2. Text information frames
250
+
251
+ The text information frames are often the most important frames,
252
+ containing information like artist, album and more. There may only be
253
+ one text information frame of its kind in an tag. All text
254
+ information frames supports multiple strings, stored as a null
255
+ separated list, where null is reperesented by the termination code
256
+ for the charater encoding. All text frame identifiers begin with "T".
257
+ Only text frame identifiers begin with "T", with the exception of the
258
+ "TXXX" frame. All the text information frames have the following
259
+ format:
260
+
261
+ <Header for 'Text information frame', ID: "T000" - "TZZZ",
262
+ excluding "TXXX" described in 4.2.6.>
263
+ Text encoding $xx
264
+ Information <text string(s) according to encoding>
265
+
266
+
267
+ 4.2.1. Identification frames
268
+
269
+ TIT1
270
+ The 'Content group description' frame is used if the sound belongs to
271
+ a larger category of sounds/music. For example, classical music is
272
+ often sorted in different musical sections (e.g. "Piano Concerto",
273
+ "Weather - Hurricane").
274
+
275
+ TIT2
276
+ The 'Title/Songname/Content description' frame is the actual name of
277
+ the piece (e.g. "Adagio", "Hurricane Donna").
278
+
279
+ TIT3
280
+ The 'Subtitle/Description refinement' frame is used for information
281
+ directly related to the contents title (e.g. "Op. 16" or "Performed
282
+ live at Wembley").
283
+
284
+ TALB
285
+ The 'Album/Movie/Show title' frame is intended for the title of the
286
+ recording (or source of sound) from which the audio in the file is
287
+ taken.
288
+
289
+ TOAL
290
+ The 'Original album/movie/show title' frame is intended for the title
291
+ of the original recording (or source of sound), if for example the
292
+ music in the file should be a cover of a previously released song.
293
+
294
+ TRCK
295
+ The 'Track number/Position in set' frame is a numeric string
296
+ containing the order number of the audio-file on its original
297
+ recording. This MAY be extended with a "/" character and a numeric
298
+ string containing the total number of tracks/elements on the original
299
+ recording. E.g. "4/9".
300
+
301
+ TPOS
302
+ The 'Part of a set' frame is a numeric string that describes which
303
+ part of a set the audio came from. This frame is used if the source
304
+ described in the "TALB" frame is divided into several mediums, e.g. a
305
+ double CD. The value MAY be extended with a "/" character and a
306
+ numeric string containing the total number of parts in the set. E.g.
307
+ "1/2".
308
+
309
+ TSST
310
+ The 'Set subtitle' frame is intended for the subtitle of the part of
311
+ a set this track belongs to.
312
+
313
+ TSRC
314
+ The 'ISRC' frame should contain the International Standard Recording
315
+ Code [ISRC] (12 characters).
316
+
317
+
318
+ 4.2.2. Involved persons frames
319
+
320
+ TPE1
321
+ The 'Lead artist/Lead performer/Soloist/Performing group' is
322
+ used for the main artist.
323
+
324
+ TPE2
325
+ The 'Band/Orchestra/Accompaniment' frame is used for additional
326
+ information about the performers in the recording.
327
+
328
+ TPE3
329
+ The 'Conductor' frame is used for the name of the conductor.
330
+
331
+ TPE4
332
+ The 'Interpreted, remixed, or otherwise modified by' frame contains
333
+ more information about the people behind a remix and similar
334
+ interpretations of another existing piece.
335
+
336
+ TOPE
337
+ The 'Original artist/performer' frame is intended for the performer
338
+ of the original recording, if for example the music in the file
339
+ should be a cover of a previously released song.
340
+
341
+ TEXT
342
+ The 'Lyricist/Text writer' frame is intended for the writer of the
343
+ text or lyrics in the recording.
344
+
345
+ TOLY
346
+ The 'Original lyricist/text writer' frame is intended for the
347
+ text writer of the original recording, if for example the music in
348
+ the file should be a cover of a previously released song.
349
+
350
+ TCOM
351
+ The 'Composer' frame is intended for the name of the composer.
352
+
353
+ TMCL
354
+ The 'Musician credits list' is intended as a mapping between
355
+ instruments and the musician that played it. Every odd field is an
356
+ instrument and every even is an artist or a comma delimited list of
357
+ artists.
358
+
359
+ TIPL
360
+ The 'Involved people list' is very similar to the musician credits
361
+ list, but maps between functions, like producer, and names.
362
+
363
+ TENC
364
+ The 'Encoded by' frame contains the name of the person or
365
+ organisation that encoded the audio file. This field may contain a
366
+ copyright message, if the audio file also is copyrighted by the
367
+ encoder.
368
+
369
+
370
+ 4.2.3. Derived and subjective properties frames
371
+
372
+ TBPM
373
+ The 'BPM' frame contains the number of beats per minute in the
374
+ main part of the audio. The BPM is an integer and represented as a
375
+ numerical string.
376
+
377
+ TLEN
378
+ The 'Length' frame contains the length of the audio file in
379
+ milliseconds, represented as a numeric string.
380
+
381
+ TKEY
382
+ The 'Initial key' frame contains the musical key in which the sound
383
+ starts. It is represented as a string with a maximum length of three
384
+ characters. The ground keys are represented with "A","B","C","D","E",
385
+ "F" and "G" and halfkeys represented with "b" and "#". Minor is
386
+ represented as "m", e.g. "Dbm" $00. Off key is represented with an
387
+ "o" only.
388
+
389
+ TLAN
390
+ The 'Language' frame should contain the languages of the text or
391
+ lyrics spoken or sung in the audio. The language is represented with
392
+ three characters according to ISO-639-2 [ISO-639-2]. If more than one
393
+ language is used in the text their language codes should follow
394
+ according to the amount of their usage, e.g. "eng" $00 "sve" $00.
395
+
396
+ TCON
397
+ The 'Content type', which ID3v1 was stored as a one byte numeric
398
+ value only, is now a string. You may use one or several of the ID3v1
399
+ types as numerical strings, or, since the category list would be
400
+ impossible to maintain with accurate and up to date categories,
401
+ define your own. Example: "21" $00 "Eurodisco" $00
402
+
403
+ You may also use any of the following keywords:
404
+
405
+ RX Remix
406
+ CR Cover
407
+
408
+ TFLT
409
+ The 'File type' frame indicates which type of audio this tag defines.
410
+ The following types and refinements are defined:
411
+
412
+ MIME MIME type follows
413
+ MPG MPEG Audio
414
+ /1 MPEG 1/2 layer I
415
+ /2 MPEG 1/2 layer II
416
+ /3 MPEG 1/2 layer III
417
+ /2.5 MPEG 2.5
418
+ /AAC Advanced audio compression
419
+ VQF Transform-domain Weighted Interleave Vector Quantisation
420
+ PCM Pulse Code Modulated audio
421
+
422
+ but other types may be used, but not for these types though. This is
423
+ used in a similar way to the predefined types in the "TMED" frame,
424
+ but without parentheses. If this frame is not present audio type is
425
+ assumed to be "MPG".
426
+
427
+ TMED
428
+ The 'Media type' frame describes from which media the sound
429
+ originated. This may be a text string or a reference to the
430
+ predefined media types found in the list below. Example:
431
+ "VID/PAL/VHS" $00.
432
+
433
+ DIG Other digital media
434
+ /A Analogue transfer from media
435
+
436
+ ANA Other analogue media
437
+ /WAC Wax cylinder
438
+ /8CA 8-track tape cassette
439
+
440
+ CD CD
441
+ /A Analogue transfer from media
442
+ /DD DDD
443
+ /AD ADD
444
+ /AA AAD
445
+
446
+ LD Laserdisc
447
+
448
+ TT Turntable records
449
+ /33 33.33 rpm
450
+ /45 45 rpm
451
+ /71 71.29 rpm
452
+ /76 76.59 rpm
453
+ /78 78.26 rpm
454
+ /80 80 rpm
455
+
456
+ MD MiniDisc
457
+ /A Analogue transfer from media
458
+
459
+ DAT DAT
460
+ /A Analogue transfer from media
461
+ /1 standard, 48 kHz/16 bits, linear
462
+ /2 mode 2, 32 kHz/16 bits, linear
463
+ /3 mode 3, 32 kHz/12 bits, non-linear, low speed
464
+ /4 mode 4, 32 kHz/12 bits, 4 channels
465
+ /5 mode 5, 44.1 kHz/16 bits, linear
466
+ /6 mode 6, 44.1 kHz/16 bits, 'wide track' play
467
+
468
+ DCC DCC
469
+ /A Analogue transfer from media
470
+
471
+ DVD DVD
472
+ /A Analogue transfer from media
473
+
474
+ TV Television
475
+ /PAL PAL
476
+ /NTSC NTSC
477
+ /SECAM SECAM
478
+
479
+ VID Video
480
+ /PAL PAL
481
+ /NTSC NTSC
482
+ /SECAM SECAM
483
+ /VHS VHS
484
+ /SVHS S-VHS
485
+ /BETA BETAMAX
486
+
487
+ RAD Radio
488
+ /FM FM
489
+ /AM AM
490
+ /LW LW
491
+ /MW MW
492
+
493
+ TEL Telephone
494
+ /I ISDN
495
+
496
+ MC MC (normal cassette)
497
+ /4 4.75 cm/s (normal speed for a two sided cassette)
498
+ /9 9.5 cm/s
499
+ /I Type I cassette (ferric/normal)
500
+ /II Type II cassette (chrome)
501
+ /III Type III cassette (ferric chrome)
502
+ /IV Type IV cassette (metal)
503
+
504
+ REE Reel
505
+ /9 9.5 cm/s
506
+ /19 19 cm/s
507
+ /38 38 cm/s
508
+ /76 76 cm/s
509
+ /I Type I cassette (ferric/normal)
510
+ /II Type II cassette (chrome)
511
+ /III Type III cassette (ferric chrome)
512
+ /IV Type IV cassette (metal)
513
+
514
+ TMOO
515
+ The 'Mood' frame is intended to reflect the mood of the audio with a
516
+ few keywords, e.g. "Romantic" or "Sad".
517
+
518
+
519
+ 4.2.4. Rights and license frames
520
+
521
+ TCOP
522
+ The 'Copyright message' frame, in which the string must begin with a
523
+ year and a space character (making five characters), is intended for
524
+ the copyright holder of the original sound, not the audio file
525
+ itself. The absence of this frame means only that the copyright
526
+ information is unavailable or has been removed, and must not be
527
+ interpreted to mean that the audio is public domain. Every time this
528
+ field is displayed the field must be preceded with "Copyright " (C) "
529
+ ", where (C) is one character showing a C in a circle.
530
+
531
+ TPRO
532
+ The 'Produced notice' frame, in which the string must begin with a
533
+ year and a space character (making five characters), is intended for
534
+ the production copyright holder of the original sound, not the audio
535
+ file itself. The absence of this frame means only that the production
536
+ copyright information is unavailable or has been removed, and must
537
+ not be interpreted to mean that the audio is public domain. Every
538
+ time this field is displayed the field must be preceded with
539
+ "Produced " (P) " ", where (P) is one character showing a P in a
540
+ circle.
541
+
542
+ TPUB
543
+ The 'Publisher' frame simply contains the name of the label or
544
+ publisher.
545
+
546
+ TOWN
547
+ The 'File owner/licensee' frame contains the name of the owner or
548
+ licensee of the file and it's contents.
549
+
550
+ TRSN
551
+ The 'Internet radio station name' frame contains the name of the
552
+ internet radio station from which the audio is streamed.
553
+
554
+ TRSO
555
+ The 'Internet radio station owner' frame contains the name of the
556
+ owner of the internet radio station from which the audio is
557
+ streamed.
558
+
559
+ 4.2.5. Other text frames
560
+
561
+ TOFN
562
+ The 'Original filename' frame contains the preferred filename for the
563
+ file, since some media doesn't allow the desired length of the
564
+ filename. The filename is case sensitive and includes its suffix.
565
+
566
+ TDLY
567
+ The 'Playlist delay' defines the numbers of milliseconds of silence
568
+ that should be inserted before this audio. The value zero indicates
569
+ that this is a part of a multifile audio track that should be played
570
+ continuously.
571
+
572
+ TDEN
573
+ The 'Encoding time' frame contains a timestamp describing when the
574
+ audio was encoded. Timestamp format is described in the ID3v2
575
+ structure document [ID3v2-strct].
576
+
577
+ TDOR
578
+ The 'Original release time' frame contains a timestamp describing
579
+ when the original recording of the audio was released. Timestamp
580
+ format is described in the ID3v2 structure document [ID3v2-strct].
581
+
582
+ TDRC
583
+ The 'Recording time' frame contains a timestamp describing when the
584
+ audio was recorded. Timestamp format is described in the ID3v2
585
+ structure document [ID3v2-strct].
586
+
587
+ TDRL
588
+ The 'Release time' frame contains a timestamp describing when the
589
+ audio was first released. Timestamp format is described in the ID3v2
590
+ structure document [ID3v2-strct].
591
+
592
+ TDTG
593
+ The 'Tagging time' frame contains a timestamp describing then the
594
+ audio was tagged. Timestamp format is described in the ID3v2
595
+ structure document [ID3v2-strct].
596
+
597
+ TSSE
598
+ The 'Software/Hardware and settings used for encoding' frame
599
+ includes the used audio encoder and its settings when the file was
600
+ encoded. Hardware refers to hardware encoders, not the computer on
601
+ which a program was run.
602
+
603
+ TSOA
604
+ The 'Album sort order' frame defines a string which should be used
605
+ instead of the album name (TALB) for sorting purposes. E.g. an album
606
+ named "A Soundtrack" might preferably be sorted as "Soundtrack".
607
+
608
+ TSOP
609
+ The 'Performer sort order' frame defines a string which should be
610
+ used instead of the performer (TPE2) for sorting purposes.
611
+
612
+ TSOT
613
+ The 'Title sort order' frame defines a string which should be used
614
+ instead of the title (TIT2) for sorting purposes.
615
+
616
+
617
+ 4.2.6. User defined text information frame
618
+
619
+ This frame is intended for one-string text information concerning the
620
+ audio file in a similar way to the other "T"-frames. The frame body
621
+ consists of a description of the string, represented as a terminated
622
+ string, followed by the actual string. There may be more than one
623
+ "TXXX" frame in each tag, but only one with the same description.
624
+
625
+ <Header for 'User defined text information frame', ID: "TXXX">
626
+ Text encoding $xx
627
+ Description <text string according to encoding> $00 (00)
628
+ Value <text string according to encoding>
629
+
630
+
631
+ 4.3. URL link frames
632
+
633
+ With these frames dynamic data such as webpages with touring
634
+ information, price information or plain ordinary news can be added to
635
+ the tag. There may only be one URL [URL] link frame of its kind in an
636
+ tag, except when stated otherwise in the frame description. If the
637
+ text string is followed by a string termination, all the following
638
+ information should be ignored and not be displayed. All URL link
639
+ frame identifiers begins with "W". Only URL link frame identifiers
640
+ begins with "W", except for "WXXX". All URL link frames have the
641
+ following format:
642
+
643
+ <Header for 'URL link frame', ID: "W000" - "WZZZ", excluding "WXXX"
644
+ described in 4.3.2.>
645
+ URL <text string>
646
+
647
+
648
+ 4.3.1. URL link frames - details
649
+
650
+ WCOM
651
+ The 'Commercial information' frame is a URL pointing at a webpage
652
+ with information such as where the album can be bought. There may be
653
+ more than one "WCOM" frame in a tag, but not with the same content.
654
+
655
+ WCOP
656
+ The 'Copyright/Legal information' frame is a URL pointing at a
657
+ webpage where the terms of use and ownership of the file is
658
+ described.
659
+
660
+ WOAF
661
+ The 'Official audio file webpage' frame is a URL pointing at a file
662
+ specific webpage.
663
+
664
+ WOAR
665
+ The 'Official artist/performer webpage' frame is a URL pointing at
666
+ the artists official webpage. There may be more than one "WOAR" frame
667
+ in a tag if the audio contains more than one performer, but not with
668
+ the same content.
669
+
670
+ WOAS
671
+ The 'Official audio source webpage' frame is a URL pointing at the
672
+ official webpage for the source of the audio file, e.g. a movie.
673
+
674
+ WORS
675
+ The 'Official Internet radio station homepage' contains a URL
676
+ pointing at the homepage of the internet radio station.
677
+
678
+ WPAY
679
+ The 'Payment' frame is a URL pointing at a webpage that will handle
680
+ the process of paying for this file.
681
+
682
+ WPUB
683
+ The 'Publishers official webpage' frame is a URL pointing at the
684
+ official webpage for the publisher.
685
+
686
+
687
+ 4.3.2. User defined URL link frame
688
+
689
+ This frame is intended for URL [URL] links concerning the audio file
690
+ in a similar way to the other "W"-frames. The frame body consists
691
+ of a description of the string, represented as a terminated string,
692
+ followed by the actual URL. The URL is always encoded with ISO-8859-1
693
+ [ISO-8859-1]. There may be more than one "WXXX" frame in each tag,
694
+ but only one with the same description.
695
+
696
+ <Header for 'User defined URL link frame', ID: "WXXX">
697
+ Text encoding $xx
698
+ Description <text string according to encoding> $00 (00)
699
+ URL <text string>
700
+
701
+
702
+ 4.4. Music CD identifier
703
+
704
+ This frame is intended for music that comes from a CD, so that the CD
705
+ can be identified in databases such as the CDDB [CDDB]. The frame
706
+ consists of a binary dump of the Table Of Contents, TOC, from the CD,
707
+ which is a header of 4 bytes and then 8 bytes/track on the CD plus 8
708
+ bytes for the 'lead out', making a maximum of 804 bytes. The offset
709
+ to the beginning of every track on the CD should be described with a
710
+ four bytes absolute CD-frame address per track, and not with absolute
711
+ time. When this frame is used the presence of a valid "TRCK" frame is
712
+ REQUIRED, even if the CD's only got one track. It is recommended that
713
+ this frame is always added to tags originating from CDs. There may
714
+ only be one "MCDI" frame in each tag.
715
+
716
+ <Header for 'Music CD identifier', ID: "MCDI">
717
+ CD TOC <binary data>
718
+
719
+
720
+ 4.5. Event timing codes
721
+
722
+ This frame allows synchronisation with key events in the audio. The
723
+ header is:
724
+
725
+ <Header for 'Event timing codes', ID: "ETCO">
726
+ Time stamp format $xx
727
+
728
+ Where time stamp format is:
729
+
730
+ $01 Absolute time, 32 bit sized, using MPEG [MPEG] frames as unit
731
+ $02 Absolute time, 32 bit sized, using milliseconds as unit
732
+
733
+ Absolute time means that every stamp contains the time from the
734
+ beginning of the file.
735
+
736
+ Followed by a list of key events in the following format:
737
+
738
+ Type of event $xx
739
+ Time stamp $xx (xx ...)
740
+
741
+ The 'Time stamp' is set to zero if directly at the beginning of the
742
+ sound or after the previous event. All events MUST be sorted in
743
+ chronological order. The type of event is as follows:
744
+
745
+ $00 padding (has no meaning)
746
+ $01 end of initial silence
747
+ $02 intro start
748
+ $03 main part start
749
+ $04 outro start
750
+ $05 outro end
751
+ $06 verse start
752
+ $07 refrain start
753
+ $08 interlude start
754
+ $09 theme start
755
+ $0A variation start
756
+ $0B key change
757
+ $0C time change
758
+ $0D momentary unwanted noise (Snap, Crackle & Pop)
759
+ $0E sustained noise
760
+ $0F sustained noise end
761
+ $10 intro end
762
+ $11 main part end
763
+ $12 verse end
764
+ $13 refrain end
765
+ $14 theme end
766
+ $15 profanity
767
+ $16 profanity end
768
+
769
+ $17-$DF reserved for future use
770
+
771
+ $E0-$EF not predefined synch 0-F
772
+
773
+ $F0-$FC reserved for future use
774
+
775
+ $FD audio end (start of silence)
776
+ $FE audio file ends
777
+ $FF one more byte of events follows (all the following bytes with
778
+ the value $FF have the same function)
779
+
780
+ Terminating the start events such as "intro start" is OPTIONAL. The
781
+ 'Not predefined synch's ($E0-EF) are for user events. You might want
782
+ to synchronise your music to something, like setting off an explosion
783
+ on-stage, activating a screensaver etc.
784
+
785
+ There may only be one "ETCO" frame in each tag.
786
+
787
+
788
+ 4.6. MPEG location lookup table
789
+
790
+ To increase performance and accuracy of jumps within a MPEG [MPEG]
791
+ audio file, frames with time codes in different locations in the file
792
+ might be useful. This ID3v2 frame includes references that the
793
+ software can use to calculate positions in the file. After the frame
794
+ header follows a descriptor of how much the 'frame counter' should be
795
+ increased for every reference. If this value is two then the first
796
+ reference points out the second frame, the 2nd reference the 4th
797
+ frame, the 3rd reference the 6th frame etc. In a similar way the
798
+ 'bytes between reference' and 'milliseconds between reference' points
799
+ out bytes and milliseconds respectively.
800
+
801
+ Each reference consists of two parts; a certain number of bits, as
802
+ defined in 'bits for bytes deviation', that describes the difference
803
+ between what is said in 'bytes between reference' and the reality and
804
+ a certain number of bits, as defined in 'bits for milliseconds
805
+ deviation', that describes the difference between what is said in
806
+ 'milliseconds between reference' and the reality. The number of bits
807
+ in every reference, i.e. 'bits for bytes deviation'+'bits for
808
+ milliseconds deviation', must be a multiple of four. There may only
809
+ be one "MLLT" frame in each tag.
810
+
811
+ <Header for 'Location lookup table', ID: "MLLT">
812
+ MPEG frames between reference $xx xx
813
+ Bytes between reference $xx xx xx
814
+ Milliseconds between reference $xx xx xx
815
+ Bits for bytes deviation $xx
816
+ Bits for milliseconds dev. $xx
817
+
818
+ Then for every reference the following data is included;
819
+
820
+ Deviation in bytes %xxx....
821
+ Deviation in milliseconds %xxx....
822
+
823
+
824
+ 4.7. Synchronised tempo codes
825
+
826
+ For a more accurate description of the tempo of a musical piece, this
827
+ frame might be used. After the header follows one byte describing
828
+ which time stamp format should be used. Then follows one or more
829
+ tempo codes. Each tempo code consists of one tempo part and one time
830
+ part. The tempo is in BPM described with one or two bytes. If the
831
+ first byte has the value $FF, one more byte follows, which is added
832
+ to the first giving a range from 2 - 510 BPM, since $00 and $01 is
833
+ reserved. $00 is used to describe a beat-free time period, which is
834
+ not the same as a music-free time period. $01 is used to indicate one
835
+ single beat-stroke followed by a beat-free period.
836
+
837
+ The tempo descriptor is followed by a time stamp. Every time the
838
+ tempo in the music changes, a tempo descriptor may indicate this for
839
+ the player. All tempo descriptors MUST be sorted in chronological
840
+ order. The first beat-stroke in a time-period is at the same time as
841
+ the beat description occurs. There may only be one "SYTC" frame in
842
+ each tag.
843
+
844
+ <Header for 'Synchronised tempo codes', ID: "SYTC">
845
+ Time stamp format $xx
846
+ Tempo data <binary data>
847
+
848
+ Where time stamp format is:
849
+
850
+ $01 Absolute time, 32 bit sized, using MPEG [MPEG] frames as unit
851
+ $02 Absolute time, 32 bit sized, using milliseconds as unit
852
+
853
+ Absolute time means that every stamp contains the time from the
854
+ beginning of the file.
855
+
856
+
857
+ 4.8. Unsynchronised lyrics/text transcription
858
+
859
+ This frame contains the lyrics of the song or a text transcription of
860
+ other vocal activities. The head includes an encoding descriptor and
861
+ a content descriptor. The body consists of the actual text. The
862
+ 'Content descriptor' is a terminated string. If no descriptor is
863
+ entered, 'Content descriptor' is $00 (00) only. Newline characters
864
+ are allowed in the text. There may be more than one 'Unsynchronised
865
+ lyrics/text transcription' frame in each tag, but only one with the
866
+ same language and content descriptor.
867
+
868
+ <Header for 'Unsynchronised lyrics/text transcription', ID: "USLT">
869
+ Text encoding $xx
870
+ Language $xx xx xx
871
+ Content descriptor <text string according to encoding> $00 (00)
872
+ Lyrics/text <full text string according to encoding>
873
+
874
+
875
+ 4.9. Synchronised lyrics/text
876
+
877
+ This is another way of incorporating the words, said or sung lyrics,
878
+ in the audio file as text, this time, however, in sync with the
879
+ audio. It might also be used to describing events e.g. occurring on a
880
+ stage or on the screen in sync with the audio. The header includes a
881
+ content descriptor, represented with as terminated text string. If no
882
+ descriptor is entered, 'Content descriptor' is $00 (00) only.
883
+
884
+ <Header for 'Synchronised lyrics/text', ID: "SYLT">
885
+ Text encoding $xx
886
+ Language $xx xx xx
887
+ Time stamp format $xx
888
+ Content type $xx
889
+ Content descriptor <text string according to encoding> $00 (00)
890
+
891
+ Content type: $00 is other
892
+ $01 is lyrics
893
+ $02 is text transcription
894
+ $03 is movement/part name (e.g. "Adagio")
895
+ $04 is events (e.g. "Don Quijote enters the stage")
896
+ $05 is chord (e.g. "Bb F Fsus")
897
+ $06 is trivia/'pop up' information
898
+ $07 is URLs to webpages
899
+ $08 is URLs to images
900
+
901
+ Time stamp format:
902
+
903
+ $01 Absolute time, 32 bit sized, using MPEG [MPEG] frames as unit
904
+ $02 Absolute time, 32 bit sized, using milliseconds as unit
905
+
906
+ Absolute time means that every stamp contains the time from the
907
+ beginning of the file.
908
+
909
+ The text that follows the frame header differs from that of the
910
+ unsynchronised lyrics/text transcription in one major way. Each
911
+ syllable (or whatever size of text is considered to be convenient by
912
+ the encoder) is a null terminated string followed by a time stamp
913
+ denoting where in the sound file it belongs. Each sync thus has the
914
+ following structure:
915
+
916
+ Terminated text to be synced (typically a syllable)
917
+ Sync identifier (terminator to above string) $00 (00)
918
+ Time stamp $xx (xx ...)
919
+
920
+ The 'time stamp' is set to zero or the whole sync is omitted if
921
+ located directly at the beginning of the sound. All time stamps
922
+ should be sorted in chronological order. The sync can be considered
923
+ as a validator of the subsequent string.
924
+
925
+ Newline characters are allowed in all "SYLT" frames and MUST be used
926
+ after every entry (name, event etc.) in a frame with the content type
927
+ $03 - $04.
928
+
929
+ A few considerations regarding whitespace characters: Whitespace
930
+ separating words should mark the beginning of a new word, thus
931
+ occurring in front of the first syllable of a new word. This is also
932
+ valid for new line characters. A syllable followed by a comma should
933
+ not be broken apart with a sync (both the syllable and the comma
934
+ should be before the sync).
935
+
936
+ An example: The "USLT" passage
937
+
938
+ "Strangers in the night" $0A "Exchanging glances"
939
+
940
+ would be "SYLT" encoded as:
941
+
942
+ "Strang" $00 xx xx "ers" $00 xx xx " in" $00 xx xx " the" $00 xx xx
943
+ " night" $00 xx xx 0A "Ex" $00 xx xx "chang" $00 xx xx "ing" $00 xx
944
+ xx "glan" $00 xx xx "ces" $00 xx xx
945
+
946
+ There may be more than one "SYLT" frame in each tag, but only one
947
+ with the same language and content descriptor.
948
+
949
+
950
+ 4.10. Comments
951
+
952
+ This frame is intended for any kind of full text information that
953
+ does not fit in any other frame. It consists of a frame header
954
+ followed by encoding, language and content descriptors and is ended
955
+ with the actual comment as a text string. Newline characters are
956
+ allowed in the comment text string. There may be more than one
957
+ comment frame in each tag, but only one with the same language and
958
+ content descriptor.
959
+
960
+ <Header for 'Comment', ID: "COMM">
961
+ Text encoding $xx
962
+ Language $xx xx xx
963
+ Short content descrip. <text string according to encoding> $00 (00)
964
+ The actual text <full text string according to encoding>
965
+
966
+
967
+ 4.11. Relative volume adjustment (2)
968
+
969
+ This is a more subjective frame than the previous ones. It allows the
970
+ user to say how much he wants to increase/decrease the volume on each
971
+ channel when the file is played. The purpose is to be able to align
972
+ all files to a reference volume, so that you don't have to change the
973
+ volume constantly. This frame may also be used to balance adjust the
974
+ audio. The volume adjustment is encoded as a fixed point decibel
975
+ value, 16 bit signed integer representing (adjustment*512), giving
976
+ +/- 64 dB with a precision of 0.001953125 dB. E.g. +2 dB is stored as
977
+ $04 00 and -2 dB is $FC 00. There may be more than one "RVA2" frame
978
+ in each tag, but only one with the same identification string.
979
+
980
+ <Header for 'Relative volume adjustment (2)', ID: "RVA2">
981
+ Identification <text string> $00
982
+
983
+ The 'identification' string is used to identify the situation and/or
984
+ device where this adjustment should apply. The following is then
985
+ repeated for every channel
986
+
987
+ Type of channel $xx
988
+ Volume adjustment $xx xx
989
+ Bits representing peak $xx
990
+ Peak volume $xx (xx ...)
991
+
992
+
993
+ Type of channel: $00 Other
994
+ $01 Master volume
995
+ $02 Front right
996
+ $03 Front left
997
+ $04 Back right
998
+ $05 Back left
999
+ $06 Front centre
1000
+ $07 Back centre
1001
+ $08 Subwoofer
1002
+
1003
+ Bits representing peak can be any number between 0 and 255. 0 means
1004
+ that there is no peak volume field. The peak volume field is always
1005
+ padded to whole bytes, setting the most significant bits to zero.
1006
+
1007
+
1008
+ 4.12. Equalisation (2)
1009
+
1010
+ This is another subjective, alignment frame. It allows the user to
1011
+ predefine an equalisation curve within the audio file. There may be
1012
+ more than one "EQU2" frame in each tag, but only one with the same
1013
+ identification string.
1014
+
1015
+ <Header of 'Equalisation (2)', ID: "EQU2">
1016
+ Interpolation method $xx
1017
+ Identification <text string> $00
1018
+
1019
+ The 'interpolation method' describes which method is preferred when
1020
+ an interpolation between the adjustment point that follows. The
1021
+ following methods are currently defined:
1022
+
1023
+ $00 Band
1024
+ No interpolation is made. A jump from one adjustment level to
1025
+ another occurs in the middle between two adjustment points.
1026
+ $01 Linear
1027
+ Interpolation between adjustment points is linear.
1028
+
1029
+ The 'identification' string is used to identify the situation and/or
1030
+ device where this adjustment should apply. The following is then
1031
+ repeated for every adjustment point
1032
+
1033
+ Frequency $xx xx
1034
+ Volume adjustment $xx xx
1035
+
1036
+ The frequency is stored in units of 1/2 Hz, giving it a range from 0
1037
+ to 32767 Hz.
1038
+
1039
+ The volume adjustment is encoded as a fixed point decibel value, 16
1040
+ bit signed integer representing (adjustment*512), giving +/- 64 dB
1041
+ with a precision of 0.001953125 dB. E.g. +2 dB is stored as $04 00
1042
+ and -2 dB is $FC 00.
1043
+
1044
+ Adjustment points should be ordered by frequency and one frequency
1045
+ should only be described once in the frame.
1046
+
1047
+
1048
+ 4.13. Reverb
1049
+
1050
+ Yet another subjective frame, with which you can adjust echoes of
1051
+ different kinds. Reverb left/right is the delay between every bounce
1052
+ in ms. Reverb bounces left/right is the number of bounces that should
1053
+ be made. $FF equals an infinite number of bounces. Feedback is the
1054
+ amount of volume that should be returned to the next echo bounce. $00
1055
+ is 0%, $FF is 100%. If this value were $7F, there would be 50% volume
1056
+ reduction on the first bounce, 50% of that on the second and so on.
1057
+ Left to left means the sound from the left bounce to be played in the
1058
+ left speaker, while left to right means sound from the left bounce to
1059
+ be played in the right speaker.
1060
+
1061
+ 'Premix left to right' is the amount of left sound to be mixed in the
1062
+ right before any reverb is applied, where $00 id 0% and $FF is 100%.
1063
+ 'Premix right to left' does the same thing, but right to left.
1064
+ Setting both premix to $FF would result in a mono output (if the
1065
+ reverb is applied symmetric). There may only be one "RVRB" frame in
1066
+ each tag.
1067
+
1068
+ <Header for 'Reverb', ID: "RVRB">
1069
+ Reverb left (ms) $xx xx
1070
+ Reverb right (ms) $xx xx
1071
+ Reverb bounces, left $xx
1072
+ Reverb bounces, right $xx
1073
+ Reverb feedback, left to left $xx
1074
+ Reverb feedback, left to right $xx
1075
+ Reverb feedback, right to right $xx
1076
+ Reverb feedback, right to left $xx
1077
+ Premix left to right $xx
1078
+ Premix right to left $xx
1079
+
1080
+
1081
+ 4.14. Attached picture
1082
+
1083
+ This frame contains a picture directly related to the audio file.
1084
+ Image format is the MIME type and subtype [MIME] for the image. In
1085
+ the event that the MIME media type name is omitted, "image/" will be
1086
+ implied. The "image/png" [PNG] or "image/jpeg" [JFIF] picture format
1087
+ should be used when interoperability is wanted. Description is a
1088
+ short description of the picture, represented as a terminated
1089
+ text string. There may be several pictures attached to one file, each
1090
+ in their individual "APIC" frame, but only one with the same content
1091
+ descriptor. There may only be one picture with the picture type
1092
+ declared as picture type $01 and $02 respectively. There is the
1093
+ possibility to put only a link to the image file by using the 'MIME
1094
+ type' "-->" and having a complete URL [URL] instead of picture data.
1095
+ The use of linked files should however be used sparingly since there
1096
+ is the risk of separation of files.
1097
+
1098
+ <Header for 'Attached picture', ID: "APIC">
1099
+ Text encoding $xx
1100
+ MIME type <text string> $00
1101
+ Picture type $xx
1102
+ Description <text string according to encoding> $00 (00)
1103
+ Picture data <binary data>
1104
+
1105
+
1106
+ Picture type: $00 Other
1107
+ $01 32x32 pixels 'file icon' (PNG only)
1108
+ $02 Other file icon
1109
+ $03 Cover (front)
1110
+ $04 Cover (back)
1111
+ $05 Leaflet page
1112
+ $06 Media (e.g. label side of CD)
1113
+ $07 Lead artist/lead performer/soloist
1114
+ $08 Artist/performer
1115
+ $09 Conductor
1116
+ $0A Band/Orchestra
1117
+ $0B Composer
1118
+ $0C Lyricist/text writer
1119
+ $0D Recording Location
1120
+ $0E During recording
1121
+ $0F During performance
1122
+ $10 Movie/video screen capture
1123
+ $11 A bright coloured fish
1124
+ $12 Illustration
1125
+ $13 Band/artist logotype
1126
+ $14 Publisher/Studio logotype
1127
+
1128
+
1129
+ 4.15. General encapsulated object
1130
+
1131
+ In this frame any type of file can be encapsulated. After the header,
1132
+ 'Frame size' and 'Encoding' follows 'MIME type' [MIME] represented as
1133
+ as a terminated string encoded with ISO 8859-1 [ISO-8859-1]. The
1134
+ filename is case sensitive and is encoded as 'Encoding'. Then follows
1135
+ a content description as terminated string, encoded as 'Encoding'.
1136
+ The last thing in the frame is the actual object. The first two
1137
+ strings may be omitted, leaving only their terminations. MIME type is
1138
+ always an ISO-8859-1 text string. There may be more than one "GEOB"
1139
+ frame in each tag, but only one with the same content descriptor.
1140
+
1141
+ <Header for 'General encapsulated object', ID: "GEOB">
1142
+ Text encoding $xx
1143
+ MIME type <text string> $00
1144
+ Filename <text string according to encoding> $00 (00)
1145
+ Content description <text string according to encoding> $00 (00)
1146
+ Encapsulated object <binary data>
1147
+
1148
+
1149
+ 4.16. Play counter
1150
+
1151
+ This is simply a counter of the number of times a file has been
1152
+ played. The value is increased by one every time the file begins to
1153
+ play. There may only be one "PCNT" frame in each tag. When the
1154
+ counter reaches all one's, one byte is inserted in front of the
1155
+ counter thus making the counter eight bits bigger. The counter must
1156
+ be at least 32-bits long to begin with.
1157
+
1158
+ <Header for 'Play counter', ID: "PCNT">
1159
+ Counter $xx xx xx xx (xx ...)
1160
+
1161
+
1162
+ 4.17. Popularimeter
1163
+
1164
+ The purpose of this frame is to specify how good an audio file is.
1165
+ Many interesting applications could be found to this frame such as a
1166
+ playlist that features better audio files more often than others or
1167
+ it could be used to profile a person's taste and find other 'good'
1168
+ files by comparing people's profiles. The frame contains the email
1169
+ address to the user, one rating byte and a four byte play counter,
1170
+ intended to be increased with one for every time the file is played.
1171
+ The email is a terminated string. The rating is 1-255 where 1 is
1172
+ worst and 255 is best. 0 is unknown. If no personal counter is wanted
1173
+ it may be omitted. When the counter reaches all one's, one byte is
1174
+ inserted in front of the counter thus making the counter eight bits
1175
+ bigger in the same away as the play counter ("PCNT"). There may be
1176
+ more than one "POPM" frame in each tag, but only one with the same
1177
+ email address.
1178
+
1179
+ <Header for 'Popularimeter', ID: "POPM">
1180
+ Email to user <text string> $00
1181
+ Rating $xx
1182
+ Counter $xx xx xx xx (xx ...)
1183
+
1184
+
1185
+ 4.18. Recommended buffer size
1186
+
1187
+ Sometimes the server from which an audio file is streamed is aware of
1188
+ transmission or coding problems resulting in interruptions in the
1189
+ audio stream. In these cases, the size of the buffer can be
1190
+ recommended by the server using this frame. If the 'embedded info
1191
+ flag' is true (1) then this indicates that an ID3 tag with the
1192
+ maximum size described in 'Buffer size' may occur in the audio
1193
+ stream. In such case the tag should reside between two MPEG [MPEG]
1194
+ frames, if the audio is MPEG encoded. If the position of the next tag
1195
+ is known, 'offset to next tag' may be used. The offset is calculated
1196
+ from the end of tag in which this frame resides to the first byte of
1197
+ the header in the next. This field may be omitted. Embedded tags are
1198
+ generally not recommended since this could render unpredictable
1199
+ behaviour from present software/hardware.
1200
+
1201
+ For applications like streaming audio it might be an idea to embed
1202
+ tags into the audio stream though. If the clients connects to
1203
+ individual connections like HTTP and there is a possibility to begin
1204
+ every transmission with a tag, then this tag should include a
1205
+ 'recommended buffer size' frame. If the client is connected to a
1206
+ arbitrary point in the stream, such as radio or multicast, then the
1207
+ 'recommended buffer size' frame SHOULD be included in every tag.
1208
+
1209
+ The 'Buffer size' should be kept to a minimum. There may only be one
1210
+ "RBUF" frame in each tag.
1211
+
1212
+ <Header for 'Recommended buffer size', ID: "RBUF">
1213
+ Buffer size $xx xx xx
1214
+ Embedded info flag %0000000x
1215
+ Offset to next tag $xx xx xx xx
1216
+
1217
+
1218
+ 4.19. Audio encryption
1219
+
1220
+ This frame indicates if the actual audio stream is encrypted, and by
1221
+ whom. Since standardisation of such encryption scheme is beyond this
1222
+ document, all "AENC" frames begin with a terminated string with a
1223
+ URL containing an email address, or a link to a location where an
1224
+ email address can be found, that belongs to the organisation
1225
+ responsible for this specific encrypted audio file. Questions
1226
+ regarding the encrypted audio should be sent to the email address
1227
+ specified. If a $00 is found directly after the 'Frame size' and the
1228
+ audio file indeed is encrypted, the whole file may be considered
1229
+ useless.
1230
+
1231
+ After the 'Owner identifier', a pointer to an unencrypted part of the
1232
+ audio can be specified. The 'Preview start' and 'Preview length' is
1233
+ described in frames. If no part is unencrypted, these fields should
1234
+ be left zeroed. After the 'preview length' field follows optionally a
1235
+ data block required for decryption of the audio. There may be more
1236
+ than one "AENC" frames in a tag, but only one with the same 'Owner
1237
+ identifier'.
1238
+
1239
+ <Header for 'Audio encryption', ID: "AENC">
1240
+ Owner identifier <text string> $00
1241
+ Preview start $xx xx
1242
+ Preview length $xx xx
1243
+ Encryption info <binary data>
1244
+
1245
+
1246
+ 4.20. Linked information
1247
+
1248
+ To keep information duplication as low as possible this frame may be
1249
+ used to link information from another ID3v2 tag that might reside in
1250
+ another audio file or alone in a binary file. It is RECOMMENDED that
1251
+ this method is only used when the files are stored on a CD-ROM or
1252
+ other circumstances when the risk of file separation is low. The
1253
+ frame contains a frame identifier, which is the frame that should be
1254
+ linked into this tag, a URL [URL] field, where a reference to the
1255
+ file where the frame is given, and additional ID data, if needed.
1256
+ Data should be retrieved from the first tag found in the file to
1257
+ which this link points. There may be more than one "LINK" frame in a
1258
+ tag, but only one with the same contents. A linked frame is to be
1259
+ considered as part of the tag and has the same restrictions as if it
1260
+ was a physical part of the tag (i.e. only one "RVRB" frame allowed,
1261
+ whether it's linked or not).
1262
+
1263
+ <Header for 'Linked information', ID: "LINK">
1264
+ Frame identifier $xx xx xx xx
1265
+ URL <text string> $00
1266
+ ID and additional data <text string(s)>
1267
+
1268
+ Frames that may be linked and need no additional data are "ASPI",
1269
+ "ETCO", "EQU2", "MCID", "MLLT", "OWNE", "RVA2", "RVRB", "SYTC", the
1270
+ text information frames and the URL link frames.
1271
+
1272
+ The "AENC", "APIC", "GEOB" and "TXXX" frames may be linked with
1273
+ the content descriptor as additional ID data.
1274
+
1275
+ The "USER" frame may be linked with the language field as additional
1276
+ ID data.
1277
+
1278
+ The "PRIV" frame may be linked with the owner identifier as
1279
+ additional ID data.
1280
+
1281
+ The "COMM", "SYLT" and "USLT" frames may be linked with three bytes
1282
+ of language descriptor directly followed by a content descriptor as
1283
+ additional ID data.
1284
+
1285
+
1286
+ 4.21. Position synchronisation frame
1287
+
1288
+ This frame delivers information to the listener of how far into the
1289
+ audio stream he picked up; in effect, it states the time offset from
1290
+ the first frame in the stream. The frame layout is:
1291
+
1292
+ <Head for 'Position synchronisation', ID: "POSS">
1293
+ Time stamp format $xx
1294
+ Position $xx (xx ...)
1295
+
1296
+ Where time stamp format is:
1297
+
1298
+ $01 Absolute time, 32 bit sized, using MPEG frames as unit
1299
+ $02 Absolute time, 32 bit sized, using milliseconds as unit
1300
+
1301
+ and position is where in the audio the listener starts to receive,
1302
+ i.e. the beginning of the next frame. If this frame is used in the
1303
+ beginning of a file the value is always 0. There may only be one
1304
+ "POSS" frame in each tag.
1305
+
1306
+
1307
+ 4.22. Terms of use frame
1308
+
1309
+ This frame contains a brief description of the terms of use and
1310
+ ownership of the file. More detailed information concerning the legal
1311
+ terms might be available through the "WCOP" frame. Newlines are
1312
+ allowed in the text. There may be more than one 'Terms of use' frame
1313
+ in a tag, but only one with the same 'Language'.
1314
+
1315
+ <Header for 'Terms of use frame', ID: "USER">
1316
+ Text encoding $xx
1317
+ Language $xx xx xx
1318
+ The actual text <text string according to encoding>
1319
+
1320
+
1321
+ 4.23. Ownership frame
1322
+
1323
+ The ownership frame might be used as a reminder of a made transaction
1324
+ or, if signed, as proof. Note that the "USER" and "TOWN" frames are
1325
+ good to use in conjunction with this one. The frame begins, after the
1326
+ frame ID, size and encoding fields, with a 'price paid' field. The
1327
+ first three characters of this field contains the currency used for
1328
+ the transaction, encoded according to ISO 4217 [ISO-4217] alphabetic
1329
+ currency code. Concatenated to this is the actual price paid, as a
1330
+ numerical string using "." as the decimal separator. Next is an 8
1331
+ character date string (YYYYMMDD) followed by a string with the name
1332
+ of the seller as the last field in the frame. There may only be one
1333
+ "OWNE" frame in a tag.
1334
+
1335
+ <Header for 'Ownership frame', ID: "OWNE">
1336
+ Text encoding $xx
1337
+ Price paid <text string> $00
1338
+ Date of purch. <text string>
1339
+ Seller <text string according to encoding>
1340
+
1341
+
1342
+ 4.24. Commercial frame
1343
+
1344
+ This frame enables several competing offers in the same tag by
1345
+ bundling all needed information. That makes this frame rather complex
1346
+ but it's an easier solution than if one tries to achieve the same
1347
+ result with several frames. The frame begins, after the frame ID,
1348
+ size and encoding fields, with a price string field. A price is
1349
+ constructed by one three character currency code, encoded according
1350
+ to ISO 4217 [ISO-4217] alphabetic currency code, followed by a
1351
+ numerical value where "." is used as decimal separator. In the price
1352
+ string several prices may be concatenated, separated by a "/"
1353
+ character, but there may only be one currency of each type.
1354
+
1355
+ The price string is followed by an 8 character date string in the
1356
+ format YYYYMMDD, describing for how long the price is valid. After
1357
+ that is a contact URL, with which the user can contact the seller,
1358
+ followed by a one byte 'received as' field. It describes how the
1359
+ audio is delivered when bought according to the following list:
1360
+
1361
+ $00 Other
1362
+ $01 Standard CD album with other songs
1363
+ $02 Compressed audio on CD
1364
+ $03 File over the Internet
1365
+ $04 Stream over the Internet
1366
+ $05 As note sheets
1367
+ $06 As note sheets in a book with other sheets
1368
+ $07 Music on other media
1369
+ $08 Non-musical merchandise
1370
+
1371
+ Next follows a terminated string with the name of the seller followed
1372
+ by a terminated string with a short description of the product. The
1373
+ last thing is the ability to include a company logotype. The first of
1374
+ them is the 'Picture MIME type' field containing information about
1375
+ which picture format is used. In the event that the MIME media type
1376
+ name is omitted, "image/" will be implied. Currently only "image/png"
1377
+ and "image/jpeg" are allowed. This format string is followed by the
1378
+ binary picture data. This two last fields may be omitted if no
1379
+ picture is attached. There may be more than one 'commercial frame' in
1380
+ a tag, but no two may be identical.
1381
+
1382
+ <Header for 'Commercial frame', ID: "COMR">
1383
+ Text encoding $xx
1384
+ Price string <text string> $00
1385
+ Valid until <text string>
1386
+ Contact URL <text string> $00
1387
+ Received as $xx
1388
+ Name of seller <text string according to encoding> $00 (00)
1389
+ Description <text string according to encoding> $00 (00)
1390
+ Picture MIME type <string> $00
1391
+ Seller logo <binary data>
1392
+
1393
+
1394
+ 4.25. Encryption method registration
1395
+
1396
+ To identify with which method a frame has been encrypted the
1397
+ encryption method must be registered in the tag with this frame. The
1398
+ 'Owner identifier' is a null-terminated string with a URL [URL]
1399
+ containing an email address, or a link to a location where an email
1400
+ address can be found, that belongs to the organisation responsible
1401
+ for this specific encryption method. Questions regarding the
1402
+ encryption method should be sent to the indicated email address. The
1403
+ 'Method symbol' contains a value that is associated with this method
1404
+ throughout the whole tag, in the range $80-F0. All other values are
1405
+ reserved. The 'Method symbol' may optionally be followed by
1406
+ encryption specific data. There may be several "ENCR" frames in a tag
1407
+ but only one containing the same symbol and only one containing the
1408
+ same owner identifier. The method must be used somewhere in the tag.
1409
+ See the description of the frame encryption flag in the ID3v2
1410
+ structure document [ID3v2-strct] for more information.
1411
+
1412
+ <Header for 'Encryption method registration', ID: "ENCR">
1413
+ Owner identifier <text string> $00
1414
+ Method symbol $xx
1415
+ Encryption data <binary data>
1416
+
1417
+
1418
+ 4.26. Group identification registration
1419
+
1420
+ This frame enables grouping of otherwise unrelated frames. This can
1421
+ be used when some frames are to be signed. To identify which frames
1422
+ belongs to a set of frames a group identifier must be registered in
1423
+ the tag with this frame. The 'Owner identifier' is a null-terminated
1424
+ string with a URL [URL] containing an email address, or a link to a
1425
+ location where an email address can be found, that belongs to the
1426
+ organisation responsible for this grouping. Questions regarding the
1427
+ grouping should be sent to the indicated email address. The 'Group
1428
+ symbol' contains a value that associates the frame with this group
1429
+ throughout the whole tag, in the range $80-F0. All other values are
1430
+ reserved. The 'Group symbol' may optionally be followed by some group
1431
+ specific data, e.g. a digital signature. There may be several "GRID"
1432
+ frames in a tag but only one containing the same symbol and only one
1433
+ containing the same owner identifier. The group symbol must be used
1434
+ somewhere in the tag. See the description of the frame grouping flag
1435
+ in the ID3v2 structure document [ID3v2-strct] for more information.
1436
+
1437
+ <Header for 'Group ID registration', ID: "GRID">
1438
+ Owner identifier <text string> $00
1439
+ Group symbol $xx
1440
+ Group dependent data <binary data>
1441
+
1442
+
1443
+ 4.27. Private frame
1444
+
1445
+ This frame is used to contain information from a software producer
1446
+ that its program uses and does not fit into the other frames. The
1447
+ frame consists of an 'Owner identifier' string and the binary data.
1448
+ The 'Owner identifier' is a null-terminated string with a URL [URL]
1449
+ containing an email address, or a link to a location where an email
1450
+ address can be found, that belongs to the organisation responsible
1451
+ for the frame. Questions regarding the frame should be sent to the
1452
+ indicated email address. The tag may contain more than one "PRIV"
1453
+ frame but only with different contents.
1454
+
1455
+ <Header for 'Private frame', ID: "PRIV">
1456
+ Owner identifier <text string> $00
1457
+ The private data <binary data>
1458
+
1459
+
1460
+ 4.28. Signature frame
1461
+
1462
+ This frame enables a group of frames, grouped with the 'Group
1463
+ identification registration', to be signed. Although signatures can
1464
+ reside inside the registration frame, it might be desired to store
1465
+ the signature elsewhere, e.g. in watermarks. There may be more than
1466
+ one 'signature frame' in a tag, but no two may be identical.
1467
+
1468
+ <Header for 'Signature frame', ID: "SIGN">
1469
+ Group symbol $xx
1470
+ Signature <binary data>
1471
+
1472
+
1473
+ 4.29. Seek frame
1474
+
1475
+ This frame indicates where other tags in a file/stream can be found.
1476
+ The 'minimum offset to next tag' is calculated from the end of this
1477
+ tag to the beginning of the next. There may only be one 'seek frame'
1478
+ in a tag.
1479
+
1480
+ <Header for 'Seek frame', ID: "SEEK">
1481
+ Minimum offset to next tag $xx xx xx xx
1482
+
1483
+
1484
+ 4.30. Audio seek point index
1485
+
1486
+ Audio files with variable bit rates are intrinsically difficult to
1487
+ deal with in the case of seeking within the file. The ASPI frame
1488
+ makes seeking easier by providing a list a seek points within the
1489
+ audio file. The seek points are a fractional offset within the audio
1490
+ data, providing a starting point from which to find an appropriate
1491
+ point to start decoding. The presence of an ASPI frame requires the
1492
+ existence of a TLEN frame, indicating the duration of the file in
1493
+ milliseconds. There may only be one 'audio seek point index' frame in
1494
+ a tag.
1495
+
1496
+ <Header for 'Seek Point Index', ID: "ASPI">
1497
+ Indexed data start (S) $xx xx xx xx
1498
+ Indexed data length (L) $xx xx xx xx
1499
+ Number of index points (N) $xx xx
1500
+ Bits per index point (b) $xx
1501
+
1502
+ Then for every index point the following data is included;
1503
+
1504
+ Fraction at index (Fi) $xx (xx)
1505
+
1506
+ 'Indexed data start' is a byte offset from the beginning of the file.
1507
+ 'Indexed data length' is the byte length of the audio data being
1508
+ indexed. 'Number of index points' is the number of index points, as
1509
+ the name implies. The recommended number is 100. 'Bits per index
1510
+ point' is 8 or 16, depending on the chosen precision. 8 bits works
1511
+ well for short files (less than 5 minutes of audio), while 16 bits is
1512
+ advantageous for long files. 'Fraction at index' is the numerator of
1513
+ the fraction representing a relative position in the data. The
1514
+ denominator is 2 to the power of b.
1515
+
1516
+ Here are the algorithms to be used in the calculation. The known data
1517
+ must be the offset of the start of the indexed data (S), the offset
1518
+ of the end of the indexed data (E), the number of index points (N),
1519
+ the offset at index i (Oi). We calculate the fraction at index i
1520
+ (Fi).
1521
+
1522
+ Oi is the offset of the frame whose start is soonest after the point
1523
+ for which the time offset is (i/N * duration).
1524
+
1525
+ The frame data should be calculated as follows:
1526
+
1527
+ Fi = Oi/L * 2^b (rounded down to the nearest integer)
1528
+
1529
+ Offset calculation should be calculated as follows from data in the
1530
+ frame:
1531
+
1532
+ Oi = (Fi/2^b)*L (rounded up to the nearest integer)
1533
+
1534
+
1535
+ 5. Copyright
1536
+
1537
+ Copyright (C) Martin Nilsson 2000. All Rights Reserved.
1538
+
1539
+ This document and translations of it may be copied and furnished to
1540
+ others, and derivative works that comment on or otherwise explain it
1541
+ or assist in its implementation may be prepared, copied, published
1542
+ and distributed, in whole or in part, without restriction of any
1543
+ kind, provided that a reference to this document is included on all
1544
+ such copies and derivative works. However, this document itself may
1545
+ not be modified in any way and reissued as the original document.
1546
+
1547
+ The limited permissions granted above are perpetual and will not be
1548
+ revoked.
1549
+
1550
+ This document and the information contained herein is provided on an
1551
+ "AS IS" basis and THE AUTHORS DISCLAIMS ALL WARRANTIES, EXPRESS OR
1552
+ IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
1553
+ THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
1554
+ WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
1555
+
1556
+
1557
+ 6. References
1558
+
1559
+ [CDDB] Compact Disc Data Base
1560
+
1561
+ http://www.cddb.com">http://www.cddb.com
1562
+
1563
+ [ID3v2.3.0] Martin Nilsson, "ID3v2 informal standard".
1564
+
1565
+ http://www.id3lib.org/id3/id3v2.3.0.txt
1566
+
1567
+ [ID3v2-strct] Martin Nilsson,
1568
+ "ID3 tag version 2.4.0 - Main Structure"
1569
+
1570
+ http://www.id3lib.org/id3/id3v2.4.0-structure.txt
1571
+
1572
+ [ISO-639-2] ISO/FDIS 639-2.
1573
+ Codes for the representation of names of languages, Part 2: Alpha-3
1574
+ code. Technical committee / subcommittee: TC 37 / SC 2
1575
+
1576
+ [ISO-4217] ISO 4217:1995.
1577
+ Codes for the representation of currencies and funds.
1578
+ Technical committee / subcommittee: TC 68
1579
+
1580
+ [ISO-8859-1] ISO/IEC DIS 8859-1.
1581
+ 8-bit single-byte coded graphic character sets, Part 1: Latin
1582
+ alphabet No. 1. Technical committee / subcommittee: JTC 1 / SC 2
1583
+
1584
+ [ISRC] ISO 3901:1986
1585
+ International Standard Recording Code (ISRC).
1586
+ Technical committee / subcommittee: TC 46 / SC 9
1587
+
1588
+ [JFIF] JPEG File Interchange Format, version 1.02
1589
+
1590
+ http://www.w3.org/Graphics/JPEG/jfif.txt
1591
+
1592
+ [KEYWORDS] S. Bradner, 'Key words for use in RFCs to Indicate
1593
+ Requirement Levels', RFC 2119, March 1997.
1594
+
1595
+ ftp://ftp.isi.edu/in-notes/rfc2119.txt
1596
+
1597
+ [MIME] Freed, N. and N. Borenstein, "Multipurpose Internet Mail
1598
+ Extensions (MIME) Part One: Format of Internet Message Bodies",
1599
+ RFC 2045, November 1996.
1600
+
1601
+ ftp://ftp.isi.edu/in-notes/rfc2045.txt
1602
+
1603
+ [MPEG] ISO/IEC 11172-3:1993.
1604
+ Coding of moving pictures and associated audio for digital storage
1605
+ media at up to about 1,5 Mbit/s, Part 3: Audio.
1606
+ Technical committee / subcommittee: JTC 1 / SC 29
1607
+ and
1608
+ ISO/IEC 13818-3:1995
1609
+ Generic coding of moving pictures and associated audio information,
1610
+ Part 3: Audio.
1611
+ Technical committee / subcommittee: JTC 1 / SC 29
1612
+ and
1613
+ ISO/IEC DIS 13818-3
1614
+ Generic coding of moving pictures and associated audio information,
1615
+ Part 3: Audio (Revision of ISO/IEC 13818-3:1995)
1616
+
1617
+
1618
+ [PNG] Portable Network Graphics, version 1.0
1619
+
1620
+ http://www.w3.org/TR/REC-png-multi.html
1621
+
1622
+ [URL] T. Berners-Lee, L. Masinter & M. McCahill, "Uniform Resource
1623
+ Locators (URL).", RFC 1738, December 1994.
1624
+
1625
+ ftp://ftp.isi.edu/in-notes/rfc1738.txt">ftp://ftp.isi.edu/in-notes/rfc1738.txt
1626
+
1627
+ [ZLIB] P. Deutsch, Aladdin Enterprises & J-L. Gailly, "ZLIB
1628
+ Compressed
1629
+ Data Format Specification version 3.3", RFC 1950, May 1996.
1630
+
1631
+ ftp://ftp.isi.edu/in-notes/rfc1950.txt
1632
+
1633
+
1634
+ 7. Appendix
1635
+
1636
+
1637
+ A. Appendix A - Genre List from ID3v1
1638
+
1639
+ The following genres is defined in ID3v1
1640
+
1641
+ 0.Blues
1642
+ 1.Classic Rock
1643
+ 2.Country
1644
+ 3.Dance
1645
+ 4.Disco
1646
+ 5.Funk
1647
+ 6.Grunge
1648
+ 7.Hip-Hop
1649
+ 8.Jazz
1650
+ 9.Metal
1651
+ 10.New Age
1652
+ 11.Oldies
1653
+ 12.Other
1654
+ 13.Pop
1655
+ 14.R&B
1656
+ 15.Rap
1657
+ 16.Reggae
1658
+ 17.Rock
1659
+ 18.Techno
1660
+ 19.Industrial
1661
+ 20.Alternative
1662
+ 21.Ska
1663
+ 22.Death Metal
1664
+ 23.Pranks
1665
+ 24.Soundtrack
1666
+ 25.Euro-Techno
1667
+ 26.Ambient
1668
+ 27.Trip-Hop
1669
+ 28.Vocal
1670
+ 29.Jazz+Funk
1671
+ 30.Fusion
1672
+ 31.Trance
1673
+ 32.Classical
1674
+ 33.Instrumental
1675
+ 34.Acid
1676
+ 35.House
1677
+ 36.Game
1678
+ 37.Sound Clip
1679
+ 38.Gospel
1680
+ 39.Noise
1681
+ 40.AlternRock
1682
+ 41.Bass
1683
+ 42.Soul
1684
+ 43.Punk
1685
+ 44.Space
1686
+ 45.Meditative
1687
+ 46.Instrumental Pop
1688
+ 47.Instrumental Rock
1689
+ 48.Ethnic
1690
+ 49.Gothic
1691
+ 50.Darkwave
1692
+ 51.Techno-Industrial
1693
+ 52.Electronic
1694
+ 53.Pop-Folk
1695
+ 54.Eurodance
1696
+ 55.Dream
1697
+ 56.Southern Rock
1698
+ 57.Comedy
1699
+ 58.Cult
1700
+ 59.Gangsta
1701
+ 60.Top 40
1702
+ 61.Christian Rap
1703
+ 62.Pop/Funk
1704
+ 63.Jungle
1705
+ 64.Native American
1706
+ 65.Cabaret
1707
+ 66.New Wave
1708
+ 67.Psychadelic
1709
+ 68.Rave
1710
+ 69.Showtunes
1711
+ 70.Trailer
1712
+ 71.Lo-Fi
1713
+ 72.Tribal
1714
+ 73.Acid Punk
1715
+ 74.Acid Jazz
1716
+ 75.Polka
1717
+ 76.Retro
1718
+ 77.Musical
1719
+ 78.Rock & Roll
1720
+ 79.Hard Rock
1721
+
1722
+
1723
+ 8. Author's Address
1724
+
1725
+ Written by
1726
+
1727
+ Martin Nilsson
1728
+ Rydsv�gen 246 C. 30
1729
+ SE-584 34 Link�ping
1730
+ Sweden
1731
+
1732
+ Email: nilsson@id3.org