CELLAR Group
Internet Engineering Task Force (IETF) S. Lhomme
Internet-Draft
Intended status: Standards Track
Request for Comments: 9559
Updates: 8794 M. Bunkus
Expires: 24 April 2024
Category: Standards Track
ISSN: 2070-1721 D. Rice
22 October 2023
July 2024
Matroska Media Container Format Specifications
draft-ietf-cellar-matroska-21 Specification
Abstract
This document defines the Matroska audiovisual data container
structure, including definitions of its structural elements, as well
as its
terminology, vocabulary, and application.
This document updates [RFC8794] RFC 8794 to permit the use of a previously
reserved EBML Extensible Binary Meta Language (EBML) Element ID.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force
(IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list It represents the consensus of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid the IETF community. It has
received public review and has been approved for a maximum publication by the
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 7841.
Information about the current status of six months this document, any errata,
and how to provide feedback on it may be updated, replaced, or obsoleted by other documents obtained at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on 24 April 2024.
https://www.rfc-editor.org/info/rfc9559.
Copyright Notice
Copyright (c) 2023 2024 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents (https://trustee.ietf.org/
license-info)
(https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Revised BSD License text as described in Section 4.e of the
Trust Legal Provisions and are provided without warranty as described
in the Revised BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 6
2. Status of this document . . . . . . . . . . . . . . . . . . . 7 This Document
3. Notation and Conventions . . . . . . . . . . . . . . . . . . 7
4. Matroska Overview . . . . . . . . . . . . . . . . . . . . . . 7
4.1. Principles . . . . . . . . . . . . . . . . . . . . . . . 7
4.2. Updates to RFC 8794 . . . . . . . . . . . . . . . . . . . 7
4.3. Added EBML Constraints . . . . . . . . . . . . . . . . . 8
4.4. Design Rules . . . . . . . . . . . . . . . . . . . . . . 9
4.5. Data Layout . . . . . . . . . . . . . . . . . . . . . . . 9
5. Matroska Schema . . . . . . . . . . . . . . . . . . . . . . . 18
5.1. Segment Element . . . . . . . . . . . . . . . . . . . . . 18
5.1.1. SeekHead Element . . . . . . . . . . . . . . . . . . 19
5.1.1.1. Seek Element . . . . . . . . . . . . . . . . . . 19
5.1.2. Info Element . . . . . . . . . . . . . . . . . . . . 19
5.1.2.1. SegmentUUID Element . . . . . . . . . . . . . . . 20
5.1.2.2. SegmentFilename Element . . . . . . . . . . . . . 20
5.1.2.3. PrevUUID Element . . . . . . . . . . . . . . . . 20
5.1.2.4. PrevFilename Element . . . . . . . . . . . . . . 20
5.1.2.5. NextUUID Element . . . . . . . . . . . . . . . . 21
5.1.2.6. NextFilename Element . . . . . . . . . . . . . . 21
5.1.2.7. SegmentFamily Element . . . . . . . . . . . . . . 21
5.1.2.8. ChapterTranslate Element . . . . . . . . . . . . 21
5.1.2.9. TimestampScale Element . . . . . . . . . . . . . 23
5.1.2.10. Duration Element . . . . . . . . . . . . . . . . 23
5.1.2.11. DateUTC Element . . . . . . . . . . . . . . . . . 23
5.1.2.12. Title Element . . . . . . . . . . . . . . . . . . 23
5.1.2.13. MuxingApp Element . . . . . . . . . . . . . . . . 23
5.1.2.14. WritingApp Element . . . . . . . . . . . . . . . 23
5.1.3. Cluster Element . . . . . . . . . . . . . . . . . . . 24
5.1.3.1. Timestamp Element . . . . . . . . . . . . . . . . 24
5.1.3.2. Position Element . . . . . . . . . . . . . . . . 24
5.1.3.3. PrevSize Element . . . . . . . . . . . . . . . . 24
5.1.3.4. SimpleBlock Element . . . . . . . . . . . . . . . 24
5.1.3.5. BlockGroup Element . . . . . . . . . . . . . . . 25
5.1.4. Tracks Element . . . . . . . . . . . . . . . . . . . 28
5.1.4.1. TrackEntry Element . . . . . . . . . . . . . . . 28
5.1.5. Cues Element . . . . . . . . . . . . . . . . . . . . 67
5.1.5.1. CuePoint Element . . . . . . . . . . . . . . . . 67
5.1.6. Attachments Element . . . . . . . . . . . . . . . . . 69
5.1.6.1. AttachedFile Element . . . . . . . . . . . . . . 69
5.1.7. Chapters Element . . . . . . . . . . . . . . . . . . 70
5.1.7.1. EditionEntry Element . . . . . . . . . . . . . . 71
5.1.8. Tags Element . . . . . . . . . . . . . . . . . . . . 76
5.1.8.1. Tag Element . . . . . . . . . . . . . . . . . . . 76
6. Matroska Element Ordering . . . . . . . . . . . . . . . . . . 82
6.1. Top-Level Elements . . . . . . . . . . . . . . . . . . . 82
6.2. CRC-32 . . . . . . . . . . . . . . . . . . . . . . . . . 83
6.3. SeekHead . . . . . . . . . . . . . . . . . . . . . . . . 83
6.4. Cues (index) . . . . . . . . . . . . . . . . . . . . . . 83 (Index)
6.5. Info . . . . . . . . . . . . . . . . . . . . . . . . . . 83
6.6. Chapters Element . . . . . . . . . . . . . . . . . . . . 84
6.7. Attachments . . . . . . . . . . . . . . . . . . . . . . . 84
6.8. Tags . . . . . . . . . . . . . . . . . . . . . . . . . . 84
7. Matroska versioning . . . . . . . . . . . . . . . . . . . . . 84 Versioning
8. Stream Copy . . . . . . . . . . . . . . . . . . . . . . . . . 85
9. DefaultDecodedFieldDuration . . . . . . . . . . . . . . . . . 86
10. Cluster Blocks . . . . . . . . . . . . . . . . . . . . . . . 86
10.1. Block Structure . . . . . . . . . . . . . . . . . . . . 87
10.2. SimpleBlock Structure . . . . . . . . . . . . . . . . . 88
10.3. Block Lacing . . . . . . . . . . . . . . . . . . . . . . 90
10.3.1. No lacing . . . . . . . . . . . . . . . . . . . . . 90 Lacing
10.3.2. Xiph lacing . . . . . . . . . . . . . . . . . . . . 91 Lacing
10.3.3. EBML lacing . . . . . . . . . . . . . . . . . . . . 92 Lacing
10.3.4. Fixed-size lacing . . . . . . . . . . . . . . . . . 94 Lacing
10.3.5. Laced Frames Timestamp . . . . . . . . . . . . . . . 94
10.4. Random Access Points . . . . . . . . . . . . . . . . . . 95
11. Timestamps . . . . . . . . . . . . . . . . . . . . . . . . . 98
11.1. Timestamp Ticks . . . . . . . . . . . . . . . . . . . . 99
11.1.1. Matroska Ticks . . . . . . . . . . . . . . . . . . . 99
11.1.2. Segment Ticks . . . . . . . . . . . . . . . . . . . 99
11.1.3. Track Ticks . . . . . . . . . . . . . . . . . . . . 100
11.2. Block Timestamps . . . . . . . . . . . . . . . . . . . . 100
11.3. TimestampScale Rounding . . . . . . . . . . . . . . . . 101
12. Language Codes . . . . . . . . . . . . . . . . . . . . . . . 101
13. Country Codes . . . . . . . . . . . . . . . . . . . . . . . . 102
14. Encryption . . . . . . . . . . . . . . . . . . . . . . . . . 102
15. Image Presentation . . . . . . . . . . . . . . . . . . . . . 103
15.1. Cropping . . . . . . . . . . . . . . . . . . . . . . . . 103
15.2. Rotation . . . . . . . . . . . . . . . . . . . . . . . . 104
16. Segment Position . . . . . . . . . . . . . . . . . . . . . . 104
16.1. Segment Position Exception . . . . . . . . . . . . . . . 104
16.2. Example of Segment Position . . . . . . . . . . . . . . 104
17. Linked Segments . . . . . . . . . . . . . . . . . . . . . . . 105
17.1. Hard Linking . . . . . . . . . . . . . . . . . . . . . . 106
17.2. Medium Linking . . . . . . . . . . . . . . . . . . . . . 108
17.2.1. Linked-Duration . . . . . . . . . . . . . . . . . . 109
17.2.2. Linked-Edition . . . . . . . . . . . . . . . . . . . 109
18. Track Flags . . . . . . . . . . . . . . . . . . . . . . . . . 109
18.1. Default flag . . . . . . . . . . . . . . . . . . . . . . 109 Flag
18.2. Forced flag . . . . . . . . . . . . . . . . . . . . . . 110 Flag
18.3. Hearing-impaired flag . . . . . . . . . . . . . . . . . 110 Hearing-Impaired Flag
18.4. Visual-impaired flag . . . . . . . . . . . . . . . . . . 110 Visual-Impaired Flag
18.5. Descriptions flag . . . . . . . . . . . . . . . . . . . 110 Flag
18.6. Original flag . . . . . . . . . . . . . . . . . . . . . 110 Flag
18.7. Commentary flag . . . . . . . . . . . . . . . . . . . . 110 Flag
18.8. Track Operation . . . . . . . . . . . . . . . . . . . . 110
18.9. Overlay Track . . . . . . . . . . . . . . . . . . . . . 111
18.10. Multi-planar and 3D videos . . . . . . . . . . . . . . . 111 Videos
19. Default track selection . . . . . . . . . . . . . . . . . . . 112 Track Selection
19.1. Audio Selection . . . . . . . . . . . . . . . . . . . . 112
19.2. Subtitle selection . . . . . . . . . . . . . . . . . . . 114 Selection
20. Chapters . . . . . . . . . . . . . . . . . . . . . . . . . . 116
20.1. EditionEntry . . . . . . . . . . . . . . . . . . . . . . 116
20.1.1. EditionFlagDefault . . . . . . . . . . . . . . . . . 116
20.1.2. Default Edition . . . . . . . . . . . . . . . . . . 116
20.1.3. EditionFlagOrdered . . . . . . . . . . . . . . . . . 117
20.1.3.1. Ordered-Edition and Matroska Segment-Linking . . 118 Segment Linking
20.2. ChapterAtom . . . . . . . . . . . . . . . . . . . . . . 119
20.2.1. ChapterTimeStart . . . . . . . . . . . . . . . . . . 119
20.2.2. ChapterTimeEnd . . . . . . . . . . . . . . . . . . . 119
20.2.3. Nested Chapters . . . . . . . . . . . . . . . . . . 119
20.2.4. Nested Chapters in Ordered Chapters . . . . . . . . 120
20.2.5. ChapterFlagHidden . . . . . . . . . . . . . . . . . 120
20.3. Menu features . . . . . . . . . . . . . . . . . . . . . 121 Features
20.4. Physical Types . . . . . . . . . . . . . . . . . . . . . 121
20.5. Chapter Examples . . . . . . . . . . . . . . . . . . . . 122
20.5.1. Example 1 : basic chaptering . . . . . . . . . . . . 122 1: Basic Chaptering
20.5.2. Example 2 : nested chapters . . . . . . . . . . . . 124 2: Nested Chapters
20.5.2.1. The Micronauts "Bleep To Bleep" . . . . . . . . 124
21. Attachments . . . . . . . . . . . . . . . . . . . . . . . . . 126
21.1. Cover Art . . . . . . . . . . . . . . . . . . . . . . . 126
21.2. Font files . . . . . . . . . . . . . . . . . . . . . . . 128 Files
22. Cues . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
22.1. Recommendations . . . . . . . . . . . . . . . . . . . . 130
23. Matroska Streaming . . . . . . . . . . . . . . . . . . . . . 130
23.1. File Access . . . . . . . . . . . . . . . . . . . . . . 130
23.2. Livestreaming . . . . . . . . . . . . . . . . . . . . . 131
24. Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
24.1. Tags Precedence . . . . . . . . . . . . . . . . . . . . 132
24.2. Tag Levels . . . . . . . . . . . . . . . . . . . . . . . 133
25. Implementation Recommendations . . . . . . . . . . . . . . . 133
25.1. Cluster . . . . . . . . . . . . . . . . . . . . . . . . 133
25.2. SeekHead . . . . . . . . . . . . . . . . . . . . . . . . 133
25.3. Optimum Layouts . . . . . . . . . . . . . . . . . . . . 133
25.3.1. Optimum layout Layout for a muxer . . . . . . . . . . . . . 133 Muxer
25.3.2. Optimum layout Layout after editing tags . . . . . . . . . 134 Editing Tags
25.3.3. Optimum layout Layout with Cues at the front . . . . . . . 134 Front
25.3.4. Optimum layout Layout for livestreaming . . . . . . . . . . 134 Livestreaming
26. Security Considerations . . . . . . . . . . . . . . . . . . . 135
27. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 135
27.1. Matroska Element IDs Registry . . . . . . . . . . . . . 136
27.2. Chapter Codec IDs Registry . . . . . . . . . . . . . . . 152
27.3. Track Types Registry
27.4. Tags Target Types Registry
27.5. Alpha Modes Registry
27.6. Content Encoding Scopes Registry
27.7. Content Encoding Types Registry
27.8. Compression Algorithms Registry
27.9. Encryption Algorithms Registry
27.10. AES Cipher Modes Registry
27.11. Stereo Modes Registry
27.12. Display Units Registry
27.13. Projection Types Registry
27.14. Track Plane Types Registry
27.15. Horizontal Chroma Sitings Registry
27.16. Vertical Chroma Sitings Registry
27.17. Color Ranges Registry
27.18. Media Types . . . . . . . . . . . . . . . . . . . . . . 153
27.3.1.
27.18.1. For files containing video tracks . . . . . . . . . 153
27.3.2. Files Containing Video Tracks
27.18.2. For files containing audio tracks Files Containing Audio Tracks with no video
tracks . . . . . . . . . . . . . . . . . . . . . . . 154
27.3.3. No Video
Tracks
27.18.3. For files containing Files Containing a stereoscopic video track . . 154 Stereoscopic Video Track
28. Annex A: References
28.1. Normative References
28.2. Informative References
Appendix A. Historic Deprecated Elements . . . . . . . . . . . . 155
28.1.
A.1. SilentTracks Element . . . . . . . . . . . . . . . . . . 155
28.2.
A.2. SilentTrackNumber Element . . . . . . . . . . . . . . . 156
28.3.
A.3. BlockVirtual Element . . . . . . . . . . . . . . . . . . 156
28.4.
A.4. ReferenceVirtual Element . . . . . . . . . . . . . . . . 156
28.5.
A.5. Slices Element . . . . . . . . . . . . . . . . . . . . . 156
28.6.
A.6. TimeSlice Element . . . . . . . . . . . . . . . . . . . 156
28.7.
A.7. LaceNumber Element . . . . . . . . . . . . . . . . . . . 156
28.8.
A.8. FrameNumber Element . . . . . . . . . . . . . . . . . . 157
28.9.
A.9. BlockAdditionID Element . . . . . . . . . . . . . . . . 157
28.10.
A.10. Delay Element . . . . . . . . . . . . . . . . . . . . . 157
28.11.
A.11. SliceDuration Element . . . . . . . . . . . . . . . . . 157
28.12.
A.12. ReferenceFrame Element . . . . . . . . . . . . . . . . . 157
28.13.
A.13. ReferenceOffset Element . . . . . . . . . . . . . . . . 157
28.14.
A.14. ReferenceTimestamp Element . . . . . . . . . . . . . . . 157
28.15.
A.15. EncryptedBlock Element . . . . . . . . . . . . . . . . . 158
28.16.
A.16. MinCache Element . . . . . . . . . . . . . . . . . . . . 158
28.17.
A.17. MaxCache Element . . . . . . . . . . . . . . . . . . . . 158
28.18.
A.18. TrackOffset Element . . . . . . . . . . . . . . . . . . 158
28.19.
A.19. CodecSettings Element . . . . . . . . . . . . . . . . . 158
28.20.
A.20. CodecInfoURL Element . . . . . . . . . . . . . . . . . . 158
28.21.
A.21. CodecDownloadURL Element . . . . . . . . . . . . . . . . 159
28.22.
A.22. CodecDecodeAll Element . . . . . . . . . . . . . . . . . 159
28.23.
A.23. TrackOverlay Element . . . . . . . . . . . . . . . . . . 159
28.24.
A.24. AspectRatioType Element . . . . . . . . . . . . . . . . 159
28.25.
A.25. GammaValue Element . . . . . . . . . . . . . . . . . . . 159
28.26.
A.26. FrameRate Element . . . . . . . . . . . . . . . . . . . 159
28.27.
A.27. ChannelPositions Element . . . . . . . . . . . . . . . . 160
28.28.
A.28. TrickTrackUID Element . . . . . . . . . . . . . . . . . 160
28.29.
A.29. TrickTrackSegmentUID Element . . . . . . . . . . . . . . 160
28.30.
A.30. TrickTrackFlag Element . . . . . . . . . . . . . . . . . 160
28.31.
A.31. TrickMasterTrackUID Element . . . . . . . . . . . . . . 160
28.32.
A.32. TrickMasterTrackSegmentUID Element . . . . . . . . . . . 160
28.33.
A.33. ContentSignature Element . . . . . . . . . . . . . . . . 161
28.34.
A.34. ContentSigKeyID Element . . . . . . . . . . . . . . . . 161
28.35.
A.35. ContentSigAlgo Element . . . . . . . . . . . . . . . . . 161
28.36.
A.36. ContentSigHashAlgo Element . . . . . . . . . . . . . . . 161
28.37.
A.37. CueRefCluster Element . . . . . . . . . . . . . . . . . 161
28.38.
A.38. CueRefNumber Element . . . . . . . . . . . . . . . . . . 161
28.39.
A.39. CueRefCodecState Element . . . . . . . . . . . . . . . . 161
28.40.
A.40. FileReferral Element . . . . . . . . . . . . . . . . . . 162
28.41.
A.41. FileUsedStartTime Element . . . . . . . . . . . . . . . 162
28.42.
A.42. FileUsedEndTime Element . . . . . . . . . . . . . . . . 162
28.43.
A.43. TagDefaultBogus Element . . . . . . . . . . . . . . . . 162
29. Normative References . . . . . . . . . . . . . . . . . . . . 162
30. Informative References . . . . . . . . . . . . . . . . . . . 164
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 166
1. Introduction
Matroska is an audiovisual data container format. It was derived
from a project called [MCF], [MCF] but diverges from it significantly
because it is based on EBML (Extensible Binary Meta Language)
[RFC8794], a binary derivative of XML. EBML provides significant
advantages in terms of future format extensibility, without breaking
file support in parsers reading the previous versions.
First,
To avoid any misunderstandings, it is essential to clarify exactly "What
what an Audio/Video audio/video container is", to avoid any misunderstandings: is:
* It is NOT a video or audio compression format (codec) (codec).
* It is an envelope in which there can be many audio, video, and
subtitles streams, allowing the user to store a complete movie or
CD in a single file.
Matroska is designed with the future in mind. It incorporates
features such as:
* Fast seeking in the file
* Chapter entries
* Full metadata (tags) support
* Selectable subtitle/audio/video streams
* Modularly expandable
* Error resilience (can recover playback even when the stream is
damaged)
* Streamable over the internet Internet and local networks (HTTP [RFC9110],
FTP [RFC0959], SMB [SMB-CIFS], etc.)
* Menus (like menus that DVDs have [DVD-Video])
2. Status of this document This Document
This document covers Matroska versions 1, 2, 3 3, and 4. Matroska v4
version 4 is the current version. Matroska versions 1 to 3 are no
longer maintained. No new elements are expected in files with
version numbers 1, 2, or 3.
3. Notation and Conventions
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP
14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here.
This document defines specific the following terms in order to define the
format and application of Matroska. Specific terms are defined below: Matroska:
Matroska: A multimedia container format based on EBML (Extensible
Binary Meta Language).
Matroska Reader: A data parser that interprets the semantics of a
Matroska document and creates a way for programs to use Matroska.
Matroska Player: A Matroska Reader with a the primary purpose of
playing audiovisual files, including Matroska documents.
Matroska Writer: A data writer that creates Matroska documents.
4. Matroska Overview
4.1. Principles
Matroska is a Document Type of EBML (Extensible Binary Meta
Language). EBML. This specification is dependent
on the EBML Specification specification [RFC8794]. For an understanding of
Matroska's EBML Schema, see in particular the sections of the EBML Specification covering
specification that cover EBML Element Types (Section 7), EBML Schema
(Section 11.1), and EBML Structure (Section 3).
4.2. Updates to RFC 8794
Because of an oversight, [RFC8794] reserved EBML ID 0x80, which is
used by deployed Matroska implementations. For this reason, this
specification updates [RFC8794] to make 0x80 a legal EBML ID.
Specifically,
Additionally, this specification makes the following are changed in [RFC8794]: updates:
* From Errata 7189
In Section 17.1, 17.1 of [RFC8794] (per Erratum ID #7189 [Err7189])
OLD:
| One-octet Element IDs MUST be between 0x81 and 0xFE. These items
| are valuable because they are short, and they need to be used for
| commonly repeated elements. Element IDs are to be allocated
| within this range according to the "RFC Required" policy
| [RFC8126].
|
| The following one-octet Element IDs are RESERVED: 0xFF and 0x80.
NEW:
| One-octet Element IDs MUST be between 0x80 and 0xFE. These items
| are valuable because they are short, and they need to be used for
| commonly repeated elements. Element IDs are to be allocated
| within this range according to the "RFC Required" policy
| [RFC8126].
|
| The following one-octet Element ID is RESERVED: 0xFF.
* From Errata 7191
In Section 5, 5 of [RFC8794] (per Erratum ID #7191 [Err7191])
OLD:
+=========================+================+=================+
| Element ID Octet Length | Range of Valid | Number of Valid |
| | Element IDs | Element IDs |
+=========================+================+=================+
| 1 | 0x81 - 0xFE | 126 |
+-------------------------+----------------+-----------------+
NEW:
+=========================+================+=================+
| Element ID Octet Length | Range of Valid | Number of Valid |
| | Element IDs | Element IDs |
+=========================+================+=================+
| 1 | 0x80 - 0xFE | 127 |
+-------------------------+----------------+-----------------+
4.3. Added EBML Constraints
As an EBML Document Type, Matroska adds the following constraints to
the EBML specification. specification [RFC8794]:
* The docType of the EBML Header MUST be "matroska".
* The EBMLMaxIDLength of the EBML Header MUST be 4.
* The EBMLMaxSizeLength of the EBML Header MUST be between 1 and 8 8,
inclusive.
4.4. Design Rules
The Root Element and all Top-Levels Top-Level Elements MUST use 4 octets for
their EBML Element ID -- i.e. i.e., Segment and direct children of
Segment.
Legacy EBML/Matroska parsers did not handle Empty Elements properly, properly;
elements were present in the file but with had a length of zero. 0. They always
assumed the value was 0 for integers/dates or 0x0p+0, the textual
expression of floats using the [ISO9899] format, format in [ISO9899], no matter the
default value of the element which that should have been used instead.
Therefore, Matroska writers Writers MUST NOT use EBML Empty Elements, Elements if the
element has a default value that is not 0 for integers/dates and
0x0p+0 for floats.
When adding new elements to Matroska, these rules apply:
* A non-mandatory integer/date Element MUST NOT have a default value
other than 0.
* A non-mandatory float Element MUST NOT have a default value other
than 0x0p+0.
* A non-mandatory string Element MUST NOT have a default value, as
empty string strings cannot be defined in the XML Schema.
4.5. Data Layout
A Matroska file MUST be composed of at least one EBML Document using
the Matroska Document Type. Each EBML Document MUST start with an
EBML Header and MUST be followed by the EBML Root Element, defined as
Segment in Matroska. Matroska defines several Top-Level Elements
which
that may occur within the Segment.
As an example, a simple Matroska file consisting of a single EBML
Document could be represented like this:
* EBML Header
* Segment
A more complex Matroska file consisting of an EBML Stream (consisting
of two EBML Documents) could be represented like this:
* EBML Header
* Segment
* EBML Header
* Segment
The following diagram represents a simple Matroska file, comprised of
an EBML Document with an EBML Header, a Segment Element element (the Root
Element), and all eight Matroska Top-Level Elements. In the
following diagrams of
in this section, horizontal spacing expresses a parent-child
relationship between Matroska Elements elements (e.g., the Info
Element element is
contained within the Segment Element) element), whereas vertical alignment
represents the storage order within the file.
+-------------+
| EBML Header |
+---------------------------+
| Segment | SeekHead |
| |-------------|
| | Info |
| |-------------|
| | Tracks |
| |-------------|
| | Chapters |
| |-------------|
| | Cluster |
| |-------------|
| | Cues |
| |-------------|
| | Attachments |
| |-------------|
| | Tags |
+---------------------------+
Figure 1: Basic layout Layout of a Matroska file. File
The Matroska EBML Schema defines eight Top-Level Elements:
* SeekHead (Section 6.3), 6.3)
* Info (Section 6.5), 6.5)
* Tracks (Section 18), 18)
* Chapters (Section 20), 20)
* Cluster (Section 10), 10)
* Cues (Section 22), 22)
* Attachments (Section 21), 21)
* and Tags (Section 6.8). 6.8)
The SeekHead Element element (also known as MetaSeek) contains an index of
Top-Level Elements locations within the Segment. Use of the SeekHead
Element
element is RECOMMENDED. Without a SeekHead Element, element, a Matroska
parser would have to search the entire file to find all of the other
Top-Level Elements. This is due to Matroska's flexible ordering
requirements; for instance, it is acceptable for the Chapters Element element
to be stored after the Cluster Elements. element(s).
+--------------------------------+
| SeekHead | Seek | SeekID |
| | |--------------|
| | | SeekPosition |
+--------------------------------+
Figure 2: Representation of a SeekHead Element. Element
The Info Element element contains vital information for identifying the whole
Segment. This includes the title for the Segment, a randomly
generated unique identifier, identifier (UID), and the unique identifier(s) UID(s) of any linked
Segment Elements. elements.
+-------------------------+
| Info | SegmentUUID |
| |------------------|
| | SegmentFilename |
| |------------------|
| | PrevUUID |
| |------------------|
| | PrevFilename |
| |------------------|
| | NextUUID |
| |------------------|
| | NextFilename |
| |------------------|
| | SegmentFamily |
| |------------------|
| | ChapterTranslate |
| |------------------|
| | TimestampScale |
| |------------------|
| | Duration |
| |------------------|
| | DateUTC |
| |------------------|
| | Title |
| |------------------|
| | MuxingApp |
| |------------------|
| | WritingApp |
|-------------------------|
Figure 3: Representation of an Info Element and its Its Child Elements. Elements
The Tracks Element element defines the technical details for each track and
can store the name, number, unique identifier, UID, language, and type (audio, video,
subtitles, etc.) of each track. For example, the Tracks Element element MAY
store information about the resolution of a video track or sample
rate of an audio track.
The Tracks Element element MUST identify all the data needed by the codec to
decode the data of the specified track. However, the data required
is contingent on the codec used for the track. For example, a Track
Element
element for uncompressed audio only requires the audio bit rate to be
present. A codec such as AC-3 would require that the CodecID Element element
be present for all tracks, as it is the primary way to identify which
codec to use to decode the track.
+------------------------------------+
| Tracks | TrackEntry | TrackNumber |
| | |--------------|
| | | TrackUID |
| | |--------------|
| | | TrackType |
| | |--------------|
| | | Name |
| | |--------------|
| | | Language |
| | |--------------|
| | | CodecID |
| | |--------------|
| | | CodecPrivate |
| | |--------------|
| | | CodecName |
| | |----------------------------------+
| | | Video | FlagInterlaced |
| | | |-------------------|
| | | | FieldOrder |
| | | |-------------------|
| | | | StereoMode |
| | | |-------------------|
| | | | AlphaMode |
| | | |-------------------|
| | | | PixelWidth |
| | | |-------------------|
| | | | PixelHeight |
| | | |-------------------|
| | | | DisplayWidth |
| | | |-------------------|
| | | | DisplayHeight |
| | | |-------------------|
| | | | AspectRatioType |
| | | |-------------------|
| | | | Color Colour |
| | |----------------------------------|
| | | Audio | SamplingFrequency |
| | | |-------------------|
| | | | Channels |
| | | |-------------------|
| | | | BitDepth |
|--------------------------------------------------------|
Figure 4: Representation of the Tracks Element and a selection Selection of its Its
Descendant Elements. Elements
The Chapters Element element lists all of the chapters. Chapters are a way
to set predefined points to jump to in video or audio.
+-----------------------------------------+
| Chapters | Edition | EditionUID |
| | Entry |--------------------|
| | | EditionFlagDefault |
| | |--------------------|
| | | EditionFlagOrdered |
| | |---------------------------------+
| | | ChapterAtom | ChapterUID |
| | | |-------------------|
| | | | ChapterStringUID |
| | | |-------------------|
| | | | ChapterTimeStart |
| | | |-------------------|
| | | | ChapterTimeEnd |
| | | |-------------------|
| | | | ChapterFlagHidden |
| | | |-------------------------------+
| | | | ChapterDisplay | ChapString |
| | | | |--------------|
| | | | | ChapLanguage |
+------------------------------------------------------------------+
Figure 5: Representation of the Chapters Element and a selection Selection
of its Its Descendant Elements.
Cluster Elements
Cluster elements contain the content for each track, e.g., video
frames. A Matroska file SHOULD contain at least one Cluster Element. element.
In the rare case it doesn't, there should be a form of Segment
linking with other Segments, method for Segments to
link together, possibly using Chapters, Chapters; see Section 17.
The Cluster Element element helps to break up SimpleBlock or BlockGroup
Elements
elements and helps with seeking and error protection. Every Cluster
Element
element MUST contain a Timestamp Element. element. This SHOULD be the
Timestamp Element element used to play the first Block in the Cluster
Element,
element, unless a different value is needed to accommodate for more
Blocks,
Blocks; see Section 11.2.
Cluster Elements elements contain one or more block Block element, such as
BlockGroup or SimpleBlock elements. In some situations, a Cluster
Element
element MAY contain no block Block element, for example example, in a live
recording when no data has been collected.
A BlockGroup Element element MAY contain a Block of data and any information
relating directly to that Block.
+--------------------------+
| Cluster | Timestamp |
| |----------------|
| | Position |
| |----------------|
| | PrevSize |
| |----------------|
| | SimpleBlock |
| |----------------|
| | BlockGroup |
+--------------------------+
Figure 6: Representation of a Cluster Element and its immediate Its Immediate
Child Elements. Elements
+----------------------------------+
| Block | Portion of | Data Type |
| | a Block | - Bit Flag |
| |--------------------------+
| | Header | TrackNumber |
| | |-------------|
| | | Timestamp |
| | |-------------|
| | | Flags |
| | | - Gap |
| | | - Lacing |
| | | - Reserved |
| |--------------------------|
| | Optional | FrameSize |
| |--------------------------|
| | Data | Frame |
+----------------------------------+
Figure 7: Representation of the Block Element structure. Structure
Each Cluster MUST contain exactly one Timestamp Element. element. The
Timestamp Element element value MUST be stored once per Cluster. The
Timestamp Element element in the Cluster is relative to the entire Segment.
The Timestamp Element element SHOULD be the first Element element in the Cluster it
belongs to, to or the second Element element if that Cluster contains a CRC-32
element (Section 6.2) 6.2).
Additionally, the Block contains an offset that, when added to the
Cluster's Timestamp Element element value, yields the Block's effective
timestamp. Therefore, the timestamp in the Block itself is relative
to the Timestamp Element element in the Cluster. For example, if the
Timestamp
Element element in the Cluster is set to 10 seconds and a Block in
that Cluster is supposed to be played 12 seconds into the clip, the
timestamp in the Block would be set to 2 seconds.
The ReferenceBlock in the BlockGroup is used instead of the basic
"P-frame"/"B-frame" description. Instead of simply saying that this
Block depends on the Block directly before, before or directly afterwards, after, the
Timestamp of the necessary Block is used. Because there can be as
many ReferenceBlock Elements elements as necessary for a Block, it allows for
some extremely complex referencing.
The Cues Element element is used to seek when playing back a file by
providing a temporal index for some of the Tracks. It is similar to
the SeekHead Element, element but is used for seeking to a specific time when
playing back the file. It is possible to seek without this element,
but it is much more difficult because a Matroska Reader would have to
'hunt
"hunt and peck' peck" through the file looking to look for the correct timestamp.
The Cues Element element SHOULD contain at least one CuePoint Element. element. Each
CuePoint Element element stores the position of the Cluster that contains the
BlockGroup or SimpleBlock Element. element. The timestamp is stored in the
CueTime Element element, and the location is stored in the CueTrackPositions
Element.
element.
The Cues Element element is flexible. For instance, the Cues Element element can be
used to index every single timestamp of every Block or they can be
indexed selectively.
+-------------------------------------+
| Cues | CuePoint | CueTime |
| | |-------------------|
| | | CueTrackPositions |
| |------------------------------|
| | CuePoint | CueTime |
| | |-------------------|
| | | CueTrackPositions |
+-------------------------------------+
Figure 8: Representation of a Cues Element and two levels Two Levels of its Its
Descendant Elements. Elements
The Attachments Element element is for attaching files to a Matroska file file,
such as pictures, fonts, webpages, web pages, etc.
+------------------------------------------------+
| Attachments | AttachedFile | FileDescription |
| | |-------------------|
| | | FileName |
| | |-------------------|
| | | FileMediaType |
| | |-------------------|
| | | FileData |
| | |-------------------|
| | | FileUID |
| | |-------------------|
| | | FileName |
| | |-------------------|
| | | FileReferral |
| | |-------------------|
| | | FileUsedStartTime |
| | |-------------------|
| | | FileUsedEndTime |
+------------------------------------------------+
Figure 9: Representation of an Attachments Element. Element
The Tags Element element contains metadata that describes the Segment and
potentially its Tracks, Chapters, and Attachments. Each Track or
Chapter that those tags applies to has its UID listed in the Tags.
The Tags contain all extra information about the file: scriptwriter,
singer, scriptwriters,
singers, actors, directors, titles, edition, price, dates, genre,
comments, etc. Tags can contain their values in multiple languages.
For example, a movie's "title" Tag "TITLE" tag value might contain both the
original English title as well as the title it was released as in Germany. German title.
+-------------------------------------------+
| Tags | Tag | Targets | TargetTypeValue |
| | | |------------------|
| | | | TargetType |
| | | |------------------|
| | | | TagTrackUID |
| | | |------------------|
| | | | TagEditionUID |
| | | |------------------|
| | | | TagChapterUID |
| | | |------------------|
| | | | TagAttachmentUID |
| | |------------------------------|
| | | SimpleTag | TagName |
| | | |------------------|
| | | | TagLanguage |
| | | |------------------|
| | | | TagDefault |
| | | |------------------|
| | | | TagString |
| | | |------------------|
| | | | TagBinary |
| | | |------------------|
| | | | SimpleTag |
+-------------------------------------------+
Figure 10: Representation of a Tags Element and three levels Three Levels of
its
Its Children Elements. Elements
5. Matroska Schema
This specification includes an EBML Schema, which Schema that defines the
Elements elements
and structure of Matroska using the EBML Schema elements and
attributes defined in Section 11.1 of [RFC8794]. The EBML Schema
defines every valid Matroska element in a manner defined by the EBML
specification.
Attributes using their default value like (like minOccurs, minver, etc. etc.)
or attributes with undefined values like (like length, maxver, etc. etc.) are
omitted.
Here the definition of
The definitions for each Matroska Element is provided. element are provided below.
5.1. Segment Element
id / type: 0x18538067 / master
unknownsizeallowed: True
path: \Segment
minOccurs / maxOccurs: 1 / 1
definition: The Root Element that contains all other Top-Level
Elements; see Section 4.5.
5.1.1. SeekHead Element
id / type: 0x114D9B74 / master
path: \Segment\SeekHead
maxOccurs: 2
definition: Contains seeking information of Top-Level Elements; see
Section 4.5.
5.1.1.1. Seek Element
id / type: 0x4DBB / master
path: \Segment\SeekHead\Seek
minOccurs: 1
definition: Contains a single seek entry to an EBML Element.
5.1.1.1.1. SeekID Element
id / type: 0x53AB / binary
length: 4
path: \Segment\SeekHead\Seek\SeekID
minOccurs / maxOccurs: 1 / 1
definition: The binary EBML ID of a Top-Level Element.
5.1.1.1.2. SeekPosition Element
id / type: 0x53AC / uinteger
path: \Segment\SeekHead\Seek\SeekPosition
minOccurs / maxOccurs: 1 / 1
definition: The Segment Position (Section 16) of a Top-Level
Element.
5.1.2. Info Element
id / type: 0x1549A966 / master
path: \Segment\Info
minOccurs / maxOccurs: 1 / 1
recurring: True
definition: Contains general information about the Segment.
5.1.2.1. SegmentUUID Element
id / type: 0x73A4 / binary
length: 16
path: \Segment\Info\SegmentUUID
maxOccurs: 1
definition: A randomly generated unique ID to identify UID that identifies the Segment
amongst many others (128 bits). It is equivalent to a UUID Universally
Unique Identifier (UUID) v4 [RFC4122] with all bits randomly (or pseudo-randomly)
pseudorandomly) chosen. An actual UUID v4 value, where some bits
are not random, MAY also be used.
usage notes: If the Segment is a part of a Linked Segment, then this
Element
element is REQUIRED. The value of the unique ID UID MUST contain at least
one bit set to 1.
5.1.2.2. SegmentFilename Element
id / type: 0x7384 / utf-8
path: \Segment\Info\SegmentFilename
maxOccurs: 1
definition: A filename corresponding to this Segment.
5.1.2.3. PrevUUID Element
id / type: 0x3CB923 / binary
length: 16
path: \Segment\Info\PrevUUID
maxOccurs: 1
definition: An ID to identify that identifies the previous Segment of a Linked
Segment.
usage notes: If the Segment is a part of a Linked Segment that uses
Hard Linking (Section 17.1), then either the PrevUUID or the
NextUUID Element element is REQUIRED. If a Segment contains a PrevUUID
but not a NextUUID, then it MAY be considered as the last Segment
of the Linked Segment. The PrevUUID MUST NOT be equal to the
SegmentUUID.
5.1.2.4. PrevFilename Element
id / type: 0x3C83AB / utf-8
path: \Segment\Info\PrevFilename
maxOccurs: 1
definition: A filename corresponding to the file of the previous
Linked Segment.
usage notes: Provision of the previous filename is for display
convenience, but PrevUUID SHOULD be considered authoritative for
identifying the previous Segment in a Linked Segment.
5.1.2.5. NextUUID Element
id / type: 0x3EB923 / binary
length: 16
path: \Segment\Info\NextUUID
maxOccurs: 1
definition: An ID to identify that identifies the next Segment of a Linked
Segment.
usage notes: If the Segment is a part of a Linked Segment that uses
Hard Linking (Section 17.1), then either the PrevUUID or the
NextUUID Element element is REQUIRED. If a Segment contains a NextUUID
but not a PrevUUID, then it MAY be considered as the first Segment
of the Linked Segment. The NextUUID MUST NOT be equal to the
SegmentUUID.
5.1.2.6. NextFilename Element
id / type: 0x3E83BB / utf-8
path: \Segment\Info\NextFilename
maxOccurs: 1
definition: A filename corresponding to the file of the next Linked
Segment.
usage notes: Provision of the next filename is for display
convenience, but NextUUID SHOULD be considered authoritative for
identifying the Next Segment.
5.1.2.7. SegmentFamily Element
id / type: 0x4444 / binary
length: 16
path: \Segment\Info\SegmentFamily
definition: A unique ID UID that all Segments of a Linked Segment MUST share
(128 bits). It is equivalent to a UUID v4 [RFC4122] with all bits
randomly (or pseudo-randomly) pseudorandomly) chosen. An actual UUID v4 value,
where some bits are not random, MAY also be used.
usage notes: If the Segment Info contains a ChapterTranslate
element, this Element element is REQUIRED.
5.1.2.8. ChapterTranslate Element
id / type: 0x6924 / master
path: \Segment\Info\ChapterTranslate
definition: The mapping between this Segment and a segment value in
the given Chapter Codec.
rationale: Chapter Codec Codecs may need to address different segments,
but they may not know of the way to identify such segment segments when
stored in Matroska. This element and its child elements add a way
to map the internal segments known to the Chapter Codec to the Segment
IDs
SegmentUUIDs in Matroska. This allows remuxing a file with
Chapter Codec without changing the content of the codec data, just
the Segment mapping.
5.1.2.8.1. ChapterTranslateID Element
id / type: 0x69A5 / binary
path: \Segment\Info\ChapterTranslate\ChapterTranslateID
minOccurs / maxOccurs: 1 / 1
definition: The binary value used to represent this Segment in the
chapter codec data. The format depends on the ChapProcessCodecID
used; see Section 5.1.7.1.4.15.
5.1.2.8.2. ChapterTranslateCodec Element
id / type: 0x69BF / uinteger
path: \Segment\Info\ChapterTranslate\ChapterTranslateCodec
minOccurs / maxOccurs: 1 / 1
definition: This ChapterTranslate applies Applies to this the chapter codec of the given chapter
edition(s); see Section 5.1.7.1.4.15.
defined values: See Table 1. Additional values can be registered in
the "Matroska Chapter Codec IDs" registry defined in Section 27.2.
+=======+=================+============================+
| value | label | definition |
+=======+=================+============================+
| 0 | Matroska Script | Chapter commands using the |
| | | Matroska Script codec. |
+-------+-----------------+----------------------------+
| 1 | DVD-menu | Chapter commands using the |
| | | DVD-like codec. |
+-------+-----------------+----------------------------+
Table 1: ChapterTranslateCodec values Values
5.1.2.8.3. ChapterTranslateEditionUID Element
id / type: 0x69FC / uinteger
path: \Segment\Info\ChapterTranslate\ChapterTranslateEditionUID
definition: Specify Specifies a chapter edition UID on to which this
ChapterTranslate applies.
usage notes: When no ChapterTranslateEditionUID is specified in the
ChapterTranslate, the ChapterTranslate applies to all chapter
editions found in the Segment using the given
ChapterTranslateCodec.
5.1.2.9. TimestampScale Element
id / type / default: 0x2AD7B1 / uinteger / 1000000
range: not 0
path: \Segment\Info\TimestampScale
minOccurs / maxOccurs: 1 / 1
definition: Base unit for Segment Ticks and Track Ticks, in
nanoseconds. A TimestampScale value of 1000000 means scaled
timestamps in the Segment are expressed in milliseconds; see
Section 11 on how to interpret timestamps.
5.1.2.10. Duration Element
id / type: 0x4489 / float
range: > 0x0p+0
path: \Segment\Info\Duration
maxOccurs: 1
definition: Duration of the Segment, expressed in Segment Ticks Ticks,
which is are based on TimestampScale; see Section 11.1.
5.1.2.11. DateUTC Element
id / type: 0x4461 / date
path: \Segment\Info\DateUTC
maxOccurs: 1
definition: The date and time that the Segment was created by the
muxing application or library.
5.1.2.12. Title Element
id / type: 0x7BA9 / utf-8
path: \Segment\Info\Title
maxOccurs: 1
definition: General name of the Segment.
5.1.2.13. MuxingApp Element
id / type: 0x4D80 / utf-8
path: \Segment\Info\MuxingApp
minOccurs / maxOccurs: 1 / 1
definition: Muxing application or library (example: "libmatroska-
0.4.3").
usage notes: Include the full name of the application or library
followed by the version number.
5.1.2.14. WritingApp Element
id / type: 0x5741 / utf-8
path: \Segment\Info\WritingApp
minOccurs / maxOccurs: 1 / 1
definition: Writing application (example: "mkvmerge-0.3.3").
usage notes: Include the full name of the application followed by
the version number.
5.1.3. Cluster Element
id / type: 0x1F43B675 / master
unknownsizeallowed: True
path: \Segment\Cluster
definition: The Top-Level Element containing the (monolithic) Block
structure.
5.1.3.1. Timestamp Element
id / type: 0xE7 / uinteger
path: \Segment\Cluster\Timestamp
minOccurs / maxOccurs: 1 / 1
definition: Absolute timestamp of the cluster, expressed in Segment
Ticks
Ticks, which is are based on TimestampScale; see Section 11.1.
usage notes: This element SHOULD be the first child element of the
Cluster it belongs to, to or the second if that Cluster contains a
CRC-32 element (Section 6.2).
5.1.3.2. Position Element
id / type: 0xA7 / uinteger
path: \Segment\Cluster\Position
maxOccurs: 1
maxver: 4
definition: The Segment Position of the Cluster in the Segment (0 in
live streams). It might help to resynchronise resynchronize the offset on
damaged streams.
5.1.3.3. PrevSize Element
id / type: 0xAB / uinteger
path: \Segment\Cluster\PrevSize
maxOccurs: 1
definition: Size of the previous Cluster, in octets. Can be useful
for backward playing.
5.1.3.4. SimpleBlock Element
id / type: 0xA3 / binary
path: \Segment\Cluster\SimpleBlock
minver: 2
definition: Similar to Block, see Block (see Section 10.1, 10.1) but without all the
extra information, mostly information. Mostly used to reduced reduce overhead when no extra
feature is needed; see Section 10.2 on SimpleBlock Structure.
5.1.3.5. BlockGroup Element
id / type: 0xA0 / master
path: \Segment\Cluster\BlockGroup
definition: Basic container of information containing a single Block
and information specific to that Block.
5.1.3.5.1. Block Element
id / type: 0xA1 / binary
path: \Segment\Cluster\BlockGroup\Block
minOccurs / maxOccurs: 1 / 1
definition: Block containing the actual data to be rendered and a
timestamp relative to the Cluster Timestamp; see Section 10.1 on
Block Structure.
5.1.3.5.2. BlockAdditions Element
id / type: 0x75A1 / master
path: \Segment\Cluster\BlockGroup\BlockAdditions
maxOccurs: 1
definition: Contain Contains additional binary data to complete the main one; Block
element; see Codec BlockAdditions section Section 4.1.5 of [MatroskaCodec] for more
information. An EBML parser that has no knowledge of the Block
structure could still see and use/skip these data.
5.1.3.5.2.1. BlockMore Element
id / type: 0xA6 / master
path: \Segment\Cluster\BlockGroup\BlockAdditions\BlockMore
minOccurs: 1
definition: Contain Contains the BlockAdditional and some parameters.
5.1.3.5.2.2. BlockAdditional Element
id / type: 0xA5 / binary
path: \Segment\Cluster\BlockGroup\BlockAdditions\BlockMore\BlockAddi
tional
minOccurs / maxOccurs: 1 / 1
definition: Interpreted by the codec as it wishes (using the
BlockAddID).
5.1.3.5.2.3. BlockAddID Element
id / type / default: 0xEE / uinteger / 1
range: not 0
path: \Segment\Cluster\BlockGroup\BlockAdditions\BlockMore\BlockAddI
D
minOccurs / maxOccurs: 1 / 1
definition: An ID to identify that identifies how to interpret the
BlockAdditional data; see Codec BlockAdditions section Section 4.1.5 of [MatroskaCodec] for
more information. A value of 1 indicates that the meaning of the BlockAdditional
data is defined by the codec. Any other value indicates the meaning of that the
BlockAdditional data is found in should be handled according to the
BlockAddIDType found that is located in the TrackEntry.
usage notes: Each BlockAddID value MUST be unique between all
BlockMore elements found in a BlockAdditions.
usage notes: BlockAdditions element. To keep
MaxBlockAdditionID as low as possible, small values SHOULD be
used.
5.1.3.5.3. BlockDuration Element
id / type: 0x9B / uinteger
path: \Segment\Cluster\BlockGroup\BlockDuration
minOccurs / maxOccurs: see implementation notes See Table 2 / 1
definition: The duration of the Block, expressed in Track Ticks; see
Section 11.1. The BlockDuration Element element can be useful at the end
of a Track to define the duration of the last frame (as there is
no subsequent Block available), available) or when there is a break in a track
like for subtitle tracks.
notes:
+===========+===================================================+ See Table 2.
+===========+==================================================+
| attribute | note |
+===========+===================================================+
+===========+==================================================+
| minOccurs | BlockDuration MUST be set (minOccurs=1) if the |
| | associated TrackEntry stores a DefaultDuration |
| | value. |
+-----------+---------------------------------------------------+
+-----------+--------------------------------------------------+
| default | When If a value is not written present and with no DefaultDuration, the DefaultDuration |
| | is defined, the value is assumed to be the difference between the |
| | difference between the timestamp of this Block |
| | and the timestamp of the |
| | next Block in "display" |
| | order (not coding order). |
+-----------+---------------------------------------------------+
+-----------+--------------------------------------------------+
Table 2: BlockDuration implementation notes Implementation Notes
5.1.3.5.4. ReferencePriority Element
id / type / default: 0xFA / uinteger / 0
path: \Segment\Cluster\BlockGroup\ReferencePriority
minOccurs / maxOccurs: 1 / 1
definition: This frame is referenced and has the specified cache
priority. In cache the cache, only a frame of the same or higher
priority can replace this frame. A value of 0 means the frame is
not referenced.
5.1.3.5.5. ReferenceBlock Element
id / type: 0xFB / integer
path: \Segment\Cluster\BlockGroup\ReferenceBlock
definition: A timestamp value, relative to the timestamp of the
Block in this BlockGroup, expressed in Track Ticks; see
Section 11.1. This is used to reference other frames necessary to
decode this frame. The relative value SHOULD correspond to a
valid Block that this Block depends on. Historically Historically, Matroska Writer
Writers didn't write the actual Block(s) that this Block depends
on, but they did write _some_
Block Block(s) in the past.
The value "0" MAY also be used to signify that this Block cannot be
decoded on its own, but without knownledge of which Block the necessary reference Block(s) is
necessary. unknown.
In this case, other ReferenceBlock elements MUST NOT be found in the
same BlockGroup. If the BlockGroup doesn't have any a ReferenceBlock
element, then the Block it contains can be decoded without using any
other Block data.
5.1.3.5.6. CodecState Element
id / type: 0xA4 / binary
path: \Segment\Cluster\BlockGroup\CodecState
maxOccurs: 1
minver: 2
definition: The new codec state to use. Data interpretation is
private to the codec. This information SHOULD always be
referenced by a seek entry.
5.1.3.5.7. DiscardPadding Element
id / type: 0x75A2 / integer
path: \Segment\Cluster\BlockGroup\DiscardPadding
maxOccurs: 1
minver: 4
definition: Duration of the silent data added to the Block,
expressed in Matroska Ticks -- i.e., in nanoseconds; see
Section 11.1 (padding at the end of the Block for positive value, values
and at the beginning of the Block for negative value). values). The
duration of DiscardPadding is not calculated in the duration of
the TrackEntry and SHOULD be discarded during playback.
5.1.4. Tracks Element
id / type: 0x1654AE6B / master
path: \Segment\Tracks
maxOccurs: 1
recurring: True
definition: A Top-Level Element of information with many tracks
described.
5.1.4.1. TrackEntry Element
id / type: 0xAE / master
path: \Segment\Tracks\TrackEntry
minOccurs: 1
definition: Describes a track with all Elements. elements.
5.1.4.1.1. TrackNumber Element
id / type: 0xD7 / uinteger
range: not 0
path: \Segment\Tracks\TrackEntry\TrackNumber
minOccurs / maxOccurs: 1 / 1
definition: The track number as used in the Block Header.
5.1.4.1.2. TrackUID Element
id / type: 0x73C5 / uinteger
range: not 0
path: \Segment\Tracks\TrackEntry\TrackUID
minOccurs / maxOccurs: 1 / 1
definition: A unique ID to identify UID that identifies the Track.
stream copy: True (Section 8)
5.1.4.1.3. TrackType Element
id / type: 0x83 / uinteger
path: \Segment\Tracks\TrackEntry\TrackType
minOccurs / maxOccurs: 1 / 1
definition: The TrackType defines the type of each frame found in
the Track. The value SHOULD be stored on 1 octet.
defined values: See Table 3. Additional values can be registered in
the "Track Types" registry defined in Section 27.3.
stream copy: True (Section 8)
+=======+==========+==========================================+
| value | label | contents of each frame contains |
+=======+==========+==========================================+
| 1 | video | An image. |
+-------+----------+------------------------------------------+
| 2 | audio | Audio samples. |
+-------+----------+------------------------------------------+
| 3 | complex | A mix of different other TrackType. The |
| | | codec needs to define how the Matroska |
| | | Player should interpret such data. |
+-------+----------+------------------------------------------+
| 16 | logo | An image to be rendered over the video |
| | | track(s). |
+-------+----------+------------------------------------------+
| 17 | subtitle | Subtitle or closed caption data to be |
| | | rendered over the video track(s). |
+-------+----------+------------------------------------------+
| 18 | buttons | Interactive button(s) to be rendered |
| | | over the video track(s). |
+-------+----------+------------------------------------------+
| 32 | control | Metadata used to control the player of |
| | | the Matroska Player. |
+-------+----------+------------------------------------------+
| 33 | metadata | Timed metadata that can be passed on to |
| | | the Matroska Player. |
+-------+----------+------------------------------------------+
Table 3: TrackType values Values
5.1.4.1.4. FlagEnabled Element
id / type / default: 0xB9 / uinteger / 1
range: 0-1
path: \Segment\Tracks\TrackEntry\FlagEnabled
minOccurs / maxOccurs: 1 / 1
minver: 2
definition: Set to 1 if the track is usable. It is possible to turn
a track that is not usable track into a usable track using chapter
codecs or control tracks.
5.1.4.1.5. FlagDefault Element
id / type / default: 0x88 / uinteger / 1
range: 0-1
path: \Segment\Tracks\TrackEntry\FlagDefault
minOccurs / maxOccurs: 1 / 1
definition: Set to 1 if that the track (audio, video video, or subs) subtitles) is
eligible for automatic selection by the player; see Section 19 for
more details.
5.1.4.1.6. FlagForced Element
id / type / default: 0x55AA / uinteger / 0
range: 0-1
path: \Segment\Tracks\TrackEntry\FlagForced
minOccurs / maxOccurs: 1 / 1
definition: Applies only to subtitles. Set to 1 if that the track is
eligible for automatic selection by the player if it matches the
user's language preference, even if the user's preferences would
normally
not normally enable subtitles with the selected audio track; this
can be used for tracks containing only translations of foreign-
language audio in
foreign languages or onscreen on-screen text. See Section 19 for more
details.
5.1.4.1.7. FlagHearingImpaired Element
id / type: 0x55AB / uinteger
range: 0-1
path: \Segment\Tracks\TrackEntry\FlagHearingImpaired
maxOccurs: 1
minver: 4
definition: Set to 1 if and only if that the track is suitable for users
with hearing impairments.
5.1.4.1.8. FlagVisualImpaired Element
id / type: 0x55AC / uinteger
range: 0-1
path: \Segment\Tracks\TrackEntry\FlagVisualImpaired
maxOccurs: 1
minver: 4
definition: Set to 1 if and only if that the track is suitable for users
with visual impairments.
5.1.4.1.9. FlagTextDescriptions Element
id / type: 0x55AD / uinteger
range: 0-1
path: \Segment\Tracks\TrackEntry\FlagTextDescriptions
maxOccurs: 1
minver: 4
definition: Set to 1 if and only if that the track contains textual
descriptions of video content.
5.1.4.1.10. FlagOriginal Element
id / type: 0x55AE / uinteger
range: 0-1
path: \Segment\Tracks\TrackEntry\FlagOriginal
maxOccurs: 1
minver: 4
definition: Set to 1 if and only if that the track is in the content's
original language.
5.1.4.1.11. FlagCommentary Element
id / type: 0x55AF / uinteger
range: 0-1
path: \Segment\Tracks\TrackEntry\FlagCommentary
maxOccurs: 1
minver: 4
definition: Set to 1 if and only if that the track contains commentary.
5.1.4.1.12. FlagLacing Element
id / type / default: 0x9C / uinteger / 1
range: 0-1
path: \Segment\Tracks\TrackEntry\FlagLacing
minOccurs / maxOccurs: 1 / 1
definition: Set to 1 if the track MAY contain blocks using that use
lacing. When set to 0 0, all blocks MUST have their lacing flags
set to No
lacing; "no lacing"; see Section 10.3 on Block 'Block' Lacing.
5.1.4.1.13. DefaultDuration Element
id / type: 0x23E383 / uinteger
range: not 0
path: \Segment\Tracks\TrackEntry\DefaultDuration
maxOccurs: 1
definition: Number of nanoseconds per frame, expressed in Matroska
Ticks -- i.e., in nanoseconds; see Section 11.1 (frame ("frame" in the
Matroska sense -- one Element element put into a (Simple)Block).
stream copy: True (Section 8)
5.1.4.1.14. DefaultDecodedFieldDuration Element
id / type: 0x234E7A / uinteger
range: not 0
path: \Segment\Tracks\TrackEntry\DefaultDecodedFieldDuration
maxOccurs: 1
minver: 4
definition: The period between two successive fields at the output
of the decoding process, expressed in Matroska Ticks -- i.e., in
nanoseconds; see Section 11.1. see See Section 9 for more information
information.
stream copy: True (Section 8)
5.1.4.1.15. TrackTimestampScale Element
id / type / default: 0x23314F / float / 0x1p+0
range: > 0x0p+0
path: \Segment\Tracks\TrackEntry\TrackTimestampScale
minOccurs / maxOccurs: 1 / 1
maxver: 3
definition: The scale to apply on this track to work at normal speed
in relation with other tracks (mostly used to adjust video speed
when the audio length differs).
stream copy: True (Section 8)
5.1.4.1.16. MaxBlockAdditionID Element
id / type / default: 0x55EE / uinteger / 0
path: \Segment\Tracks\TrackEntry\MaxBlockAdditionID
minOccurs / maxOccurs: 1 / 1
definition: The maximum value of BlockAddID (Section 5.1.3.5.2.3).
A value of 0 means there is no BlockAdditions (Section 5.1.3.5.2)
for this track.
5.1.4.1.17. BlockAdditionMapping Element
id / type: 0x41E4 / master
path: \Segment\Tracks\TrackEntry\BlockAdditionMapping
minver: 4
definition: Contains elements that extend the track format, format by adding
content either to each frame, with BlockAddID
(Section 5.1.3.5.2.3), or to the track as a whole with
BlockAddIDExtraData.
5.1.4.1.17.1. BlockAddIDValue Element
id / type: 0x41F0 / uinteger
range: >=2
path: \Segment\Tracks\TrackEntry\BlockAdditionMapping\BlockAddIDValu
e
maxOccurs: 1
minver: 4
definition: If the track format extension needs content beside
frames, the value refers to the BlockAddID (Section 5.1.3.5.2.3), 5.1.3.5.2.3)
value being described.
usage notes: To keep MaxBlockAdditionID as low as possible, small
values SHOULD be used.
5.1.4.1.17.2. BlockAddIDName Element
id / type: 0x41A4 / string
path: \Segment\Tracks\TrackEntry\BlockAdditionMapping\BlockAddIDName
maxOccurs: 1
minver: 4
definition: A human-friendly name describing the type of
BlockAdditional data, as defined by the associated Block
Additional Mapping.
5.1.4.1.17.3. BlockAddIDType Element
id / type / default: 0x41E7 / uinteger / 0
path: \Segment\Tracks\TrackEntry\BlockAdditionMapping\BlockAddIDType
minOccurs / maxOccurs: 1 / 1
minver: 4
definition: Stores the registered identifier of the Block Additional
Mapping to define how the BlockAdditional data should be handled.
usage notes: If BlockAddIDType is 0, the BlockAddIDValue and
corresponding BlockAddID values MUST be 1.
5.1.4.1.17.4. BlockAddIDExtraData Element
id / type: 0x41ED / binary
path: \Segment\Tracks\TrackEntry\BlockAdditionMapping\BlockAddIDExtr
aData
maxOccurs: 1
minver: 4
definition: Extra binary data that the BlockAddIDType can use to
interpret the BlockAdditional data. The interpretation of the
binary data depends on the BlockAddIDType value and the
corresponding Block Additional Mapping.
5.1.4.1.18. Name Element
id / type: 0x536E / utf-8
path: \Segment\Tracks\TrackEntry\Name
maxOccurs: 1
definition: A human-readable track name.
5.1.4.1.19. Language Element
id / type / default: 0x22B59C / string / eng
path: \Segment\Tracks\TrackEntry\Language
minOccurs / maxOccurs: 1 / 1
definition: The language of the track, in the Matroska languages
form; see Section 12 on language codes. This Element element MUST be
ignored if the LanguageBCP47 Element element is used in the same
TrackEntry.
5.1.4.1.20. LanguageBCP47 Element
id / type: 0x22B59D / string
path: \Segment\Tracks\TrackEntry\LanguageBCP47
maxOccurs: 1
minver: 4
definition: The language of the track, in the [BCP47] form; form defined in
[RFC5646]; see Section 12 on language codes. If this Element element is
used, then any Language Elements elements used in the same TrackEntry MUST
be ignored.
5.1.4.1.21. CodecID Element
id / type: 0x86 / string
path: \Segment\Tracks\TrackEntry\CodecID
minOccurs / maxOccurs: 1 / 1
definition: An ID corresponding to the codec, codec; see [MatroskaCodec]
for more info.
stream copy: True (Section 8)
5.1.4.1.22. CodecPrivate Element
id / type: 0x63A2 / binary
path: \Segment\Tracks\TrackEntry\CodecPrivate
maxOccurs: 1
definition: Private data only known to the codec.
stream copy: True (Section 8)
5.1.4.1.23. CodecName Element
id / type: 0x258688 / utf-8
path: \Segment\Tracks\TrackEntry\CodecName
maxOccurs: 1
definition: A human-readable string specifying the codec.
5.1.4.1.24. AttachmentLink Element
id / type: 0x7446 / uinteger
range: not 0
path: \Segment\Tracks\TrackEntry\AttachmentLink
maxOccurs: 1
maxver: 3
definition: The UID of an attachment that is used by this codec.
usage notes: The value MUST match the FileUID value of an attachment
found in this Segment.
5.1.4.1.25. CodecDelay Element
id / type / default: 0x56AA / uinteger / 0
path: \Segment\Tracks\TrackEntry\CodecDelay
minOccurs / maxOccurs: 1 / 1
minver: 4
definition: CodecDelay is The codec-built-in delay, built-in delay for the codec, expressed in Matroska
Ticks -- i.e., in nanoseconds; see Section 11.1. It represents
the amount number of codec samples that will be discarded by the decoder
during playback. This timestamp value MUST be subtracted from
each frame timestamp in order to get the timestamp that will be
actually played. The value SHOULD be small so the muxing of
tracks with the same actual timestamp are in the same Cluster.
stream copy: True (Section 8)
5.1.4.1.26. SeekPreRoll Element
id / type / default: 0x56BB / uinteger / 0
path: \Segment\Tracks\TrackEntry\SeekPreRoll
minOccurs / maxOccurs: 1 / 1
minver: 4
definition: After a discontinuity, SeekPreRoll is the duration of the data that the
decoder MUST decode before the decoded data is valid, expressed in
Matroska Ticks -- i.e., in nanoseconds; see Section 11.1.
stream copy: True (Section 8)
5.1.4.1.27. TrackTranslate Element
id / type: 0x6624 / master
path: \Segment\Tracks\TrackEntry\TrackTranslate
definition: The mapping between this TrackEntry and a track value in
the given Chapter Codec.
rationale: Chapter Codec Codecs may need to address content in a specific
track, but they may not know of the way to identify tracks in
Matroska. This element and its child elements add a way to map
the internal tracks known to the Chapter Codec to the track IDs in
Matroska. This allows remuxing a file with Chapter Codec without
changing the content of the codec data, just the track mapping.
5.1.4.1.27.1. TrackTranslateTrackID Element
id / type: 0x66A5 / binary
path: \Segment\Tracks\TrackEntry\TrackTranslate\TrackTranslateTrackI
D
minOccurs / maxOccurs: 1 / 1
definition: The binary value used to represent this TrackEntry in
the chapter codec data. The format depends on the
ChapProcessCodecID used; see Section 5.1.7.1.4.15.
5.1.4.1.27.2. TrackTranslateCodec Element
id / type: 0x66BF / uinteger
path: \Segment\Tracks\TrackEntry\TrackTranslate\TrackTranslateCodec
minOccurs / maxOccurs: 1 / 1
definition: This TrackTranslate applies Applies to this the chapter codec of the given chapter
edition(s); see Section 5.1.7.1.4.15.
defined values: See Table 4. Additional values can be registered in
the "Matroska Chapter Codec IDs" registry defined in Section 27.2.
+=======+=================+============================+
| value | label | definition |
+=======+=================+============================+
| 0 | Matroska Script | Chapter commands using the |
| | | Matroska Script codec. |
+-------+-----------------+----------------------------+
| 1 | DVD-menu | Chapter commands using the |
| | | DVD-like codec. |
+-------+-----------------+----------------------------+
Table 4: TrackTranslateCodec values Values
5.1.4.1.27.3. TrackTranslateEditionUID Element
id / type: 0x66FC / uinteger
path: \Segment\Tracks\TrackEntry\TrackTranslate\TrackTranslateEditio
nUID
definition: Specify Specifies a chapter edition UID on to which this
TrackTranslate applies.
usage notes: When no TrackTranslateEditionUID is specified in the
TrackTranslate, the TrackTranslate applies to all chapter editions
found in the Segment using the given TrackTranslateCodec.
5.1.4.1.28. Video Element
id / type: 0xE0 / master
path: \Segment\Tracks\TrackEntry\Video
maxOccurs: 1
definition: Video settings.
5.1.4.1.28.1. FlagInterlaced Element
id / type / default: 0x9A / uinteger / 0
path: \Segment\Tracks\TrackEntry\Video\FlagInterlaced
minOccurs / maxOccurs: 1 / 1
minver: 2
definition: Specify Specifies whether the video frames in this track are
interlaced.
defined values:
restrictions: See Table 5.
stream copy: True (Section 8)
+=======+==============+==========================+
| value | label | definition |
+=======+==============+==========================+
| 0 | undetermined | Unknown status.This status. This |
| | | value SHOULD be avoided. |
+-------+--------------+--------------------------+
| 1 | interlaced | Interlaced frames. |
+-------+--------------+--------------------------+
| 2 | progressive | No interlacing. |
+-------+--------------+--------------------------+
Table 5: FlagInterlaced values Values
5.1.4.1.28.2. FieldOrder Element
id / type / default: 0x9D / uinteger / 2
path: \Segment\Tracks\TrackEntry\Video\FieldOrder
minOccurs / maxOccurs: 1 / 1
minver: 4
definition: Specify Specifies the field ordering of video frames in this
track.
defined values:
restrictions: See Table 6.
usage notes: If FlagInterlaced is not set to 1, this Element element MUST be
ignored.
stream copy: True (Section 8)
+=======+==============+=========================================+
+=======+===============+=========================================+
| value | label | definition |
+=======+==============+=========================================+
+=======+===============+=========================================+
| 0 | progressive | Interlaced frames.This frames. This value SHOULD be |
| | | avoided, be avoided; setting FlagInterlaced to 2 is |
| | | is sufficient. |
+-------+--------------+-----------------------------------------+
+-------+---------------+-----------------------------------------+
| 1 | tff | Top field displayed first. Top field |
| | | stored first. |
+-------+--------------+-----------------------------------------+
+-------+---------------+-----------------------------------------+
| 2 | undetermined | Unknown field order.This order. This value SHOULD |
| | | be avoided. |
+-------+--------------+-----------------------------------------+
+-------+---------------+-----------------------------------------+
| 6 | bff | Bottom field displayed first. Bottom |
| | | field stored first. |
+-------+--------------+-----------------------------------------+
+-------+---------------+-----------------------------------------+
| 9 | bff(swapped) tff | Top field displayed first. Fields are |
| | (interleaved) | interleaved in storage with the top |
| | | line of the top field stored first. |
+-------+--------------+-----------------------------------------+
+-------+---------------+-----------------------------------------+
| 14 | tff(swapped) bff | Bottom field displayed first. Fields |
| | (interleaved) | are interleaved in storage with the top |
| | | line of the top field stored first. |
+-------+--------------+-----------------------------------------+
+-------+---------------+-----------------------------------------+
Table 6: FieldOrder values Values
5.1.4.1.28.3. StereoMode Element
id / type / default: 0x53B8 / uinteger / 0
path: \Segment\Tracks\TrackEntry\Video\StereoMode
minOccurs / maxOccurs: 1 / 1
minver: 3
definition: Stereo-3D video mode. There are some See Section 18.10 for more details
details.
defined values: See Table 7. Additional values can be registered in
the "Stereo Modes" registry defined in Section 18.10.
restrictions: 27.11.
stream copy: True (Section 8)
+=======+===================================================+
| value | label |
+=======+===================================================+
| 0 | mono |
+-------+---------------------------------------------------+
| 1 | side by side (left eye first) |
+-------+---------------------------------------------------+
| 2 | top - bottom (right eye is first) |
+-------+---------------------------------------------------+
| 3 | top - bottom (left eye is first) |
+-------+---------------------------------------------------+
| 4 | checkboard (right eye is first) |
+-------+---------------------------------------------------+
| 5 | checkboard (left eye is first) |
+-------+---------------------------------------------------+
| 6 | row interleaved (right eye is first) |
+-------+---------------------------------------------------+
| 7 | row interleaved (left eye is first) |
+-------+---------------------------------------------------+
| 8 | column interleaved (right eye is first) |
+-------+---------------------------------------------------+
| 9 | column interleaved (left eye is first) |
+-------+---------------------------------------------------+
| 10 | anaglyph (cyan/red) |
+-------+---------------------------------------------------+
| 11 | side by side (right eye first) |
+-------+---------------------------------------------------+
| 12 | anaglyph (green/magenta) |
+-------+---------------------------------------------------+
| 13 | both eyes laced in one Block (left eye is first) |
+-------+---------------------------------------------------+
| 14 | both eyes laced in one Block (right eye is first) |
+-------+---------------------------------------------------+
Table 7: StereoMode values Values
5.1.4.1.28.4. AlphaMode Element
id / type / default: 0x53C0 / uinteger / 0
path: \Segment\Tracks\TrackEntry\Video\AlphaMode
minOccurs / maxOccurs: 1 / 1
minver: 3
definition: Indicate Indicates whether the BlockAdditional Element element with
BlockAddID of "1" contains Alpha data, data as defined by to the Codec
Mapping for the CodecID. Undefined values (i.e., values other
than 0 or 1) SHOULD NOT be used used, as the behavior of known
implementations is different (considered
either as 0 or 1). different.
defined values: See Table 8. Additional values can be registered in
the "Alpha Modes" registry defined in Section 27.5.
stream copy: True (Section 8)
+=======+=========+============================================+
| value | label | definition |
+=======+=========+============================================+
| 0 | none | The BlockAdditional Element element with |
| | | BlockAddID of "1" does not exist or SHOULD |
| | | NOT be considered as containing such data. |
+-------+---------+--------------------------------------------+
| 1 | present | The BlockAdditional Element element with |
| | | BlockAddID of "1" contains alpha channel |
| | | data. |
+-------+---------+--------------------------------------------+
Table 8: AlphaMode values Values
5.1.4.1.28.5. OldStereoMode Element
id / type: 0x53B9 / uinteger
path: \Segment\Tracks\TrackEntry\Video\OldStereoMode
maxOccurs: 1
maxver: 2
definition: Bogus StereoMode value used in old versions of
libmatroska.
[libmatroska].
restrictions: See Table 9.
usage notes: This Element element MUST NOT be used. It was an incorrect
value used in libmatroska up to 0.9.0.
+=======+===========+
| value | label |
+=======+===========+
| 0 | mono |
+-------+-----------+
| 1 | right eye |
+-------+-----------+
| 2 | left eye |
+-------+-----------+
| 3 | both eyes |
+-------+-----------+
Table 9: OldStereoMode
values
Values
5.1.4.1.28.6. PixelWidth Element
id / type: 0xB0 / uinteger
range: not 0
path: \Segment\Tracks\TrackEntry\Video\PixelWidth
minOccurs / maxOccurs: 1 / 1
definition: Width of the encoded video frames in pixels.
stream copy: True (Section 8)
5.1.4.1.28.7. PixelHeight Element
id / type: 0xBA / uinteger
range: not 0
path: \Segment\Tracks\TrackEntry\Video\PixelHeight
minOccurs / maxOccurs: 1 / 1
definition: Height of the encoded video frames in pixels.
stream copy: True (Section 8)
5.1.4.1.28.8. PixelCropBottom Element
id / type / default: 0x54AA / uinteger / 0
path: \Segment\Tracks\TrackEntry\Video\PixelCropBottom
minOccurs / maxOccurs: 1 / 1
definition: The number of video pixels to remove at the bottom of
the image.
stream copy: True (Section 8)
5.1.4.1.28.9. PixelCropTop Element
id / type / default: 0x54BB / uinteger / 0
path: \Segment\Tracks\TrackEntry\Video\PixelCropTop
minOccurs / maxOccurs: 1 / 1
definition: The number of video pixels to remove at the top of the
image.
stream copy: True (Section 8)
5.1.4.1.28.10. PixelCropLeft Element
id / type / default: 0x54CC / uinteger / 0
path: \Segment\Tracks\TrackEntry\Video\PixelCropLeft
minOccurs / maxOccurs: 1 / 1
definition: The number of video pixels to remove on the left of the
image.
stream copy: True (Section 8)
5.1.4.1.28.11. PixelCropRight Element
id / type / default: 0x54DD / uinteger / 0
path: \Segment\Tracks\TrackEntry\Video\PixelCropRight
minOccurs / maxOccurs: 1 / 1
definition: The number of video pixels to remove on the right of the
image.
stream copy: True (Section 8)
5.1.4.1.28.12. DisplayWidth Element
id / type: 0x54B0 / uinteger
range: not 0
path: \Segment\Tracks\TrackEntry\Video\DisplayWidth
maxOccurs: 1
definition: Width of the video frames to display. Applies to the
video frame after cropping (PixelCrop* Elements).
notes: See Table 10.
stream copy: True (Section 8)
+===========+=================================================+
+===========+==================================================+
| attribute | note |
+===========+=================================================+
+===========+==================================================+
| default | If the DisplayUnit of the same TrackEntry is 0, |
| | then the default value for DisplayWidth is equal |
| | equal toPixelWidth to PixelWidth - PixelCropLeft - PixelCropRight; |
| | PixelCropRight, else else, there is no default value. |
+-----------+-------------------------------------------------+
+-----------+--------------------------------------------------+
Table 10: DisplayWidth implementation notes Implementation Notes
5.1.4.1.28.13. DisplayHeight Element
id / type: 0x54BA / uinteger
range: not 0
path: \Segment\Tracks\TrackEntry\Video\DisplayHeight
maxOccurs: 1
definition: Height of the video frames to display. Applies to the
video frame after cropping (PixelCrop* Elements).
notes: See Table 11.
stream copy: True (Section 8)
+===========+==================================================+
+===========+===================================================+
| attribute | note |
+===========+==================================================+
+===========+===================================================+
| default | If the DisplayUnit of the same TrackEntry is 0, |
| | then the default value for DisplayHeight is equal |
| | equal toPixelHeight to PixelHeight - PixelCropTop - PixelCropBottom; |
| | PixelCropBottom, else else, there is no default value. |
+-----------+--------------------------------------------------+
+-----------+---------------------------------------------------+
Table 11: DisplayHeight implementation notes Implementation Notes
5.1.4.1.28.14. DisplayUnit Element
id / type / default: 0x54B2 / uinteger / 0
path: \Segment\Tracks\TrackEntry\Video\DisplayUnit
minOccurs / maxOccurs: 1 / 1
definition: How DisplayWidth & and DisplayHeight are interpreted.
restrictions:
defined values: See Table 12. Additional values can be registered
in the "Display Units" registry defined in Section 27.12.
+=======+======================+
| value | label |
+=======+======================+
| 0 | pixels |
+-------+----------------------+
| 1 | centimeters |
+-------+----------------------+
| 2 | inches |
+-------+----------------------+
| 3 | display aspect ratio |
+-------+----------------------+
| 4 | unknown |
+-------+----------------------+
Table 12: DisplayUnit values Values
5.1.4.1.28.15. UncompressedFourCC Element
id / type: 0x2EB524 / binary
length: 4
path: \Segment\Tracks\TrackEntry\Video\UncompressedFourCC
minOccurs / maxOccurs: see implementation notes See Table 13 / 1
definition: Specify Specifies the uncompressed pixel format used for the
Track's data as a FourCC. This value is similar in scope to the
biCompression value of AVI's BITMAPINFO [AVIFormat]. There is no
neither a definitive list of FourCC values, values nor an official
registry. Some common values for YUV pixel formats can be found
at [MSYUV8],
[MSYUV16] [MSYUV16], and [FourCC-YUV]. Some common values for
uncompressed RGB pixel formats can be found at [MSRGB] and
[FourCC-RGB].
notes: See Table 13.
stream copy: True (Section 8)
+===========+==============================================+
| attribute | note |
+===========+==============================================+
| minOccurs | UncompressedFourCC MUST be set (minOccurs=1) |
| | in TrackEntry, TrackEntry when the CodecID Element element of |
| | the TrackEntry is set to "V_UNCOMPRESSED". |
+-----------+----------------------------------------------+
Table 13: UncompressedFourCC implementation notes Implementation Notes
5.1.4.1.28.16. Colour Element
id / type: 0x55B0 / master
path: \Segment\Tracks\TrackEntry\Video\Colour
maxOccurs: 1
minver: 4
definition: Settings describing the colour color format.
stream copy: True (Section 8)
5.1.4.1.28.17. MatrixCoefficients Element
id / type / default: 0x55B1 / uinteger / 2
path: \Segment\Tracks\TrackEntry\Video\Colour\MatrixCoefficients
minOccurs / maxOccurs: 1 / 1
minver: 4
definition: The Matrix Coefficients of the video used to derive luma
and chroma values from red, green, and blue color primaries. For
clarity, the value and meanings for MatrixCoefficients are adopted
from Table 4 of [ITU-H.273].
restrictions: See Table 14.
stream copy: True (Section 8)
+=======+=======================================+
| value | label |
+=======+=======================================+
| 0 | Identity |
+-------+---------------------------------------+
| 1 | ITU-R BT.709 |
+-------+---------------------------------------+
| 2 | unspecified |
+-------+---------------------------------------+
| 3 | reserved |
+-------+---------------------------------------+
| 4 | US FCC 73.682 |
+-------+---------------------------------------+
| 5 | ITU-R BT.470BG |
+-------+---------------------------------------+
| 6 | SMPTE 170M |
+-------+---------------------------------------+
| 7 | SMPTE 240M |
+-------+---------------------------------------+
| 8 | YCoCg |
+-------+---------------------------------------+
| 9 | BT2020 Non-constant Luminance |
+-------+---------------------------------------+
| 10 | BT2020 Constant Luminance |
+-------+---------------------------------------+
| 11 | SMPTE ST 2085 |
+-------+---------------------------------------+
| 12 | Chroma-derived Non-constant Luminance |
+-------+---------------------------------------+
| 13 | Chroma-derived Constant Luminance |
+-------+---------------------------------------+
| 14 | ITU-R BT.2100-0 |
+-------+---------------------------------------+
Table 14: MatrixCoefficients values Values
5.1.4.1.28.18. BitsPerChannel Element
id / type / default: 0x55B2 / uinteger / 0
path: \Segment\Tracks\TrackEntry\Video\Colour\BitsPerChannel
minOccurs / maxOccurs: 1 / 1
minver: 4
definition: Number of decoded bits per channel. A value of 0
indicates that the BitsPerChannel is unspecified.
stream copy: True (Section 8)
5.1.4.1.28.19. ChromaSubsamplingHorz Element
id / type: 0x55B3 / uinteger
path: \Segment\Tracks\TrackEntry\Video\Colour\ChromaSubsamplingHorz
maxOccurs: 1
minver: 4
definition: The amount number of pixels to remove in the Cr and Cb channels
for every pixel not removed horizontally. Example: For video with
4:2:0 chroma subsampling, the ChromaSubsamplingHorz SHOULD be set
to 1.
stream copy: True (Section 8)
5.1.4.1.28.20. ChromaSubsamplingVert Element
id / type: 0x55B4 / uinteger
path: \Segment\Tracks\TrackEntry\Video\Colour\ChromaSubsamplingVert
maxOccurs: 1
minver: 4
definition: The amount number of pixels to remove in the Cr and Cb channels
for every pixel not removed vertically. Example: For video with
4:2:0 chroma subsampling, the ChromaSubsamplingVert SHOULD be set
to 1.
stream copy: True (Section 8)
5.1.4.1.28.21. CbSubsamplingHorz Element
id / type: 0x55B5 / uinteger
path: \Segment\Tracks\TrackEntry\Video\Colour\CbSubsamplingHorz
maxOccurs: 1
minver: 4
definition: The amount number of pixels to remove in the Cb channel for
every pixel not removed horizontally. This is additive with
ChromaSubsamplingHorz. Example: For video with 4:2:1 chroma
subsampling, the ChromaSubsamplingHorz SHOULD be set to 1 1, and
CbSubsamplingHorz SHOULD be set to 1.
stream copy: True (Section 8)
5.1.4.1.28.22. CbSubsamplingVert Element
id / type: 0x55B6 / uinteger
path: \Segment\Tracks\TrackEntry\Video\Colour\CbSubsamplingVert
maxOccurs: 1
minver: 4
definition: The amount number of pixels to remove in the Cb channel for
every pixel not removed vertically. This is additive with
ChromaSubsamplingVert.
stream copy: True (Section 8)
5.1.4.1.28.23. ChromaSitingHorz Element
id / type / default: 0x55B7 / uinteger / 0
path: \Segment\Tracks\TrackEntry\Video\Colour\ChromaSitingHorz
minOccurs / maxOccurs: 1 / 1
minver: 4
definition: How chroma is subsampled horizontally.
restrictions:
defined values: See Table 15. Additional values can be registered
in the "Horizontal Chroma Sitings" registry defined in
Section 27.15.
stream copy: True (Section 8)
+=======+=================+
| value | label |
+=======+=================+
| 0 | unspecified |
+-------+-----------------+
| 1 | left collocated |
+-------+-----------------+
| 2 | half |
+-------+-----------------+
Table 15:
ChromaSitingHorz values Values
5.1.4.1.28.24. ChromaSitingVert Element
id / type / default: 0x55B8 / uinteger / 0
path: \Segment\Tracks\TrackEntry\Video\Colour\ChromaSitingVert
minOccurs / maxOccurs: 1 / 1
minver: 4
definition: How chroma is subsampled vertically.
restrictions:
defined values: See Table 16. Additional values can be registered
in the "Vertical Chroma Sitings" registry defined in
Section 27.16.
stream copy: True (Section 8)
+=======+================+
| value | label |
+=======+================+
| 0 | unspecified |
+-------+----------------+
| 1 | top collocated |
+-------+----------------+
| 2 | half |
+-------+----------------+
Table 16:
ChromaSitingVert
values
Values
5.1.4.1.28.25. Range Element
id / type / default: 0x55B9 / uinteger / 0
path: \Segment\Tracks\TrackEntry\Video\Colour\Range
minOccurs / maxOccurs: 1 / 1
minver: 4
definition: Clipping of the color ranges.
restrictions:
defined values: See Table 17. Additional values can be defined in
the "Color Ranges" registry defined in Section 27.17.
stream copy: True (Section 8)
+=======+=========================================================+
| value | label |
+=======+=========================================================+
| 0 | unspecified |
+-------+---------------------------------------------------------+
| 1 | broadcast range |
+-------+---------------------------------------------------------+
| 2 | full range (no clipping) |
+-------+---------------------------------------------------------+
| 3 | defined by MatrixCoefficients / TransferCharacteristics |
+-------+---------------------------------------------------------+
Table 17: Range values Values
5.1.4.1.28.26. TransferCharacteristics Element
id / type / default: 0x55BA / uinteger / 2
path: \Segment\Tracks\TrackEntry\Video\Colour\TransferCharacteristic
s
minOccurs / maxOccurs: 1 / 1
minver: 4
definition: The transfer characteristics of the video. For clarity,
the value and meanings for TransferCharacteristics are adopted
from Table 3 of [ITU-H.273].
restrictions: See Table 18.
stream copy: True (Section 8)
+=======+=======================================+
| value | label |
+=======+=======================================+
| 0 | reserved |
+-------+---------------------------------------+
| 1 | ITU-R BT.709 |
+-------+---------------------------------------+
| 2 | unspecified |
+-------+---------------------------------------+
| 3 | reserved2 |
+-------+---------------------------------------+
| 4 | Gamma 2.2 curve - BT.470M |
+-------+---------------------------------------+
| 5 | Gamma 2.8 curve - BT.470BG |
+-------+---------------------------------------+
| 6 | SMPTE 170M |
+-------+---------------------------------------+
| 7 | SMPTE 240M |
+-------+---------------------------------------+
| 8 | Linear |
+-------+---------------------------------------+
| 9 | Log |
+-------+---------------------------------------+
| 10 | Log Sqrt |
+-------+---------------------------------------+
| 11 | IEC 61966-2-4 |
+-------+---------------------------------------+
| 12 | ITU-R BT.1361 Extended Colour Gamut |
+-------+---------------------------------------+
| 13 | IEC 61966-2-1 |
+-------+---------------------------------------+
| 14 | ITU-R BT.2020 10 bit |
+-------+---------------------------------------+
| 15 | ITU-R BT.2020 12 bit |
+-------+---------------------------------------+
| 16 | ITU-R BT.2100 Perceptual Quantization |
+-------+---------------------------------------+
| 17 | SMPTE ST 428-1 |
+-------+---------------------------------------+
| 18 | ARIB STD-B67 (HLG) |
+-------+---------------------------------------+
Table 18: TransferCharacteristics values Values
5.1.4.1.28.27. Primaries Element
id / type / default: 0x55BB / uinteger / 2
path: \Segment\Tracks\TrackEntry\Video\Colour\Primaries
minOccurs / maxOccurs: 1 / 1
minver: 4
definition: The colour color primaries of the video. For clarity, the
value and meanings for Primaries are adopted from Table 2 of
[ITU-H.273].
restrictions: See Table 19.
stream copy: True (Section 8)
+=======+========================================+
| value | label |
+=======+========================================+
| 0 | reserved |
+-------+----------------------------------------+
| 1 | ITU-R BT.709 |
+-------+----------------------------------------+
| 2 | unspecified |
+-------+----------------------------------------+
| 3 | reserved2 |
+-------+----------------------------------------+
| 4 | ITU-R BT.470M |
+-------+----------------------------------------+
| 5 | ITU-R BT.470BG - BT.601 625 |
+-------+----------------------------------------+
| 6 | ITU-R BT.601 525 - SMPTE 170M |
+-------+----------------------------------------+
| 7 | SMPTE 240M |
+-------+----------------------------------------+
| 8 | FILM |
+-------+----------------------------------------+
| 9 | ITU-R BT.2020 |
+-------+----------------------------------------+
| 10 | SMPTE ST 428-1 |
+-------+----------------------------------------+
| 11 | SMPTE RP 432-2 |
+-------+----------------------------------------+
| 12 | SMPTE EG 432-2 |
+-------+----------------------------------------+
| 22 | EBU Tech. 3213-E - JEDEC P22 phosphors |
+-------+----------------------------------------+
Table 19: Primaries values Values
5.1.4.1.28.28. MaxCLL Element
id / type: 0x55BC / uinteger
path: \Segment\Tracks\TrackEntry\Video\Colour\MaxCLL
maxOccurs: 1
minver: 4
definition: Maximum brightness of a single pixel (Maximum Content
Light Level) in candelas per square meter (cd/m^2).
stream copy: True (Section 8)
5.1.4.1.28.29. MaxFALL Element
id / type: 0x55BD / uinteger
path: \Segment\Tracks\TrackEntry\Video\Colour\MaxFALL
maxOccurs: 1
minver: 4
definition: Maximum brightness of a single full frame (Maximum
Frame-Average Light Level) in candelas per square meter (cd/m^2).
stream copy: True (Section 8)
5.1.4.1.28.30. MasteringMetadata Element
id / type: 0x55D0 / master
path: \Segment\Tracks\TrackEntry\Video\Colour\MasteringMetadata
maxOccurs: 1
minver: 4
definition: SMPTE 2086 mastering data.
stream copy: True (Section 8)
5.1.4.1.28.31. PrimaryRChromaticityX Element
id / type: 0x55D1 / float
range: 0x0p+0-0x1p+0
path: \Segment\Tracks\TrackEntry\Video\Colour\MasteringMetadata\Prim
aryRChromaticityX
maxOccurs: 1
minver: 4
definition: Red X chromaticity coordinate, as defined by [CIE-1931].
stream copy: True (Section 8)
5.1.4.1.28.32. PrimaryRChromaticityY Element
id / type: 0x55D2 / float
range: 0x0p+0-0x1p+0
path: \Segment\Tracks\TrackEntry\Video\Colour\MasteringMetadata\Prim
aryRChromaticityY
maxOccurs: 1
minver: 4
definition: Red Y chromaticity coordinate, as defined by [CIE-1931].
stream copy: True (Section 8)
5.1.4.1.28.33. PrimaryGChromaticityX Element
id / type: 0x55D3 / float
range: 0x0p+0-0x1p+0
path: \Segment\Tracks\TrackEntry\Video\Colour\MasteringMetadata\Prim
aryGChromaticityX
maxOccurs: 1
minver: 4
definition: Green X chromaticity coordinate, as defined by
[CIE-1931].
stream copy: True (Section 8)
5.1.4.1.28.34. PrimaryGChromaticityY Element
id / type: 0x55D4 / float
range: 0x0p+0-0x1p+0
path: \Segment\Tracks\TrackEntry\Video\Colour\MasteringMetadata\Prim
aryGChromaticityY
maxOccurs: 1
minver: 4
definition: Green Y chromaticity coordinate, as defined by
[CIE-1931].
stream copy: True (Section 8)
5.1.4.1.28.35. PrimaryBChromaticityX Element
id / type: 0x55D5 / float
range: 0x0p+0-0x1p+0
path: \Segment\Tracks\TrackEntry\Video\Colour\MasteringMetadata\Prim
aryBChromaticityX
maxOccurs: 1
minver: 4
definition: Blue X chromaticity coordinate, as defined by
[CIE-1931].
stream copy: True (Section 8)
5.1.4.1.28.36. PrimaryBChromaticityY Element
id / type: 0x55D6 / float
range: 0x0p+0-0x1p+0
path: \Segment\Tracks\TrackEntry\Video\Colour\MasteringMetadata\Prim
aryBChromaticityY
maxOccurs: 1
minver: 4
definition: Blue Y chromaticity coordinate, as defined by
[CIE-1931].
stream copy: True (Section 8)
5.1.4.1.28.37. WhitePointChromaticityX Element
id / type: 0x55D7 / float
range: 0x0p+0-0x1p+0
path: \Segment\Tracks\TrackEntry\Video\Colour\MasteringMetadata\Whit
ePointChromaticityX
maxOccurs: 1
minver: 4
definition: White X chromaticity coordinate, as defined by
[CIE-1931].
stream copy: True (Section 8)
5.1.4.1.28.38. WhitePointChromaticityY Element
id / type: 0x55D8 / float
range: 0x0p+0-0x1p+0
path: \Segment\Tracks\TrackEntry\Video\Colour\MasteringMetadata\Whit
ePointChromaticityY
maxOccurs: 1
minver: 4
definition: White Y chromaticity coordinate, as defined by
[CIE-1931].
stream copy: True (Section 8)
5.1.4.1.28.39. LuminanceMax Element
id / type: 0x55D9 / float
range: >= 0x0p+0
path: \Segment\Tracks\TrackEntry\Video\Colour\MasteringMetadata\Lumi
nanceMax
maxOccurs: 1
minver: 4
definition: Maximum luminance. Represented in candelas per square
meter (cd/m^2).
stream copy: True (Section 8)
5.1.4.1.28.40. LuminanceMin Element
id / type: 0x55DA / float
range: >= 0x0p+0
path: \Segment\Tracks\TrackEntry\Video\Colour\MasteringMetadata\Lumi
nanceMin
maxOccurs: 1
minver: 4
definition: Minimum luminance. Represented in candelas per square
meter (cd/m^2).
stream copy: True (Section 8)
5.1.4.1.28.41. Projection Element
id / type: 0x7670 / master
path: \Segment\Tracks\TrackEntry\Video\Projection
maxOccurs: 1
minver: 4
definition: Describes the video projection details. Used to render
spherical,
spherical or VR videos or flipping to flip videos horizontally/vertically. horizontally or
vertically.
stream copy: True (Section 8)
5.1.4.1.28.42. ProjectionType Element
id / type / default: 0x7671 / uinteger / 0
path: \Segment\Tracks\TrackEntry\Video\Projection\ProjectionType
minOccurs / maxOccurs: 1 / 1
minver: 4
definition: Describes the projection used for this video track.
restrictions:
defined values: See Table 20. Additional values can be registered
in the "Projection Types" registry defined in Section 27.13.
stream copy: True (Section 8)
+=======+=================+
| value | label |
+=======+=================+
| 0 | rectangular |
+-------+-----------------+
| 1 | equirectangular |
+-------+-----------------+
| 2 | cubemap |
+-------+-----------------+
| 3 | mesh |
+-------+-----------------+
Table 20:
ProjectionType values Values
5.1.4.1.28.43. ProjectionPrivate Element
id / type: 0x7672 / binary
path: \Segment\Tracks\TrackEntry\Video\Projection\ProjectionPrivate
maxOccurs: 1
minver: 4
definition: Private data that only applies to a specific projection.
* If ProjectionType equals 0 (Rectangular), (rectangular), then this element MUST
NOT be present.
* If ProjectionType equals 1 (Equirectangular), (equirectangular), then this element
MUST be present and contain the same binary data that would be
stored inside an ISOBMFF Equirectangular Projection Box ('equi'). ("equi").
* If ProjectionType equals 2 (Cubemap), (cubemap), then this element MUST be
present and contain the same binary data that would be stored
inside an ISOBMFF Cubemap Projection Box ('cbmp'). ("cbmp").
* If ProjectionType equals 3 (Mesh), (mesh), then this element MUST be
present and contain the same binary data that would be stored
inside an ISOBMFF Mesh Projection Box ('mshp'). ("mshp").
usage notes: ISOBMFF box size and fourcc FourCC fields are not included in
the binary data, but the FullBox version and flag fields are.
This is to avoid redundant framing information while preserving
versioning and semantics between the two container formats.
stream copy: True (Section 8)
5.1.4.1.28.44. ProjectionPoseYaw Element
id / type / default: 0x7673 / float / 0x0p+0
range: >= -0xB4p+0, <= 0xB4p+0
path: \Segment\Tracks\TrackEntry\Video\Projection\ProjectionPoseYaw
minOccurs / maxOccurs: 1 / 1
minver: 4
definition: Specifies a yaw rotation to the projection. Value
represents a clockwise rotation, in degrees, around the up vector.
This rotation must be applied before any ProjectionPosePitch or
ProjectionPoseRoll rotations. The value of this element MUST be
in the -180 to 180 degree range, both included. inclusive.
Setting ProjectionPoseYaw to 180 or -180 degrees, degrees with the
ProjectionPoseRoll and ProjectionPosePitch set to 0 degrees flips the
image horizontally.
stream copy: True (Section 8)
5.1.4.1.28.45. ProjectionPosePitch Element
id / type / default: 0x7674 / float / 0x0p+0
range: >= -0x5Ap+0, <= 0x5Ap+0
path: \Segment\Tracks\TrackEntry\Video\Projection\ProjectionPosePitc
h
minOccurs / maxOccurs: 1 / 1
minver: 4
definition: Specifies a pitch rotation to the projection. Value
represents a counter-clockwise rotation, in degrees, around the
right vector. This rotation must be applied after the
ProjectionPoseYaw rotation and before the ProjectionPoseRoll
rotation. The value of this element MUST be in the -90 to 90
degree range, both included. inclusive.
stream copy: True (Section 8)
5.1.4.1.28.46. ProjectionPoseRoll Element
id / type / default: 0x7675 / float / 0x0p+0
range: >= -0xB4p+0, <= 0xB4p+0
path: \Segment\Tracks\TrackEntry\Video\Projection\ProjectionPoseRoll
minOccurs / maxOccurs: 1 / 1
minver: 4
definition: Specifies a roll rotation to the projection. Value
represents a counter-clockwise rotation, in degrees, around the
forward vector. This rotation must be applied after the
ProjectionPoseYaw and ProjectionPosePitch rotations. The value of
this element MUST be in the -180 to 180 degree range, both included.
inclusive. Setting ProjectionPoseRoll to 180 or -180 degrees, the degrees and
ProjectionPoseYaw to 180 or -180 degrees with ProjectionPosePitch
set to 0 degrees flips the image vertically. Setting
ProjectionPoseRoll to 180 or -180 degrees, degrees with the ProjectionPoseYaw
and ProjectionPosePitch set to 0 degrees flips the image
horizontally and vertically.
stream copy: True (Section 8)
5.1.4.1.29. Audio Element
id / type: 0xE1 / master
path: \Segment\Tracks\TrackEntry\Audio
maxOccurs: 1
definition: Audio settings.
5.1.4.1.29.1. SamplingFrequency Element
id / type / default: 0xB5 / float / 0x1.f4p+12
range: > 0x0p+0
path: \Segment\Tracks\TrackEntry\Audio\SamplingFrequency
minOccurs / maxOccurs: 1 / 1
definition: Sampling frequency in Hz.
stream copy: True (Section 8)
5.1.4.1.29.2. OutputSamplingFrequency Element
id / type: 0x78B5 / float
range: > 0x0p+0
path: \Segment\Tracks\TrackEntry\Audio\OutputSamplingFrequency
maxOccurs: 1
definition: Real output sampling frequency in Hz (used that is used for SBR
techniques).
Spectral Band Replication (SBR) techniques.
notes: See Table 21.
+===========+======================================================+
| attribute | note |
+===========+======================================================+
| default | The default value for OutputSamplingFrequency of the |
| | same TrackEntry is equal to the SamplingFrequency. |
+-----------+------------------------------------------------------+
Table 21: OutputSamplingFrequency implementation notes Implementation Notes
5.1.4.1.29.3. Channels Element
id / type / default: 0x9F / uinteger / 1
range: not 0
path: \Segment\Tracks\TrackEntry\Audio\Channels
minOccurs / maxOccurs: 1 / 1
definition: Numbers of channels in the track.
stream copy: True (Section 8)
5.1.4.1.29.4. BitDepth Element
id / type: 0x6264 / uinteger
range: not 0
path: \Segment\Tracks\TrackEntry\Audio\BitDepth
maxOccurs: 1
definition: Bits per sample, mostly used for PCM.
stream copy: True (Section 8)
5.1.4.1.30. TrackOperation Element
id / type: 0xE2 / master
path: \Segment\Tracks\TrackEntry\TrackOperation
maxOccurs: 1
minver: 3
definition: Operation that needs to be applied on tracks to create
this virtual track. For more details look at details, see Section 18.8.
stream copy: True (Section 8)
5.1.4.1.30.1. TrackCombinePlanes Element
id / type: 0xE3 / master
path: \Segment\Tracks\TrackEntry\TrackOperation\TrackCombinePlanes
maxOccurs: 1
minver: 3
definition: Contains the list of all video plane tracks that need to
be combined to create this 3D track track.
stream copy: True (Section 8)
5.1.4.1.30.2. TrackPlane Element
id / type: 0xE4 / master
path: \Segment\Tracks\TrackEntry\TrackOperation\TrackCombinePlanes\T
rackPlane
minOccurs: 1
minver: 3
definition: Contains a video plane track that need needs to be combined
to create this 3D track track.
stream copy: True (Section 8)
5.1.4.1.30.3. TrackPlaneUID Element
id / type: 0xE5 / uinteger
range: not 0
path: \Segment\Tracks\TrackEntry\TrackOperation\TrackCombinePlanes\T
rackPlane\TrackPlaneUID
minOccurs / maxOccurs: 1 / 1
minver: 3
definition: The trackUID TrackUID number of the track representing the plane.
stream copy: True (Section 8)
5.1.4.1.30.4. TrackPlaneType Element
id / type: 0xE6 / uinteger
path: \Segment\Tracks\TrackEntry\TrackOperation\TrackCombinePlanes\T
rackPlane\TrackPlaneType
minOccurs / maxOccurs: 1 / 1
minver: 3
definition: The kind of plane this track corresponds to.
restrictions:
defined values: See Table 22. Additional values can be registered
in the "Track Plane Types" registry defined in Section 27.14.
stream copy: True (Section 8)
+=======+============+
| value | label |
+=======+============+
| 0 | left eye |
+-------+------------+
| 1 | right eye |
+-------+------------+
| 2 | background |
+-------+------------+
Table 22:
TrackPlaneType values Values
5.1.4.1.30.5. TrackJoinBlocks Element
id / type: 0xE9 / master
path: \Segment\Tracks\TrackEntry\TrackOperation\TrackJoinBlocks
maxOccurs: 1
minver: 3
definition: Contains the list of all tracks whose Blocks need to be
combined to create this virtual track track.
stream copy: True (Section 8)
5.1.4.1.30.6. TrackJoinUID Element
id / type: 0xED / uinteger
range: not 0
path: \Segment\Tracks\TrackEntry\TrackOperation\TrackJoinBlocks\Trac
kJoinUID
minOccurs: 1
minver: 3
definition: The trackUID TrackUID number of a track whose blocks are used to
create this virtual track.
stream copy: True (Section 8)
5.1.4.1.31. ContentEncodings Element
id / type: 0x6D80 / master
path: \Segment\Tracks\TrackEntry\ContentEncodings
maxOccurs: 1
definition: Settings for several content encoding mechanisms like
compression or encryption.
stream copy: True (Section 8)
5.1.4.1.31.1. ContentEncoding Element
id / type: 0x6240 / master
path: \Segment\Tracks\TrackEntry\ContentEncodings\ContentEncoding
minOccurs: 1
definition: Settings for one content encoding like compression or
encryption.
stream copy: True (Section 8)
5.1.4.1.31.2. ContentEncodingOrder Element
id / type / default: 0x5031 / uinteger / 0
path: \Segment\Tracks\TrackEntry\ContentEncodings\ContentEncoding\Co
ntentEncodingOrder
minOccurs / maxOccurs: 1 / 1
definition: Tell in which Defines the order to apply each ContentEncoding of the
ContentEncodings. The decoder/demuxer MUST start with the
ContentEncoding with the highest ContentEncodingOrder and work its
way down to the ContentEncoding with the lowest
ContentEncodingOrder. This value MUST be unique over for each
ContentEncoding found in the ContentEncodings of this TrackEntry.
stream copy: True (Section 8)
5.1.4.1.31.3. ContentEncodingScope Element
id / type / default: 0x5032 / uinteger / 1
path: \Segment\Tracks\TrackEntry\ContentEncodings\ContentEncoding\Co
ntentEncodingScope
minOccurs / maxOccurs: 1 / 1
definition: A bit field that describes which Elements elements have been
modified in this way. Values (big-endian) can be OR'ed.
defined values: See Table 23. Additional values can be registered
in the "Content Encoding Scopes" registry defined in Section 27.6.
stream copy: True (Section 8)
+=======+=========+===========================================+
+=======+=========+============================================+
| value | label | definition |
+=======+=========+===========================================+
+=======+=========+============================================+
| 1 | Block | All frame contents, excluding lacing |
| | | data. |
+-------+---------+-------------------------------------------+
+-------+---------+--------------------------------------------+
| 2 | Private | The track's CodecPrivate data. |
+-------+---------+-------------------------------------------+
+-------+---------+--------------------------------------------+
| 4 | Next | The next ContentEncoding (next |
| | | ContentEncodingOrder. Either ContentEncodingOrder; the data inside |
| | | inside ContentCompression and/or |
| | | ContentEncryption).This ContentEncryption). This value SHOULD NOT |
| | | be used used, as it's not supported by players. |
+-------+---------+-------------------------------------------+
+-------+---------+--------------------------------------------+
Table 23: ContentEncodingScope values Values
5.1.4.1.31.4. ContentEncodingType Element
id / type / default: 0x5033 / uinteger / 0
path: \Segment\Tracks\TrackEntry\ContentEncodings\ContentEncoding\Co
ntentEncodingType
minOccurs / maxOccurs: 1 / 1
definition: A value describing what the kind of transformation that is
applied.
restrictions:
defined values: See Table 24. Additional values can be registered
in the "Content Encoding Types" registry defined in Section 27.7.
stream copy: True (Section 8)
+=======+=============+
| value | label |
+=======+=============+
| 0 | Compression |
+-------+-------------+
| 1 | Encryption |
+-------+-------------+
Table 24:
ContentEncodingType
values
Values
5.1.4.1.31.5. ContentCompression Element
id / type: 0x5034 / master
path: \Segment\Tracks\TrackEntry\ContentEncodings\ContentEncoding\Co
ntentCompression
maxOccurs: 1
definition: Settings describing the compression used. This Element element
MUST be present if the value of ContentEncodingType is 0 and
absent otherwise. Each block MUST be decompressable decompressable, even if no
previous block is available in order not to not prevent seeking.
stream copy: True (Section 8)
5.1.4.1.31.6. ContentCompAlgo Element
id / type / default: 0x4254 / uinteger / 0
path: \Segment\Tracks\TrackEntry\ContentEncodings\ContentEncoding\Co
ntentCompression\ContentCompAlgo
minOccurs / maxOccurs: 1 / 1
definition: The compression algorithm used.
defined values: See Table 25. Additional values can be registered
in the "Compression Algorithms" registry defined in Section 27.8.
usage notes: Compression method "1" (bzlib) and "2" (lzo1x) are
lacking lack
proper documentation on the format format, which limits implementation
possibilities. Due to licensing conflicts on commonly available libraries
libraries' compression methods methods, "2" (lzo1x) does not offer
widespread interoperability. A Matroska Writer SHOULD NOT use
these compression methods by default. A Matroska Reader MAY
support methods "1" and "2" as possible, and SHOULD support other methods.
stream copy: True (Section 8)
+=======+===========+=========================================+
+=======+===========+========================================+
| value | label | definition |
+=======+===========+=========================================+
+=======+===========+========================================+
| 0 | zlib | zlib compression [RFC1950]. |
+-------+-----------+-----------------------------------------+
+-------+-----------+----------------------------------------+
| 1 | bzlib | bzip2 compression [BZIP2], [BZIP2] SHOULD NOT |
| | | be used; see usage notes. |
+-------+-----------+-----------------------------------------+
+-------+-----------+----------------------------------------+
| 2 | lzo1x | Lempel-Ziv-Oberhumer compression [LZO], [LZO] |
| | | SHOULD NOT be used; see usage notes. |
+-------+-----------+-----------------------------------------+
+-------+-----------+----------------------------------------+
| 3 | Header | Octets in ContentCompSettings |
| | Stripping | (Section 5.1.4.1.31.7) have been |
| | | stripped from each frame. |
+-------+-----------+-----------------------------------------+
+-------+-----------+----------------------------------------+
Table 25: ContentCompAlgo values Values
5.1.4.1.31.7. ContentCompSettings Element
id / type: 0x4255 / binary
path: \Segment\Tracks\TrackEntry\ContentEncodings\ContentEncoding\Co
ntentCompression\ContentCompSettings
maxOccurs: 1
definition: Settings that might be needed by the decompressor. For
Header Stripping (ContentCompAlgo=3), the bytes that were removed
from the beginning of each frames frame of the track.
stream copy: True (Section 8)
5.1.4.1.31.8. ContentEncryption Element
id / type: 0x5035 / master
path: \Segment\Tracks\TrackEntry\ContentEncodings\ContentEncoding\Co
ntentEncryption
maxOccurs: 1
definition: Settings describing the encryption used. This Element element
MUST be present if the value of ContentEncodingType is 1
(encryption) and MUST be ignored otherwise. A Matroska Player MAY
support encryption.
stream copy: True (Section 8)
5.1.4.1.31.9. ContentEncAlgo Element
id / type / default: 0x47E1 / uinteger / 0
path: \Segment\Tracks\TrackEntry\ContentEncodings\ContentEncoding\Co
ntentEncryption\ContentEncAlgo
minOccurs / maxOccurs: 1 / 1
definition: The encryption algorithm used.
defined values: See Table 26. Additional values can be registered
in the "Encryption Algorithms" registry defined in Section 27.9.
stream copy: True (Section 8)
+=======+===============+===========================================+
+=======+===========+============================================+
| value | label | definition |
+=======+===============+===========================================+
+=======+===========+============================================+
| 0 | Not | The data are not encrypted. |
| | encrypted | |
+-------+---------------+-------------------------------------------+
+-------+-----------+--------------------------------------------+
| 1 | DES | Data Encryption Standard (DES) [FIPS46-3]. |
| | | [FIPS.46-3].This This value SHOULD be avoided. |
+-------+---------------+-------------------------------------------+
+-------+-----------+--------------------------------------------+
| 2 | 3DES | Triple Data Encryption Algorithm |
| | | [SP.800-67].This [SP800-67]. This value SHOULD be avoided. |
+-------+---------------+-------------------------------------------+
+-------+-----------+--------------------------------------------+
| 3 | Twofish | Twofish Encryption Algorithm [Twofish]. |
+-------+---------------+-------------------------------------------+
+-------+-----------+--------------------------------------------+
| 4 | Blowfish | Blowfish Encryption Algorithm [Blowfish]. |
| | | [Blowfish].This This value SHOULD be avoided. |
+-------+---------------+-------------------------------------------+
+-------+-----------+--------------------------------------------+
| 5 | AES | Advanced Encryption Standard (AES) |
| | | [FIPS.197]. [FIPS197]. |
+-------+---------------+-------------------------------------------+
+-------+-----------+--------------------------------------------+
Table 26: ContentEncAlgo values Values
5.1.4.1.31.10. ContentEncKeyID Element
id / type: 0x47E2 / binary
path: \Segment\Tracks\TrackEntry\ContentEncodings\ContentEncoding\Co
ntentEncryption\ContentEncKeyID
maxOccurs: 1
definition: For public key algorithms this is algorithms, the ID of the public key that
the data was encrypted with.
stream copy: True (Section 8)
5.1.4.1.31.11. ContentEncAESSettings Element
id / type: 0x47E7 / master
path: \Segment\Tracks\TrackEntry\ContentEncodings\ContentEncoding\Co
ntentEncryption\ContentEncAESSettings
maxOccurs: 1
minver: 4
definition: Settings describing the encryption algorithm used.
notes: See Table 27.
stream copy: True (Section 8)
+===========+=================================================+
| attribute | note |
+===========+=================================================+
| maxOccurs | ContentEncAESSettings MUST NOT be set |
| | (maxOccurs=0) if ContentEncAlgo is not AES (5). |
+-----------+-------------------------------------------------+
Table 27: ContentEncAESSettings implementation notes Implementation Notes
5.1.4.1.31.12. AESSettingsCipherMode Element
id / type: 0x47E8 / uinteger
path: \Segment\Tracks\TrackEntry\ContentEncodings\ContentEncoding\Co
ntentEncryption\ContentEncAESSettings\AESSettingsCipherMode
minOccurs / maxOccurs: 1 / 1
minver: 4
definition: The AES cipher mode used in the encryption.
defined values: See Table 28. Additional values can be registered
in the "AES Cipher Modes" registry defined in Section 27.10.
notes: See Table 29.
stream copy: True (Section 8)
+=======+=========+=====================================+
+=======+=========+===================================+
| value | label | definition |
+=======+=========+=====================================+
+=======+=========+===================================+
| 1 | AES-CTR | Counter [SP.800-38A]. [SP800-38A] |
+-------+---------+-------------------------------------+
+-------+---------+-----------------------------------+
| 2 | AES-CBC | Cipher Block Chaining [SP.800-38A]. [SP800-38A] |
+-------+---------+-------------------------------------+
+-------+---------+-----------------------------------+
Table 28: AESSettingsCipherMode values Values
+===========+=================================================+
| attribute | note |
+===========+=================================================+
| maxOccurs | AESSettingsCipherMode MUST NOT be set |
| | (maxOccurs=0) if ContentEncAlgo is not AES (5). |
+-----------+-------------------------------------------------+
Table 29: AESSettingsCipherMode implementation notes Implementation Notes
5.1.5. Cues Element
id / type: 0x1C53BB6B / master
path: \Segment\Cues
minOccurs / maxOccurs: see implementation notes See Table 30 / 1
definition: A Top-Level Element to speed seeking access. All
entries are local to the Segment.
notes: See Table 30.
+===========+====================================================+
| attribute | note |
+===========+====================================================+
| minOccurs | This Element element SHOULD be set when the Segment is not |
| | transmitted as a live stream; see Section 23.2. |
+-----------+----------------------------------------------------+
Table 30: Cues implementation notes Implementation Notes
5.1.5.1. CuePoint Element
id / type: 0xBB / master
path: \Segment\Cues\CuePoint
minOccurs: 1
definition: Contains all information relative to a seek point in the
Segment.
5.1.5.1.1. CueTime Element
id / type: 0xB3 / uinteger
path: \Segment\Cues\CuePoint\CueTime
minOccurs / maxOccurs: 1 / 1
definition: Absolute timestamp of the seek point, expressed in
Matroska Ticks -- i.e., in nanoseconds;
Segment Ticks, which are based on TimestampScale; see
Section 11.1.
5.1.5.1.2. CueTrackPositions Element
id / type: 0xB7 / master
path: \Segment\Cues\CuePoint\CueTrackPositions
minOccurs: 1
definition: Contain Contains positions for different tracks corresponding to
the timestamp.
5.1.5.1.2.1. CueTrack Element
id / type: 0xF7 / uinteger
range: not 0
path: \Segment\Cues\CuePoint\CueTrackPositions\CueTrack
minOccurs / maxOccurs: 1 / 1
definition: The track for which a position is given.
5.1.5.1.2.2. CueClusterPosition Element
id / type: 0xF1 / uinteger
path: \Segment\Cues\CuePoint\CueTrackPositions\CueClusterPosition
minOccurs / maxOccurs: 1 / 1
definition: The Segment Position (Section 16) of the Cluster
containing the associated Block.
5.1.5.1.2.3. CueRelativePosition Element
id / type: 0xF0 / uinteger
path: \Segment\Cues\CuePoint\CueTrackPositions\CueRelativePosition
maxOccurs: 1
minver: 4
definition: The relative position inside the Cluster of the
referenced SimpleBlock or BlockGroup with 0 being the first
possible position for an Element element inside that Cluster.
5.1.5.1.2.4. CueDuration Element
id / type: 0xB2 / uinteger
path: \Segment\Cues\CuePoint\CueTrackPositions\CueDuration
maxOccurs: 1
minver: 4
definition: The duration of the block, expressed in Segment Ticks Ticks,
which is are based on TimestampScale; see Section 11.1. If missing,
the track's DefaultDuration does not apply and no duration
information is available in terms of the cues.
5.1.5.1.2.5. CueBlockNumber Element
id / type: 0x5378 / uinteger
range: not 0
path: \Segment\Cues\CuePoint\CueTrackPositions\CueBlockNumber
maxOccurs: 1
definition: Number of the Block in the specified Cluster.
5.1.5.1.2.6. CueCodecState Element
id / type / default: 0xEA / uinteger / 0
path: \Segment\Cues\CuePoint\CueTrackPositions\CueCodecState
minOccurs / maxOccurs: 1 / 1
minver: 2
definition: The Segment Position (Section 16) of the Codec State
corresponding to this Cue Element. Cues element. 0 means that the data is taken
from the initial Track Entry. TrackEntry.
5.1.5.1.2.7. CueReference Element
id / type: 0xDB / master
path: \Segment\Cues\CuePoint\CueTrackPositions\CueReference
minver: 2
definition: The Clusters containing the referenced Blocks.
5.1.5.1.2.8. CueRefTime Element
id / type: 0x96 / uinteger
path: \Segment\Cues\CuePoint\CueTrackPositions\CueReference\CueRefTi
me
minOccurs / maxOccurs: 1 / 1
minver: 2
definition: Timestamp of the referenced Block, expressed in Matroska Segment
Ticks -- i.e., in nanoseconds; which is based on TimestampScale; see Section 11.1.
5.1.6. Attachments Element
id / type: 0x1941A469 / master
path: \Segment\Attachments
maxOccurs: 1
definition: Contain Contains attached files.
5.1.6.1. AttachedFile Element
id / type: 0x61A7 / master
path: \Segment\Attachments\AttachedFile
minOccurs: 1
definition: An attached file.
5.1.6.1.1. FileDescription Element
id / type: 0x467E / utf-8
path: \Segment\Attachments\AttachedFile\FileDescription
maxOccurs: 1
definition: A human-friendly name for the attached file.
5.1.6.1.2. FileName Element
id / type: 0x466E / utf-8
path: \Segment\Attachments\AttachedFile\FileName
minOccurs / maxOccurs: 1 / 1
definition: Filename of the attached file.
5.1.6.1.3. FileMediaType Element
id / type: 0x4660 / string
path: \Segment\Attachments\AttachedFile\FileMediaType
minOccurs / maxOccurs: 1 / 1
definition: Media type of the file following the [RFC6838] format. format described in
[RFC6838].
stream copy: True (Section 8)
5.1.6.1.4. FileData Element
id / type: 0x465C / binary
path: \Segment\Attachments\AttachedFile\FileData
minOccurs / maxOccurs: 1 / 1
definition: The data of the file.
stream copy: True (Section 8)
5.1.6.1.5. FileUID Element
id / type: 0x46AE / uinteger
range: not 0
path: \Segment\Attachments\AttachedFile\FileUID
minOccurs / maxOccurs: 1 / 1
definition: Unique ID UID representing the file, as random as possible.
stream copy: True (Section 8)
5.1.7. Chapters Element
id / type: 0x1043A770 / master
path: \Segment\Chapters
maxOccurs: 1
recurring: True
definition: A system to define basic menus and partition data. For
more detailed information, look at the Chapters explanation in see Section 20.
5.1.7.1. EditionEntry Element
id / type: 0x45B9 / master
path: \Segment\Chapters\EditionEntry
minOccurs: 1
definition: Contains all information about a Segment edition.
5.1.7.1.1. EditionUID Element
id / type: 0x45BC / uinteger
range: not 0
path: \Segment\Chapters\EditionEntry\EditionUID
maxOccurs: 1
definition: A unique ID to identify UID that identifies the edition. It's useful for
tagging an edition.
stream copy: True (Section 8)
5.1.7.1.2. EditionFlagDefault Element
id / type / default: 0x45DB / uinteger / 0
range: 0-1
path: \Segment\Chapters\EditionEntry\EditionFlagDefault
minOccurs / maxOccurs: 1 / 1
definition: Set to 1 if the edition SHOULD be used as the default
one.
5.1.7.1.3. EditionFlagOrdered Element
id / type / default: 0x45DD / uinteger / 0
range: 0-1
path: \Segment\Chapters\EditionEntry\EditionFlagOrdered
minOccurs / maxOccurs: 1 / 1
definition: Set to 1 if the chapters can be defined multiple times
and the order to play them is enforced; see Section 20.1.3.
5.1.7.1.4. ChapterAtom Element
id / type: 0xB6 / master
path: \Segment\Chapters\EditionEntry\+ChapterAtom
minOccurs: 1
recursive: True
definition: Contains the atom information to use as the chapter atom
(apply
(applies to all tracks).
5.1.7.1.4.1. ChapterUID Element
id / type: 0x73C4 / uinteger
range: not 0
path: \Segment\Chapters\EditionEntry\+ChapterAtom\ChapterUID
minOccurs / maxOccurs: 1 / 1
definition: A unique ID to identify UID that identifies the Chapter.
stream copy: True (Section 8)
5.1.7.1.4.2. ChapterStringUID Element
id / type: 0x5654 / utf-8
path: \Segment\Chapters\EditionEntry\+ChapterAtom\ChapterStringUID
maxOccurs: 1
minver: 3
definition: A unique string ID to identify that identifies the Chapter. For example
example, it is used as the storage for [WebVTT] cue identifier values. values
[WebVTT].
5.1.7.1.4.3. ChapterTimeStart Element
id / type: 0x91 / uinteger
path: \Segment\Chapters\EditionEntry\+ChapterAtom\ChapterTimeStart
minOccurs / maxOccurs: 1 / 1
definition: Timestamp of the start of Chapter, expressed in Matroska
Ticks -- i.e., in nanoseconds; see Section 11.1.
5.1.7.1.4.4. ChapterTimeEnd Element
id / type: 0x92 / uinteger
path: \Segment\Chapters\EditionEntry\+ChapterAtom\ChapterTimeEnd
minOccurs / maxOccurs: see implementation notes See Table 31 / 1
definition: Timestamp of the end of Chapter timestamp excluded, (timestamp excluded),
expressed in Matroska Ticks -- i.e., in nanoseconds; see
Section 11.1. The value MUST be greater than or equal to the
ChapterTimeStart of the same ChapterAtom.
usage notes: The With the ChapterTimeEnd timestamp value being excluded,
it MUST take in into account the duration of the last frame it
includes, especially for the ChapterAtom using the last frames of
the Segment.
notes: See Table 31.
+===========+====================================================+
| attribute | note |
+===========+====================================================+
| minOccurs | ChapterTimeEnd MUST be set (minOccurs=1) if the |
| | Edition is an ordered edition; see Section 20.1.3, 20.1.3. |
| | unless If it's a Parent Chapter; Chapter, see Section 20.2.3 20.2.3. |
+-----------+----------------------------------------------------+
Table 31: ChapterTimeEnd implementation notes Implementation Notes
5.1.7.1.4.5. ChapterFlagHidden Element
id / type / default: 0x98 / uinteger / 0
range: 0-1
path: \Segment\Chapters\EditionEntry\+ChapterAtom\ChapterFlagHidden
minOccurs / maxOccurs: 1 / 1
definition: Set to 1 if a chapter is hidden. Hidden chapters SHOULD
NOT be available to the user interface (but still be available to
Control Tracks; see Section 20.2.5 on Chapter flags).
5.1.7.1.4.6. ChapterSegmentUUID Element
id / type: 0x6E67 / binary
length: 16
path: \Segment\Chapters\EditionEntry\+ChapterAtom\ChapterSegmentUUID
minOccurs / maxOccurs: see implementation notes See Table 32 / 1
definition: The SegmentUUID of another Segment to play during this
chapter.
usage notes: The value MUST NOT be the SegmentUUID value of the
Segment it belongs to.
notes: See Table 32.
+===========+==============================================+
| attribute | note |
+===========+==============================================+
| minOccurs | ChapterSegmentUUID MUST be set (minOccurs=1) |
| | if ChapterSegmentEditionUID is used; see |
| | Section 17.2 on medium-linking Medium-Linking Segments. |
+-----------+----------------------------------------------+
Table 32: ChapterSegmentUUID implementation notes Implementation Notes
5.1.7.1.4.7. ChapterSegmentEditionUID Element
id / type: 0x6EBC / uinteger
range: not 0
path: \Segment\Chapters\EditionEntry\+ChapterAtom\ChapterSegmentEdit
ionUID
maxOccurs: 1
definition: The EditionUID to play from the Segment linked in
ChapterSegmentUUID. If ChapterSegmentEditionUID is undeclared,
then no Edition of the linked Linked Segment is used; see Section 17.2 on
medium-linking
Medium-Linking Segments.
5.1.7.1.4.8. ChapterPhysicalEquiv Element
id / type: 0x63C3 / uinteger
path: \Segment\Chapters\EditionEntry\+ChapterAtom\ChapterPhysicalEqu
iv
maxOccurs: 1
definition: Specify Specifies the physical equivalent of this ChapterAtom like ChapterAtom,
e.g., "DVD" (60) or "SIDE" (50); see Section 20.4 for a complete
list of values.
5.1.7.1.4.9. ChapterDisplay Element
id / type: 0x80 / master
path: \Segment\Chapters\EditionEntry\+ChapterAtom\ChapterDisplay
definition: Contains all possible strings to use for the chapter
display.
5.1.7.1.4.10. ChapString Element
id / type: 0x85 / utf-8
path: \Segment\Chapters\EditionEntry\+ChapterAtom\ChapterDisplay\Cha
pString
minOccurs / maxOccurs: 1 / 1
definition: Contains the string to use as the chapter atom.
5.1.7.1.4.11. ChapLanguage Element
id / type / default: 0x437C / string / eng
path: \Segment\Chapters\EditionEntry\+ChapterAtom\ChapterDisplay\Cha
pLanguage
minOccurs: 1
definition: A language corresponding to the string, in the Matroska
languages form; see Section 12 on language codes. This Element element
MUST be ignored if a ChapLanguageBCP47 Element element is used within the
same ChapterDisplay Element. element.
5.1.7.1.4.12. ChapLanguageBCP47 Element
id / type: 0x437D / string
path: \Segment\Chapters\EditionEntry\+ChapterAtom\ChapterDisplay\Cha
pLanguageBCP47
minver: 4
definition: A language corresponding to the ChapString, in the
[BCP47] form; form
defined in [RFC5646]; see Section 12 on language codes. If a
ChapLanguageBCP47 Element element is used, then any ChapLanguage and
ChapCountry Elements elements used in the same ChapterDisplay MUST be
ignored.
5.1.7.1.4.13. ChapCountry Element
id / type: 0x437E / string
path: \Segment\Chapters\EditionEntry\+ChapterAtom\ChapterDisplay\Cha
pCountry
definition: A country corresponding to the string, in the Matroska
countries form; see Section 13 on country codes. This Element element
MUST be ignored if a ChapLanguageBCP47 Element element is used within the
same ChapterDisplay Element. element.
5.1.7.1.4.14. ChapProcess Element
id / type: 0x6944 / master
path: \Segment\Chapters\EditionEntry\+ChapterAtom\ChapProcess
definition: Contains all the commands associated to with the Atom.
5.1.7.1.4.15. ChapProcessCodecID Element
id / type / default: 0x6955 / uinteger / 0
path: \Segment\Chapters\EditionEntry\+ChapterAtom\ChapProcess\ChapPr
ocessCodecID
minOccurs / maxOccurs: 1 / 1
definition: Contains the type of the codec used for the processing.
A
defined values: See Table 33. Additional values can be registered
in the "Matroska Chapter Codec IDs" registry defined in
Section 27.2.
+=======+=================+============================+
| value of | label | definition |
+=======+=================+============================+
| 0 means built-in | Matroska processing (to be defined), a
value of Script | Chapter commands using the |
| | | Matroska Script codec. |
+-------+-----------------+----------------------------+
| 1 means | DVD-menu | Chapter commands using the DVD command set is used; see Section 20.3 on
DVD menus. More codec IDs can be added later. |
| | | DVD-like codec. |
+-------+-----------------+----------------------------+
Table 33: ChapProcessCodecID Values
5.1.7.1.4.16. ChapProcessPrivate Element
id / type: 0x450D / binary
path: \Segment\Chapters\EditionEntry\+ChapterAtom\ChapProcess\ChapPr
ocessPrivate
maxOccurs: 1
definition: Some optional Optional data attached to the ChapProcessCodecID
information. For ChapProcessCodecID = 1, it is the "DVD level"
equivalent; see Section 20.3 on DVD menus.
5.1.7.1.4.17. ChapProcessCommand Element
id / type: 0x6911 / master
path: \Segment\Chapters\EditionEntry\+ChapterAtom\ChapProcess\ChapPr
ocessCommand
definition: Contains all the commands associated to with the Atom.
5.1.7.1.4.18. ChapProcessTime Element
id / type: 0x6922 / uinteger
path: \Segment\Chapters\EditionEntry\+ChapterAtom\ChapProcess\ChapPr
ocessCommand\ChapProcessTime
minOccurs / maxOccurs: 1 / 1
definition: Defines when the process command SHOULD be handled handled.
restrictions: See Table 34.
+=======+===============================+
| value | label |
+=======+===============================+
| 0 | during the whole chapter |
+-------+-------------------------------+
| 1 | before starting playback |
+-------+-------------------------------+
| 2 | after playback of the chapter |
+-------+-------------------------------+
Table 33: 34: ChapProcessTime values Values
5.1.7.1.4.19. ChapProcessData Element
id / type: 0x6933 / binary
path: \Segment\Chapters\EditionEntry\+ChapterAtom\ChapProcess\ChapPr
ocessCommand\ChapProcessData
minOccurs / maxOccurs: 1 / 1
definition: Contains the command information. The data SHOULD be
interpreted depending on the ChapProcessCodecID value. For
ChapProcessCodecID = 1, the data correspond to the binary DVD cell
pre/post commands; see Section 20.3 on DVD menus.
5.1.8. Tags Element
id / type: 0x1254C367 / master
path: \Segment\Tags
definition: Element containing metadata describing Tracks, Editions,
Chapters, Attachments, or the Segment as a whole. A list of valid
tags can be found in [MatroskaTags].
5.1.8.1. Tag Element
id / type: 0x7373 / master
path: \Segment\Tags\Tag
minOccurs: 1
definition: A single metadata descriptor.
5.1.8.1.1. Targets Element
id / type: 0x63C0 / master
path: \Segment\Tags\Tag\Targets
minOccurs / maxOccurs: 1 / 1
definition: Specifies which other elements the metadata represented
by the Tag tag value applies to. If empty or omitted, then the Tag tag
value describes everything in the Segment.
5.1.8.1.1.1. TargetTypeValue Element
id / type / default: 0x68CA / uinteger / 50
path: \Segment\Tags\Tag\Targets\TargetTypeValue
minOccurs / maxOccurs: 1 / 1
definition: A number to indicate the logical level of the target.
defined values:
+=======+===================+=================================+ See Table 35. Additional values can be registered
in the "Tags Target Types" registry defined in Section 27.4.
+=======+==========================+================================+
| value | label | definition |
+=======+===================+=================================+
+=======+==========================+================================+
| 70 | COLLECTION | The highest hierarchical level |
| | | that tags can describe. |
+-------+-------------------+---------------------------------+
+-------+--------------------------+--------------------------------+
| 60 | EDITION / ISSUE / | A list of lower levels grouped |
| | VOLUME / OPUS / | together. |
| | SEASON / SEQUEL | |
+-------+-------------------+---------------------------------+
+-------+--------------------------+--------------------------------+
| 50 | ALBUM / OPERA / | The most common grouping level |
| | CONCERT / MOVIE / | of music and video (equals to (e.g., an |
| | EPISODE | an episode for TV series). |
+-------+-------------------+---------------------------------+
+-------+--------------------------+--------------------------------+
| 40 | PART / SESSION | When an album or episode has |
| | | different logical parts. |
+-------+-------------------+---------------------------------+
+-------+--------------------------+--------------------------------+
| 30 | TRACK / SONG / | The common parts of an album or |
| | CHAPTER | or movie. |
+-------+-------------------+---------------------------------+
+-------+--------------------------+--------------------------------+
| 20 | SUBTRACK / | Corresponds to parts of a track |
| | MOVEMENT / SCENE | track for audio like a movement, or audio, such as a |
| | | movement or scene in a movie. |
+-------+-------------------+---------------------------------+
+-------+--------------------------+--------------------------------+
| 10 | SHOT | The lowest hierarchy found in |
| | | music or movies. |
+-------+-------------------+---------------------------------+
+-------+--------------------------+--------------------------------+
Table 34: 35: TargetTypeValue values Values
5.1.8.1.1.2. TargetType Element
id / type: 0x63CA / string
path: \Segment\Tags\Tag\Targets\TargetType
maxOccurs: 1
definition: An informational string that can be used to display the
logical level of the target like target, such as "ALBUM", "TRACK", "MOVIE",
"CHAPTER", etc.
restrictions: See Table 36.
+============+====================+
| value | label |
+============+====================+
| COLLECTION | TargetTypeValue 70 |
+------------+--------------------+
| EDITION | TargetTypeValue 60 |
+------------+--------------------+
| ISSUE | TargetTypeValue 60 |
+------------+--------------------+
| VOLUME | TargetTypeValue 60 |
+------------+--------------------+
| OPUS | TargetTypeValue 60 |
+------------+--------------------+
| SEASON | TargetTypeValue 60 |
+------------+--------------------+
| SEQUEL | TargetTypeValue 60 |
+------------+--------------------+
| ALBUM | TargetTypeValue 50 |
+------------+--------------------+
| OPERA | TargetTypeValue 50 |
+------------+--------------------+
| CONCERT | TargetTypeValue 50 |
+------------+--------------------+
| MOVIE | TargetTypeValue 50 |
+------------+--------------------+
| EPISODE | TargetTypeValue 50 |
+------------+--------------------+
| PART | TargetTypeValue 40 |
+------------+--------------------+
| SESSION | TargetTypeValue 40 |
+------------+--------------------+
| TRACK | TargetTypeValue 30 |
+------------+--------------------+
| SONG | TargetTypeValue 30 |
+------------+--------------------+
| CHAPTER | TargetTypeValue 30 |
+------------+--------------------+
| SUBTRACK | TargetTypeValue 20 |
+------------+--------------------+
| MOVEMENT | TargetTypeValue 20 |
+------------+--------------------+
| SCENE | TargetTypeValue 20 |
+------------+--------------------+
| SHOT | TargetTypeValue 10 |
+------------+--------------------+
Table 35: 36: TargetType values Values
5.1.8.1.1.3. TagTrackUID Element
id / type / default: 0x63C5 / uinteger / 0
path: \Segment\Tags\Tag\Targets\TagTrackUID
definition: A unique ID to identify UID that identifies the Track(s) that the tags belong
to.
usage notes: If the value is 0 at this level, the tags apply to all
tracks in the Segment. If set to any other value, it MUST match
the TrackUID value of a track found in this Segment.
5.1.8.1.1.4. TagEditionUID Element
id / type / default: 0x63C9 / uinteger / 0
path: \Segment\Tags\Tag\Targets\TagEditionUID
definition: A unique ID to identify UID that identifies the EditionEntry(s) that the tags
belong to.
usage notes: If the value is 0 at this level, the tags apply to all
editions in the Segment. If set to any other value, it MUST match
the EditionUID value of an edition found in this Segment.
5.1.8.1.1.5. TagChapterUID Element
id / type / default: 0x63C4 / uinteger / 0
path: \Segment\Tags\Tag\Targets\TagChapterUID
definition: A unique ID to identify UID that identifies the Chapter(s) that the tags
belong to.
usage notes: If the value is 0 at this level, the tags apply to all
chapters in the Segment. If set to any other value, it MUST match
the ChapterUID value of a chapter found in this Segment.
5.1.8.1.1.6. TagAttachmentUID Element
id / type / default: 0x63C6 / uinteger / 0
path: \Segment\Tags\Tag\Targets\TagAttachmentUID
definition: A unique ID to identify UID that identifies the Attachment(s) that the tags
belong to.
usage notes: If the value is 0 at this level, the tags apply to all
the attachments in the Segment. If set to any other value, it
MUST match the FileUID value of an attachment found in this
Segment.
5.1.8.1.2. SimpleTag Element
id / type: 0x67C8 / master
path: \Segment\Tags\Tag\+SimpleTag
minOccurs: 1
recursive: True
definition: Contains general information about the target.
5.1.8.1.2.1. TagName Element
id / type: 0x45A3 / utf-8
path: \Segment\Tags\Tag\+SimpleTag\TagName
minOccurs / maxOccurs: 1 / 1
definition: The name of the Tag tag value that is going to be stored.
5.1.8.1.2.2. TagLanguage Element
id / type / default: 0x447A / string / und
path: \Segment\Tags\Tag\+SimpleTag\TagLanguage
minOccurs / maxOccurs: 1 / 1
definition: Specifies the language of the specified tag specified, in the
Matroska languages form; see Section 12 on language codes. This
Element
element MUST be ignored if the TagLanguageBCP47 Element element is used
within the same SimpleTag Element. element.
5.1.8.1.2.3. TagLanguageBCP47 Element
id / type: 0x447B / string
path: \Segment\Tags\Tag\+SimpleTag\TagLanguageBCP47
maxOccurs: 1
minver: 4
definition: The language used in the TagString, in the [BCP47] form; form defined
in [RFC5646]; see Section 12 on language codes. If this Element element
is used, then any TagLanguage Elements elements used in the same SimpleTag
MUST be ignored.
5.1.8.1.2.4. TagDefault Element
id / type / default: 0x4484 / uinteger / 1
range: 0-1
path: \Segment\Tags\Tag\+SimpleTag\TagDefault
minOccurs / maxOccurs: 1 / 1
definition: A boolean value to indicate if this is the default/
original language to use for the given tag.
5.1.8.1.2.5. TagString Element
id / type: 0x4487 / utf-8
path: \Segment\Tags\Tag\+SimpleTag\TagString
maxOccurs: 1
definition: The value of the Tag. tag value.
5.1.8.1.2.6. TagBinary Element
id / type: 0x4485 / binary
path: \Segment\Tags\Tag\+SimpleTag\TagBinary
maxOccurs: 1
definition: The values of the Tag, tag value if it is binary. Note that this cannot be
used in the same SimpleTag as TagString.
6. Matroska Element Ordering
Except for
With the exceptions of the EBML Header and the CRC-32 Element, element, the
EBML specification [RFC8794] does not require any particular storage
order for
Elements. This elements. However, this specification however defines mandates and
recommendations for ordering certain Elements in order elements to facilitate better
playback, seeking, and editing efficiency. This section describes
and offers rationale for ordering requirements and recommendations
for Matroska.
6.1. Top-Level Elements
The Info Element element is the only REQUIRED Top-Level Element in a Matroska
file. To be playable, Matroska MUST also contain at least one Tracks
Element
element and Cluster Element. element. The first Info Element element and the first
Tracks Element MUST element either MUST be stored before the first Cluster Element element
or both SHALL both be referenced by a SeekHead Element element occurring before
the first Cluster Element. element.
All Top-Level Elements MUST use a 4-octet long EBML Element ID.
When using Medium Linking, chapters are used to reference other
Segments to play in a given order (see Section 17.2. 17.2). A Segment
containing these linked Linked Chapters does not require a Track Element Tracks element or
a Cluster
Element. element.
It is possible to edit a Matroska file after it has been created.
For example, chapters, tags, or attachments can be added. When new
Top-Level Elements are added to a Matroska file, the SeekHead
Element(s)
element(s) MUST be updated so that the SeekHead Element(s) itemize element(s) itemizes
the identity and position of all Top-Level Elements.
Editing, removing, or adding Elements elements to a Matroska file often
requires that some existing Elements elements be voided or extended.
Transforming the existing Elements elements into Void Elements elements as padding can
be used as a method to avoid moving large amounts of data around.
6.2. CRC-32
As noted by the EBML specification, specification [RFC8794], if a CRC-32 Element element is
used, then the CRC-32 Element element MUST be the first ordered Element element
within its Parent Element.
In Matroska Matroska, all Top-Level Elements of an EBML Document SHOULD
include a CRC-32 Element element as their first Child Element. The Segment Element,
element, which is the Root Element, SHOULD NOT have a CRC-32 Element. element.
6.3. SeekHead
If used, the first SeekHead Element element MUST be the first non-CRC-32
Child Element element of the Segment Element. element. If a second SeekHead Element element
is used, then the first SeekHead Element element MUST reference the identity
and position of the second SeekHead. SeekHead element.
Additionally, the second SeekHead Element element MUST only reference Cluster
Elements
elements and not any other Top-Level Element already contained within
the first SeekHead Element. element.
The second SeekHead Element element MAY be stored in any order relative to
the other Top-Level Elements. Whether one or two SeekHead Element(s) elements
are used, the SeekHead Element(s) element(s) MUST collectively reference the
identity and position of all Top-Level Elements except for the first
SeekHead Element. element.
6.4. Cues (index) (Index)
The Cues Element element is RECOMMENDED to optimize seeking access in
Matroska. It is programmatically simpler to add the Cues Element element
after all Cluster Elements elements have been written because this does not
require a prediction of how much space to reserve before writing the
Cluster Elements. elements. However, storing the Cues Element element before the
Cluster Elements elements can provide some seeking advantages. If the Cues
Element
element is present, then it SHOULD either be stored before the first
Cluster Element element or be referenced by a SeekHead Element. element.
6.5. Info
The first Info Element element SHOULD occur before the first Tracks Element element
and first Cluster Element element except when referenced by a SeekHead
Element.
element.
6.6. Chapters Element
The Chapters Element element SHOULD be placed before the Cluster Element(s). element(s).
The Chapters Element element can be used during playback even if the user
does not need to seek. It immediately gives the user information
about what section is being read and what other sections are
available.
In the case of Ordered Chapters Chapters, it is RECOMMENDED to evaluate the
logical linking even before playing. The Chapters
Element element SHOULD be
placed before the first Tracks Element element and after the first Info Element.
element.
6.7. Attachments
The Attachments Element element is not intended to be used by default when
playing the file, file but could contain information relevant to the
content, such as cover art or fonts. Cover art is useful even before
the file is played played, and fonts could be needed before playback starts
for the initialization of subtitles. The Attachments Element element MAY be
placed before the first Cluster Element; element; however, if the Attachments
Element
element is likely to be edited, then it SHOULD be placed after the
last Cluster Element. element.
6.8. Tags
The Tags Element element is most subject to changes after the file was
originally created. For easier editing, the Tags Element element can be
placed at the end of the Segment Element, element, even after the Attachments
Element.
element. On the other hand, it is inconvenient to have to seek in
the Segment for tags, especially for network streams. So streams; thus, it's
better if the Tags Element element is found early in the stream. When
editing the Tags Element, element, the original Tags Element element at the beginning
can be overwritten with a Void Element element and a new Tags Element element written
at the end of the Segment Element. element. The file and Segment sizes will
only marginally change.
7. Matroska versioning Versioning
Matroska is based upon on the principle that a reading application does
not have to support 100% of the specifications in order to be able to
play the file. A Therefore, a Matroska file therefore contains version
indicators that tell a reading application what to expect.
It is possible and valid to have the version fields indicate that the
file contains Matroska Elements elements from a higher specification version
number while signaling that a reading application MUST only support a
lower version number properly in order to play it back (possibly with
a reduced feature set).
The EBML Header of each Matroska document informs the reading
application on what version of Matroska to expect. The Elements elements
within the EBML Header with jurisdiction over this information are
DocTypeVersion and DocTypeReadVersion.
DocTypeVersion MUST be equal to or greater than the highest Matroska
version number of any Element element present in the Matroska file. For
example, a file using the SimpleBlock Element element (Section 5.1.3.4) MUST
have a DocTypeVersion equal to or greater than 2. A file containing
CueRelativePosition Elements elements (Section 5.1.5.1.2.3) MUST have a
DocTypeVersion equal to or greater than 4.
The DocTypeReadVersion MUST contain the minimum version number that a
reading application can minimally support in order to play the file
back -- optionally with a reduced feature set. For example, if a
file contains only Elements elements of version 2 or lower except for
CueRelativePosition (which is a version 4 Matroska Element), element), then
DocTypeReadVersion SHOULD still be set to 2 and not 4 because
evaluating CueRelativePosition is not necessary for standard playback
-- it makes seeking more precise if used.
A reading application supporting Matroska version V MUST NOT refuse
to read a file with DocReadTypeVersion equal to or lower than V V, even
if DocTypeVersion is greater than V.
A reading application supporting at least Matroska version V and
reading a file whose DocTypeReadVersion field is equal to or lower
than V MUST skip Matroska/EBML Elements elements it encounters but does not
know about if that unknown element fits into the size constraints set
by the current Parent Element.
8. Stream Copy
It is sometimes necessary to create a Matroska file from another
Matroska file, for example example, to add subtitles in a language or to edit
out a portion of the content. Some values from the original Matroska
file need to be kept the same in the destination file. For example,
the SamplingFrequency of an audio track wouldn't change between the
two files. Some other values may change between the two files, for
example
example, the TrackNumber of an audio track when another track has
been added.
An Element element is marked with a property: stream property "stream copy: True True" when the
values of that Element element need to be kept identical between the source
and destination file. files. If that property is not set, elements may or
may not keep the same value between the source and destination. destination files.
9. DefaultDecodedFieldDuration
The DefaultDecodedFieldDuration Element element can signal to the displaying
application how often fields of a video sequence will be available
for displaying. It can be used for both interlaced and progressive
content.
If the video sequence is signaled as interlaced Section 5.1.4.1.28.1,
(Section 5.1.4.1.28.1), then DefaultDecodedFieldDuration equals the
period between two successive fields at the output of the decoding
process. For video sequences signaled as progressive,
DefaultDecodedFieldDuration is half of the period between two
successive frames at the output of the decoding process.
These values are valid at the end of the decoding process before
post-processing (such as deinterlacing or inverse telecine) is
applied.
Examples:
* Blu-ray movie: 1000000000 ns/(48/1.001) = 20854167 ns
* PAL broadcast/DVD: 1000000000 ns/(50/1.000) = 20000000 ns
* N/ATSC broadcast: 1000000000 ns/(60/1.001) = 16683333 ns
* hard-telecined Hard-telecined DVD: 1000000000 ns/(60/1.001) = 16683333 ns (60
encoded interlaced fields per second)
* soft-telecined Soft-telecined DVD: 1000000000 ns/(60/1.001) = 16683333 ns (48
encoded interlaced fields per second, with "repeat_first_field =
1")
10. Cluster Blocks
Frames using references SHOULD be stored in "coding order". That
means order" (i.e., the
references first, first and then the frames referencing them. them). A
consequence is that timestamps might not be consecutive. But However, a
frame with a past timestamp MUST reference a frame already known, otherwise
it's known;
otherwise, it is considered bad/void.
Matroska has two similar ways to store frames in a block:
* in a Block which that is contained inside a BlockGroup, BlockGroup
* or in a SimpleBlock which that is directly in the Cluster. Cluster
The SimpleBlock is usually preferred unless some extra elements of
the BlockGroup need to be used. A Matroska Reader MUST support both
types of blocks.
Each block contains the same parts in the following order:
* a variable length header, variable-length header
* optionally the lacing information, information (optional)
* the consecutive frame(s)
The block header starts with the number of the Track it corresponds
to. The value MUST corresponding correspond to the TrackNumber (Section 5.1.4.1.1)
of a TrackEntry of the Segment.
The TrackNumber is coded using the VINT Variable-Size Integer (VINT)
mechanism described in Section 4 of [RFC8794]. To save space, the
shortest VINT form SHOULD be used. The value can be coded on using up
to 8 octets. This is the only element with a variable size in the
block header.
The timestamp is expressed in Track Ticks; see Section 11.1. The
value is stored as a signed value on 16 bits.
10.1. Block Structure
This section describes the binary data contained in the Block Element
Section 5.1.3.5.1. element
(Section 5.1.3.5.1). Bit 0 is the most significant bit.
As the TrackNumber size can vary between 1 and 8 octets, there are 8
different sizes for the Block header. We only provide the The definitions for
TrackNumber sizes of 1 and 2. The 2 are provided; the other variants can be
deduced by extending the size of the TrackNumber by multiples of 8
bits.
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |I|LAC|U|
| Track Number | Timestamp | Rsvrd |N|ING|N|
| | | |V| |U|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 11: Block Header with 1 octet 1-Octet TrackNumber
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Track Number | Timestamp |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |I|LAC|U|
| Rsvrd |N|ING|N| ...
| |V| |U|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 12: Block Header with 2 octets 2-Octet TrackNumber
where:
Track Number: 8, 16, 24, 32, 40, 48 48, or 64 bits
an 56 bits. An EBML VINT coded VINT-coded
track number number.
Timestamp: 16 bits
signed bits. Signed timestamp in Track Ticks Ticks.
Rsvrd: 4 bits bits. Reserved bits MUST be set to 0 0.
INV: 1 bit
Invisible, the bit. Invisible. The codec SHOULD decode this frame but not
display it it.
LACING: 2 bits
using bits. Uses lacing mode
* 00b : mode.
00b: no lacing (Section 10.3.1)
* 01b
01b: : Xiph lacing (Section 10.3.2)
* 11b
11b: : EBML lacing (Section 10.3.3)
* 10b
10b: : fixed-size lacing (Section 10.3.4)
UNU: 1 bit
unused bit bit. Unused bit.
The following remaining data in the Block correspond corresponds to the lacing data and
frames usage as described in each respective lacing mode. mode (see
Section 10.3).
10.2. SimpleBlock Structure
This section describes the binary data contained in the SimpleBlock
Element Section 5.1.3.4.
element (Section 5.1.3.4). Bit 0 is the most significant bit.
The SimpleBlock structure is inspired by the Block structure; see
Section 10.1. The main differences are the added Keyframe flag and
Discardable flag. Otherwise, everything is the same.
As the TrackNumber size can vary between 1 and 8 octets, there are 8
different sizes for the SimpleBlock header. We only provide the The definitions for
TrackNumber sizes of 1 and 2. The 2 are provided; the other variants can be
deduced by extending the size of the TrackNumber by multiples of 8
bits.
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | |K| |I|LAC|D|
| Track Number | Timestamp |E|Rsvrd|N|ING|I|
| | |Y| |V| |S|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 13: SimpleBlock Header with 1 octet 1-Octet TrackNumber
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Track Number | Timestamp |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|K| |I|LAC|D|
|E|Rsvrd|N|ING|I| ...
|Y| |V| |S|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 14: SimpleBlock Header with 2 octets 2-Octet TrackNumber
where:
Track Number: 8, 16, 24, 32, 40, 48 48, or 64 bits
an 56 bits. An EBML VINT coded VINT-coded
track number number.
Timestamp: 16 bits
signed bits. Signed timestamp in Track Ticks Ticks.
KEY: 1 bit
Keyframe, set bit. Keyframe. Set when the Block contains only keyframes keyframes.
Rsvrd: 3 bits bits. Reserved bits MUST be set to 0 0.
INV: 1 bit
Invisible, bit. Invisible; the codec SHOULD decode this frame but not
display it it.
LACING: 2 bits
using bits. Uses lacing mode
* 00b : mode.
00b: no lacing (Section 10.3.1)
* 01b
01b: : Xiph lacing (Section 10.3.2)
* 11b
11b: : EBML lacing (Section 10.3.3)
* 10b
10b: : fixed-size lacing (Section 10.3.4)
DIS: 1 bit
Discardable, the bit. Discardable. The frames of the Block can be discarded
during playing if needed needed.
The following remaining data in the SimpleBlock correspond corresponds to the lacing data
and frames usage as described in each respective lacing mode. mode (see
Section 10.3).
10.3. Block Lacing
Lacing is a mechanism to save space when storing data. It is
typically used for small blocks of data (referred to as frames in
Matroska). It packs multiple frames into a single Block or
SimpleBlock.
Lacing MUST NOT be used to store a single frame in a Block or
SimpleBlock.
There are 3 three types of lacing:
1.
* Xiph, which is inspired by what is found in the Ogg container
[RFC3533]
2.
* EBML, which is the same with sizes coded differently
3. fixed-size,
* Fixed-size, where the size is not coded
When lacing is not used, i.e. i.e., to store a single frame, the lacing
bits (bits 5 and 6 6) of the Block or SimpleBlock MUST be set to zero.
For example, a user wants to store 3 three frames of the same track.
The first frame is 800 octets long, the second is 500 octets long long,
and the third is 1000 octets long. As Because these data frames are small,
they can be stored in a lace to save space.
It is possible not to not use lacing at all and just store a single frame
without any extra data. When the FlagLacing -- Section 5.1.4.1.12 -- (Section 5.1.4.1.12) is
set to "0" 0, all blocks of that track MUST NOT use lacing.
10.3.1. No lacing Lacing
When no lacing is used, the number of frames in the lace is ommitted ommitted,
and only one frame can be stored in the Block. The LACING bits 5-6 of
the Block Header flags are set to 0b00. 00b.
The Block for an 800 octets 800-octet frame is as follows:
+==============+=========+===================+
+=============+=========+===================+
| Block Octets Octet | Value | Description |
+==============+=========+===================+
+=============+=========+===================+
| 4-803 | <frame> | Single frame data |
+--------------+---------+-------------------+
+-------------+---------+-------------------+
Table 36: 37: No lacing Lacing
When a Block contains a single frame, it MUST use this No lacing "no lacing"
mode.
10.3.2. Xiph lacing Lacing
The Xiph lacing uses the same coding of size as found in the Ogg
container [RFC3533]. The LACING bits 5-6 of the Block Header flags are
set to 0b01. 01b.
The Block data with laced frames is stored as follows:
* Lacing Head on 1 Octet: Number of frames in the lace minus 1.
* Lacing size of each frame except the last one.
* Binary data of each frame consecutively.
The lacing size is split into 255 values, stored as unsigned octets
-- for example, 500 is coded 255;245 or [0xFF 0xF5]. A frame with a
size multiple of 255 is coded with a 0 at the end of the size -- for
example, 765 is coded 255;255;255;0 or [0xFF 0xFF 0xFF 0x00].
The size of the last frame is deduced from the size remaining in the
Block after the other frames.
Because large sizes result in large coding of the sizes, it is
RECOMMENDED to use Xiph lacing only with small frames.
In our example, the 800, 500 800-, 500-, and 1000 1000-octet frames are stored with
Xiph lacing in a Block as follows:
+=============+=====================+==========================+
+==============+=====================+==========================+
| Block Octet Octets | Value | Description |
+=============+=====================+==========================+
+==============+=====================+==========================+
| 4 | 0x02 | Number of frames minus 1 |
+-------------+---------------------+--------------------------+
+--------------+---------------------+--------------------------+
| 5-8 | 0xFF 0xFF 0xFF 0x23 | Size of the first frame |
| | | (255;255;255;35) |
+-------------+---------------------+--------------------------+
+--------------+---------------------+--------------------------+
| 9-10 | 0xFF 0xF5 | Size of the second frame |
| | | (255;245) |
+-------------+---------------------+--------------------------+
+--------------+---------------------+--------------------------+
| 11-810 | | First frame data |
+-------------+---------------------+--------------------------+
+--------------+---------------------+--------------------------+
| 811-1310 | | Second frame data |
+-------------+---------------------+--------------------------+
+--------------+---------------------+--------------------------+
| 1311-2310 | | Third frame data |
+-------------+---------------------+--------------------------+
+--------------+---------------------+--------------------------+
Table 37: 38: Xiph lacing example Lacing Example
The Block is 2311 octets large octets, and the last frame starts at 1311, so we
can deduce that the size of the last frame is 2311 - 1311 = 1000.
10.3.3. EBML lacing Lacing
The EBML lacing encodes the frame size with an EBML-like encoding
[RFC8794]. The LACING bits 5-6 of the Block Header flags are set to 0b11. 11b.
The Block data with laced frames is stored as follows:
* Lacing Head on 1 Octet: Number of frames in the lace minus 1.
* Lacing size of each frame except the last one.
* Binary data of each frame consecutively.
The first frame size is encoded as an EBML Variable-Size Integer
value, also known as VINT in [RFC8794]. value. The remaining
frame sizes are encoded as signed values using the difference between
the frame size and the previous frame size. These signed values are
encoded as VINT, with a mapping from signed to unsigned numbers.
Decoding the unsigned number stored in the VINT to a signed number is
done by subtracting 2^((7*n)-1)-1, where n is the octet size of the
VINT.
+===================================+======================+
| Bit Representation of signed Signed VINT | Possible Value Range |
+===================================+======================+
| 1xxx xxxx | 2^7 values from |
| | -(2^6-1) to 2^6 |
+-----------------------------------+----------------------+
| 01xx xxxx xxxx xxxx | 2^14 values from |
| | -(2^13-1) to 2^13 |
+-----------------------------------+----------------------+
| 001x xxxx xxxx xxxx xxxx xxxx | 2^21 values from |
| | -(2^20-1) to 2^20 |
+-----------------------------------+----------------------+
| 0001 xxxx xxxx xxxx xxxx xxxx | 2^28 values from |
| xxxx xxxx | -(2^27-1) to 2^27 |
+-----------------------------------+----------------------+
| 0000 1xxx xxxx xxxx xxxx xxxx | 2^35 values from |
| xxxx xxxx xxxx xxxx | -(2^34-1) to 2^34 |
+-----------------------------------+----------------------+
Table 38: 39: EBML Lacing signed Signed VINT bits usage Bits Usage
In our example, the 800, 500 800-, 500-, and 1000 1000-octet frames are stored with
EBML lacing in a Block as follows:
+==============+===========+=====================================+
| Block Octets | Value | Description |
+==============+===========+=====================================+
| 4 | 0x02 | Number of frames minus 1 |
+--------------+-----------+-------------------------------------+
| 5-6 | 0x43 0x20 | Size of the first frame (800 = |
| | | 0x320 + 0x4000) |
+--------------+-----------+-------------------------------------+
| 7-8 | 0x5E 0xD3 | Size of the second frame (500 - 800 |
| | | = -300 = - 0x12C + 0x1FFF + 0x4000) |
+--------------+-----------+-------------------------------------+
| 8-807 | <frame1> | First frame data |
+--------------+-----------+-------------------------------------+
| 808-1307 | <frame2> | Second frame data |
+--------------+-----------+-------------------------------------+
| 1308-2307 | <frame3> | Third frame data |
+--------------+-----------+-------------------------------------+
Table 39: 40: EBML lacing example Lacing Example
The Block is 2308 octets large octets, and the last frame starts at 1308, so we
can deduce that the size of the last frame is 2308 - 1308 = 1000.
10.3.4. Fixed-size lacing
The Lacing
Fixed-size lacing doesn't store the frame size, size; rather, it only
stores the number of frames in the lace. Each frame MUST have the
same size. The frame size of each frame is deduced from the total
size of the Block. The LACING bits 5-6 of the Block Header flags are set
to 0b10. 10b.
The Block data with laced frames is stored as follows:
* Lacing Head on 1 Octet: Number of frames in the lace minus 1.
* Binary data of each frame consecutively.
For example, for 3 three frames of that are 800 octets each:
+==============+==========+==========================+
| Block Octets | Value | Description |
+==============+==========+==========================+
| 4 | 0x02 | Number of frames minus 1 |
+--------------+----------+--------------------------+
| 5-804 | <frame1> | First frame data |
+--------------+----------+--------------------------+
| 805-1604 | <frame2> | Second frame data |
+--------------+----------+--------------------------+
| 1605-2404 | <frame3> | Third frame data |
+--------------+----------+--------------------------+
Table 40: Fixed-size lacing example 41: Fixed-Size Lacing Example
This gives a Block of 2405 octets. When reading the Block Block, we find
that there are 3 three frames (Octet 4). The data start at Octet 5, so
the size of each frame is (2405 - 5) / 3 = 800.
10.3.5. Laced Frames Timestamp
A Block only contains a single timestamp value. But when lacing is
used, it contains more than one frame. Each frame originally has its
own timestamp, or Presentation Timestamp (PTS). That timestamp
applies to the first frame in the lace.
In the lace, each frame after the first one has an underdetermined
timestamp. But However, each of these frames MUST be contiguous -- i.e. i.e.,
the decoded data MUST NOT contain any gap between them. If there is
a gap in the stream, the frames around the gap MUST NOT be in the
same Block.
Lacing is only useful for small contiguous data to save space. This
is usually the case for audio tracks and not the case for video --
which
(which use a lot of data -- data) or subtitle tracks -- which (which have long
gaps. gaps).
For audio, there is usually a fixed output sampling frequency for the
whole track. So track, so the decoder should be able to recover the timestamp
of each sample, knowing each output sample is contiguous with a fixed
frequency. For subtitles subtitles, this is usually not the case case, so lacing
SHOULD NOT be used.
10.4. Random Access Points
Random Access Points (RAP) (RAPs) are positions where the parser can seek
to and start playback without decoding of what was before. In Matroska Matroska,
BlockGroups and SimpleBlocks can be RAPs. To seek to these elements elements,
it is still necessary to seek to the Cluster containing them, read
the Cluster Timestamp Timestamp, and start playback from the BlockGroup or
SimpleBlock that is a RAP.
Because a Matroska File is usually composed of multiple tracks
playing at the same time -- video, audio audio, and subtitles -- to seek
properly to a RAP, each selected track must be taken in into account.
Usually
Usually, all audio and subtitle BlockGroup BlockGroups or SimpleBlock SimpleBlocks are RAP. RAPs.
They are independent of each other and can be played randomly.
Video tracks on
On the other hand hand, video tracks often use references to previous and
future frames for better coding efficiency. Frames with such
reference
references MUST either contain one or more ReferenceBlock Elements elements in
their BlockGroup or MUST be marked as non-keyframe in a SimpleBlock;
see Section 10.2.
* BlockGroup with a frame that references another frame, with the
EBML tree shown as XML:
<Cluster>
<Timestamp>123456</Timestamp>
<BlockGroup>
<!-- References a Block 40 Track Ticks before this one -->
<ReferenceBlock>-40</ReferenceBlock>
<Block/>
</BlockGroup>
...
</Cluster>
* SimpleBlock
Figure 15: BlockGroup with a frame that references another frame, Frame That References Another Frame,
with the EBML tree shown Tree Shown as XML: XML
<Cluster>
<Timestamp>123456</Timestamp>
<SimpleBlock/> (octet 3 bit 0 not set)
...
</Cluster>
Figure 16: SimpleBlock with a Frame That References Another
Frame, with the EBML Tree Shown as XML
Frames that are RAP -- i.e. they RAPs (i.e., frames that don't depend on other frames -- frames)
MUST set the keyframe flag if they are in a SimpleBlock or their
parent BlockGroup MUST NOT contain a ReferenceBlock.
* BlockGroup with a frame that references no other frame, with the
EBML tree shown as XML:
<Cluster>
<Timestamp>123456</Timestamp>
<BlockGroup>
<!-- No ReferenceBlock allowed in this BlockGroup -->
<Block/>
</BlockGroup>
...
</Cluster>
* SimpleBlock
Figure 17: BlockGroup with a frame that references no other frame, Frame That References No Other
Frame, with the EBML tree shown Tree Shown as XML: XML
<Cluster>
<Timestamp>123456</Timestamp>
<SimpleBlock/> (octet 3 bit 0 set)
...
</Cluster>
Figure 18: SimpleBlock with a Frame That References No Other
Frame, with the EBML Tree Shown as XML
There may be cases where the use of BlockGroup is necessary, as the
frame may need a BlockDuration, BlockAdditions, CodecState CodecState, or a
DiscardPadding element. For thoses cases those cases, a SimpleBlock MUST NOT be
used,
used; the reference information SHOULD be recovered for non-RAP
frames.
* SimpleBlock with a frame that references another frame, with the
EBML tree shown as XML:
<Cluster>
<Timestamp>123456</Timestamp>
<SimpleBlock/> (octet 3 bit 0 not set)
...
</Cluster>
* Same frame that references another frame put inside
Figure 19: SimpleBlock with a BlockGroup
to add BlockDuration, Frame That References Another
Frame, with the EBML tree shown Tree Shown as XML: XML
<Cluster>
<Timestamp>123456</Timestamp>
<BlockGroup>
<!-- ReferenceBlock value recovered based on the codec -->
<ReferenceBlock>-40</ReferenceBlock>
<BlockDuration>20<BlockDuration>
<BlockDuration>20</BlockDuration>
<Block/>
</BlockGroup>
...
</Cluster>
Figure 20: Same Frame That References Another Frame Put inside a
BlockGroup to Add BlockDuration, with the EBML Tree Shown as XML
When a frame in a BlockGroup is not a RAP, the BlockGroup MUST
contain at least a ReferenceBlock. The ReferenceBlocks MUST be used
in one of the following ways:
* each reference frame listed as a ReferenceBlock,
* some referenced frame frames listed as a ReferenceBlock, even if the
timestamp value is accurate,
* or
* one ReferenceBlock with the timestamp value "0" corresponding to a
self or unknown reference.
The lack of ReferenceBlock would mean such a frame is a RAP RAP, and
seeking on that frame that actually depends on other frames may
create a bogus output or even crash.
* Same frame that references another frame put inside a BlockGroup
but the reference could not be recovered, with the EBML tree shown
as XML:
<Cluster>
<Timestamp>123456</Timestamp>
<BlockGroup>
<!-- ReferenceBlock value not recovered from the codec -->
<ReferenceBlock>0</ReferenceBlock>
<BlockDuration>20<BlockDuration>
<BlockDuration>20</BlockDuration>
<Block/>
</BlockGroup>
...
</Cluster>
* BlockGroup with
Figure 21: Same Frame That References Another Frame Put inside a frame that references two other frames,
BlockGroup, but the Reference Could Not Be Recovered, with the
EBML tree shown Tree Shown as XML: XML
<Cluster>
<Timestamp>123456</Timestamp>
<BlockGroup>
<!-- References a Block 80 Track Ticks before this one -->
<ReferenceBlock>-80</ReferenceBlock>
<!-- References a Block 40 Track Ticks after this one -->
<ReferenceBlock>40</ReferenceBlock>
<Block/>
</BlockGroup>
...
</Cluster>
Figure 22: BlockGroup with a Frame That References Two Other
Frames, with the EBML Tree Shown as XML
Intra-only video frames, such as the ones found in AV1 or VP9, can be
decoded without any other frame, but they don't reset the codec
state. So Thus, seeking to these frames is not possible possible, as the next
frames may need frames that are not known from this seeking point.
Such intra-only frames MUST NOT be considered as keyframes keyframes, so the
keyframe flag MUST NOT be set in the SimpleBlock or a ReferenceBlock
MUST be used to signify the frame is not a RAP. The timestamp value
of the ReferenceBlock MUST be "0", meaning it's referencing itself.
* Intra-only frame not an RAP, with the EBML tree shown as XML:
<Cluster>
<Timestamp>123456</Timestamp>
<BlockGroup>
<!-- References itself to mark it should not be used as RAP -->
<ReferenceBlock>0</ReferenceBlock>
<Block/>
</BlockGroup>
...
</Cluster>
Figure 23: Intra-Only Frame (Not a RAP), with the EBML Tree Shown
as XML
Because a video SimpleBlock has less references information on references than a
video BlockGroup, it is possible to remux a video track using
BlockGroup into a SimpleBlock, as long as it doesn't use any other
BlockGroup features than ReferenceBlock.
11. Timestamps
Historically
Historically, timestamps in Matroska were mistakenly called
timecodes. The Timestamp Element element was called Timecode, the
TimestampScale Element element was called TimecodeScale, the
TrackTimestampScale Element element was called
TrackTimecodeScale TrackTimecodeScale, and the
ReferenceTimestamp Element element was called ReferenceTimeCode.
11.1. Timestamp Ticks
All timestamp values in Matroska are expressed in multiples of a
tick. They are usually stored as integers. There are three types of
ticks possible: Matroska Ticks, Segment Ticks, and Track Ticks.
11.1.1. Matroska Ticks
For such elements, the
The timestamp value is stored directly in nanoseconds.
The elements storing values in Matroska Ticks/nanoseconds are:
* TrackEntry\DefaultDuration; defined in Section 5.1.4.1.13
* TrackEntry\DefaultDecodedFieldDuration; defined in
Section 5.1.4.1.14
* TrackEntry\SeekPreRoll; defined in Section 5.1.4.1.26
* TrackEntry\CodecDelay; defined in Section 5.1.4.1.25
* BlockGroup\DiscardPadding; defined in Section 5.1.3.5.7
* ChapterAtom\ChapterTimeStart; defined in Section 5.1.7.1.4.3
* ChapterAtom\ChapterTimeEnd; defined in Section 5.1.7.1.4.4
* CuePoint\CueTime; defined in Section 5.1.5.1.1
* CueReference\CueRefTime; defined in Section 5.1.5.1.1
11.1.2. Segment Ticks
Elements in Segment Ticks involve the use of the TimestampScale
Element
element of the Segment to get the timestamp in nanoseconds of the
element, with the following formula:
timestamp in nanosecond = element value * TimestampScale
This allows storing for storage of smaller integer values in the elements.
When using the default value of TimestampScale of "1,000,000", "1,000,000" for TimestampScale, one
Segment Tick represents one millisecond.
The elements storing values in Segment Ticks are:
* Cluster\Timestamp; defined in Section 5.1.3.1
* Info\Duration is stored as a floating-point floating-point, but the same formula
applies; defined in Section 5.1.2.10
* CuePoint\CueTime; defined in Section 5.1.5.1.1
* CuePoint\CueTrackPositions\CueDuration; defined in
Section 5.1.5.1.2.4
* CueReference\CueRefTime; defined in Section 5.1.5.1.1
11.1.3. Track Ticks
Elements in Track Ticks involve the use of the TimestampScale Element element
of the Segment and the TrackTimestampScale Element element of the Track to
get the timestamp in nanoseconds of the element, with the following
formula:
timestamp in nanoseconds =
element value * TrackTimestampScale * TimestampScale
This allows storing for storage of smaller integer values in the elements.
The resulting floating-point values of the timestamps are still
expressed in nanoseconds.
When using the default values for TimestampScale and
TrackTimestampScale of "1,000,000" for TimestampScale and of
"1.0" respectively, for TrackTimestampScale, one Track Tick represents one
millisecond.
The elements storing values in Track Ticks are:
* Cluster\BlockGroup\Block and Cluster\SimpleBlock timestamps;
detailed in Section 11.2
* Cluster\BlockGroup\BlockDuration; defined in Section 5.1.3.5.3
* Cluster\BlockGroup\ReferenceBlock; defined in Section 5.1.3.5.5
When the TrackTimestampScale is interpreted as "1.0", Track Ticks are
equivalent to Segment Ticks and give an integer value in nanoseconds.
This is the most common case as TrackTimestampScale is usually
omitted.
A value of TrackTimestampScale other than "1.0" MAY be used to scale
the timestamps more in tune with each Track sampling frequency. For
historical reasons, a lot of Matroska readers Readers don't take the
TrackTimestampScale value in into account. So Thus, using a value other
than "1.0" might not work in many places.
11.2. Block Timestamps
A Block Element element and SimpleBlock Element element timestamp is the time when
the decoded data of the first frame in the Block/SimpleBlock MUST be
presented,
presented if the track of that Block/SimpleBlock is selected for
playback. This is also known as the Presentation Timestamp (PTS).
The Block Element element and SimpleBlock Element element store their timestamps as
signed integers, relative to the Cluster\Timestamp value of the
Cluster they are stored in. To get the timestamp of a Block or
SimpleBlock in nanoseconds you have to use nanoseconds, the following formula: formula is used:
( Cluster\Timestamp + ( block timestamp * TrackTimestampScale ) ) *
TimestampScale
The Block Element element and SimpleBlock Element element store their timestamps as
16bit
16-bit signed integers, allowing a range from "-32768" to "+32767"
Track Ticks. Although these values can be negative, when added to
the Cluster\Timestamp, the resulting frame timestamp SHOULD NOT be
negative.
When a CodecDelay Element element is set, its value MUST be substracted from
each Block timestamp of that track. To get the timestamp in
nanoseconds of the first frame in a Block or SimpleBlock, the formula
becomes:
( ( Cluster\Timestamp + ( block timestamp * TrackTimestampScale ) ) *
TimestampScale ) - CodecDelay
The resulting frame timestamp SHOULD NOT be negative.
During playback, when a frame has a negative timestamp, the content
MUST be decoded by the decoder but not played to the user.
11.3. TimestampScale Rounding
The default Track Tick duration is one millisecond.
The TimestampScale is a floating-point value, which value that is usually 1.0. "1.0".
But when it's not, the multiplied Block Timestamp is a floating-point
value in nanoseconds. The Matroska Reader SHOULD use the nearest
rounding value in nanosecond nanoseconds to get the proper nanosecond timestamp
of a Block. This allows some clever TimestampScale values to have a
more refined timestamp precision per frame.
12. Language Codes
Matroska from version versions 1 through 3 uses use language codes that can be either
the 3 letters three-letter bibliographic ISO-639-2 ISO 639-2 form [ISO639-2] (like "fre"
for French), French) or such a language code followed by a dash and a country
code for specialities in languages (like "fre-ca" for Canadian
French). The ISO 639-2 Language Elements elements are "Language
Element", "TagLanguage Element", Language element,
TagLanguage element, and "ChapLanguage Element". ChapLanguage element.
Starting in Matroska version 4, the forms defined in either
[ISO639-2] or [BCP47] [RFC5646] MAY be used, although BCP 47 the form in [RFC5646]
is RECOMMENDED. The BCP 47 Language Elements elements in the [RFC5646] form are "LanguageBCP47 Element", "TagLanguageBCP47 Element",
LanguageBCP47 element, TagLanguageBCP47 element, and
"ChapLanguageBCP47 Element".
ChapLanguageBCP47 element. If a BCP 47 both an [ISO639-2] Language Element element
and an ISO
639-2 [RFC5646] Language Element element are used within the same Parent
Element, then the ISO 639-2 Language Element element in the [ISO639-2] form MUST be
ignored and precedence given to the BCP 47 Language Element. element in the [RFC5646]
form.
In this document, "BCP47" in element names refers specifically to
[RFC5646], which is part of BCP 47.
13. Country Codes
Country codes are the [BCP47] [RFC5646] two-letter region subtag, subtags, without
the UK exception.
14. Encryption
This Matroska specification provides no interoperable solution for
securing the data container with any assurances of confidentiality,
integrity, authenticity, or to provide authorization. The ContentEncryption Element
element (Section 5.1.4.1.31.8) and associated sub-
fields sub-fields
(Section 5.1.4.1.31.9 to Section 5.1.4.1.31.12) are defined only for
the benefit of implementers to construct their own proprietary
solution or as the basis for further standardization activities. How
to use these fields to secure a Matroska data container is out of
scope, as are any related issues such as key management and
distribution.
A Matroska Reader who encounters containers that use the fields
defined in this section MUST rely on out-of-scope guidance to decode
the associated content.
Because encryption occurs within the Block Element, element, it is possible to
manipulate encrypted streams without decrypting them. The streams
could potentially be copied, deleted, cut, appended, or any number of
other possible editing techniques without decryption. The data can
be used without having to expose it or go through the decrypting
process.
Encryption can also be layered within Matroska. This means that two
completely different types of encryption can be used, requiring two
separate keys to be able to decrypt a stream.
Encryption information is stored in the ContentEncodings Element element
under the ContentEncryption Element. element.
For encryption systems sharing public/private keys, the creation of
the keys and the exchange of keys are not covered by this document.
They have to be handled by the system using Matroska.
The algorithms described in Table 26 support different modes of
operations and key sizes. The specification of these parameters is
required for a complete solution, solution but is out of scope of this document
and left to the proprietary implementations using them or subsequent
profiles of this document.
The ContentEncodingScope Element element gives an idea of which part of the
track are encrypted. But is encrypted, but each ContentEncAlgo Element element and its sub sub-
elements like AESSettingsCipherMode really (like AESSettingsCipherMode) define exactly how the
encrypted track should be exactly interpreted.
An example of an extension that builds upon these security-related
fields in this specification is [WebM-Enc]. It uses AES-CTR,
ContentEncAlgo = 5 (Section 5.1.4.1.31.9) 5.1.4.1.31.9), and AESSettingsCipherMode
= 1 (Section 5.1.4.1.31.12).
A Matroska Writer MUST NOT use insecure cryptographic algorithms to
create new archives or streams, but a Matroska Reader MAY support
these algorithms to read previously made archives or stream. streams.
15. Image Presentation
15.1. Cropping
The PixelCrop Elements elements (PixelCropTop, PixelCropBottom,
PixelCropRight, and PixelCropLeft) indicate when, and by how much,
encoded videos video frames SHOULD be cropped for display. These Elements elements
allow edges of the frame that are not intended for display, such display (such as
the sprockets of a full-frame film scan or the VANC Video ANCillary (VANC)
area of a digitized analog videotape, videotape) to be stored but hidden.
PixelCropTop and PixelCropBottom store an integer of how many rows of
pixels SHOULD be cropped from the top and bottom of the image
(respectively). image,
respectively. PixelCropLeft and PixelCropRight store an integer of
how many columns of pixels SHOULD be cropped from the left and right
of the image (respectively). image, respectively.
For example, a pillar-boxed video that stores a 1440x1080 visual
image within the center of a padded 1920x1080 encoded image may set
both PixelCropLeft and PixelCropRight to "240", so that a Matroska Player
should crop off 240 columns of pixels from the left and right of the
encoded image to present the image with the pillar-boxes hidden.
Cropping has to be performed before resizing and the display
dimensions given by DisplayWidth, DisplayHeight DisplayHeight, and DisplayUnit
apply to the already cropped already-cropped image.
15.2. Rotation
The ProjectionPoseRoll Element (see Section element (Section 5.1.4.1.28.46) can be used to
indicate that the image from the associated video track SHOULD be
rotated for presentation. For instance, the following
representation example of the
Projection Element Section element (Section 5.1.4.1.28.41) and the ProjectionPoseRoll Element
element represents a video track where the image SHOULD be presented
with a 90-degree counter-clockwise rotation, with the EBML tree shown
as XML : XML:
<Projection>
<ProjectionPoseRoll>90</ProjectionPoseRoll>
</Projection>
Figure 15: 24: Rotation example. Example
16. Segment Position
The Segment Position of an Element element refers to the position of the
first octet of the Element ID of that Element, element, measured in octets,
from the beginning of the Element Data section of the containing
Segment Element. element. In other words, the Segment Position of an Element element
is the distance in octets from the beginning of its containing
Segment Element element minus the size of the Element ID and Element Data
Size of that Segment Element. element. The Segment Position of the first
Child Element of the Segment Element element is 0. An Element which element that is not
stored within a Segment Element, element, such as the Elements elements of the EBML
Header, do not have a Segment Position.
16.1. Segment Position Exception
Elements that are defined to store a Segment Position MAY define
reserved values to indicate a special meaning.
16.2. Example of Segment Position
This table presents an example of Segment Position by showing a
hexadecimal representation of a very small Matroska file with labels
to show the offsets in octets. The file contains a Segment Element element
with an Element ID of "0x18538067" and a MuxingApp Element element with an
Element ID of "0x4D80".
0 1 2
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
0 |1A|45|DF|A3|8B|42|82|88|6D|61|74|72|6F|73|6B|61|
^ EBML Header
0 | |18|53|80|67|
^ Segment ID
20 |93|
^ Segment Data Size
20 | |15|49|A9|66|8E|4D|80|84|69|65|74|66|57|41|84|69|65|74|66|
^ Start of Segment data
20 | |4D|80|84|69|65|74|66|57|41|84|69|65|74|66|
^ MuxingApp start
In the above example, the Element ID of the Segment Element element is stored
at offset 16, the Element Data Size of the Segment Element element is stored
at offset 20, and the Element Data of the Segment Element element is stored
at offset 21.
The MuxingApp Element element is stored at offset 26. Since the Segment
Position of an Element element is calculated by subtracting the position of
the Element Data of the containing Segment Element element from the position
of that Element, element, the Segment Position of the MuxingApp Element element in the
above example is '26 "26 - 21' 21" or '5'. "5".
17. Linked Segments
Matroska provides several methods to link two or more Segment
Elements
elements together to create a Linked Segment. A Linked Segment is a
set of multiple Segments linked together into a single presentation
by using Hard Linking or Medium Linking.
All Segments within a Linked Segment MUST have a SegmentUUID.
All Segments within a Linked Segment SHOULD be stored within the same
directory or be accessible quickly accessible based on their SegmentUUID in
order to have a seamless transition between segments.
All Segments within a Linked Segment MAY set a SegmentFamily with a
common value to make it easier for a Matroska Player to know which
Segments are meant to be played together.
The SegmentFilename, PrevFilename PrevFilename, and NextFilename elements MAY also
give hints on the original filenames that were used when the Segment
links were created, in case some SegmentUUID SegmentUUIDs are damaged.
17.1. Hard Linking
Hard Linking, also called splitting, "splitting", is the process of creating a
Linked Segment by linking multiple Segment Elements elements using the
NextUUID and PrevUUID Elements. elements.
All Segments within a Hard Linked Segment MUST use the same Tracks
list and TimestampScale.
Within a Linked Segment, the timestamps of Block and SimpleBlock MUST
follow
consecutively follow the timestamps of Block and SimpleBlock from the
previous Segment in linking order.
With Hard Linking, the chapters of any Segment within the Linked
Segment MUST only reference the current Segment. The NextUUID and
PrevUUID reference the respective SegmentUUID values of the next and
previous Segments.
The first Segment of a Linked Segment MUST NOT have a PrevUUID
Element.
element. The last Segment of a Linked Segment MUST NOT have a
NextUUID Element. element.
For each node of the chain of Segments of a Linked Segment Segment, at least
one Segment MUST reference the other Segment within the chain.
In a chain of Segments of a Linked Segment Segment, the NextUUID always takes
precedence over the PrevUUID. So Thus, if SegmentA has a NextUUID to
SegmentB and SegmentB has a PrevUUID to SegmentC, the link to use is
NextUUID between SegmentA and SegmentB, and SegmentC is not part of
the Linked Segment.
If SegmentB has a PrevUUID to SegmentA SegmentA, but SegmentA has no NextUUID,
then the Matroska Player MAY consider these two Segments linked as
SegmentA followed by SegmentB.
As an example, three Segments can be Hard Linked as a Linked Segment
through cross-referencing each other with SegmentUUID, PrevUUID, and
NextUUID,
NextUUID as shown in this table:
+==========+================+==================+==================+
|file name |SegmentUUID | PrevUUID | NextUUID |
+==========+================+==================+==================+
|start.mkv |71000c23cd310998| Invalid | a77b3598941cb803 |
| |53fbc94dd984a5dd| | eac0fcdafe44fac9 |
+----------+----------------+------------------+------------------+
|middle.mkv|a77b3598941cb803| 71000c23cd310998 | 6c92285fa6d3e827 |
| |eac0fcdafe44fac9| 53fbc94dd984a5dd | b198d120ea3ac674 |
+----------+----------------+------------------+------------------+
|end.mkv |6c92285fa6d3e827| a77b3598941cb803 | Invalid |
| |b198d120ea3ac674| eac0fcdafe44fac9 | |
+----------+----------------+------------------+------------------+
Table 41: 42: Usual Hard Linking UIDs
An other example where only the NextUUID Element element is used:
+============+==================+==========+==================+
| file name | SegmentUUID | PrevUUID | NextUUID |
+============+==================+==========+==================+
| start.mkv | 71000c23cd310998 | Invalid | a77b3598941cb803 |
| | 53fbc94dd984a5dd | | eac0fcdafe44fac9 |
+------------+------------------+----------+------------------+
| middle.mkv | a77b3598941cb803 | n/a | 6c92285fa6d3e827 |
| | eac0fcdafe44fac9 | | b198d120ea3ac674 |
+------------+------------------+----------+------------------+
| end.mkv | 6c92285fa6d3e827 | n/a | Invalid |
| | b198d120ea3ac674 | | |
+------------+------------------+----------+------------------+
Table 42: 43: Hard Linking without PrevUUID
An example where only the PrevUUID Element element is used:
+============+==================+==================+==========+
| file name | SegmentUUID | PrevUUID | NextUUID |
+============+==================+==================+==========+
| start.mkv | 71000c23cd310998 | Invalid | n/a |
| | 53fbc94dd984a5dd | | |
+------------+------------------+------------------+----------+
| middle.mkv | a77b3598941cb803 | 71000c23cd310998 | n/a |
| | eac0fcdafe44fac9 | 53fbc94dd984a5dd | |
+------------+------------------+------------------+----------+
| end.mkv | 6c92285fa6d3e827 | a77b3598941cb803 | Invalid |
| | b198d120ea3ac674 | eac0fcdafe44fac9 | |
+------------+------------------+------------------+----------+
Table 43: 44: Hard Linking without NextUUID
In this
An example where only the middle.mkv is using the PrevUUID and
NextUUID Elements: elements:
+==========+================+==================+==================+
|file name |SegmentUUID | PrevUUID | NextUUID |
+==========+================+==================+==================+
|start.mkv |71000c23cd310998| Invalid | n/a |
| |53fbc94dd984a5dd| | |
+----------+----------------+------------------+------------------+
|middle.mkv|a77b3598941cb803| 71000c23cd310998 | 6c92285fa6d3e827 |
| |eac0fcdafe44fac9| 53fbc94dd984a5dd | b198d120ea3ac674 |
+----------+----------------+------------------+------------------+
|end.mkv |6c92285fa6d3e827| n/a | Invalid |
| |b198d120ea3ac674| | |
+----------+----------------+------------------+------------------+
Table 44: 45: Hard Linking with mixed Mixed UID links Links
17.2. Medium Linking
Medium Linking creates relationships between Segments using Ordered
Chapters (Section 20.1.3) and the ChapterSegmentUUID Element. element. A
Chapter Edition with Ordered Chapters MAY contain Chapter Chapters elements
that reference timestamp ranges from other Segments. The Segment
referenced by the Ordered Chapter via the ChapterSegmentUUID Element element
SHOULD be played as part of a Linked Segment.
The timestamps of Segment content referenced by Ordered Chapters MUST
be adjusted according to the cumulative duration of the previous
Ordered Chapters.
As an example example, a file named intro.mkv could have a SegmentUUID of
"0xb16a58609fc7e60653a60c984fc11ead". Another file called
program.mkv could use a Chapter Edition that contains two Ordered
Chapters. The first chapter references the Segment of intro.mkv with
the use of a ChapterSegmentUUID, ChapterSegmentEditionUID,
ChapterTimeStart, and optionally a an optional ChapterTimeEnd element. The second
chapter references content within the Segment of program.mkv. A
Matroska Player SHOULD recognize the Linked Segment created by the
use of ChapterSegmentUUID in an enabled Edition and present the
reference content of the two Segments as a single presentation.
The ChapterSegmentUUID represents the Segment that holds the content
to play in place of the Linked Chapter. The ChapterSegmentUUID MUST
NOT be the SegmentUUID of its own Segment.
There are 2 two ways to use a chapter link:
* Linked-Duration linking, linking
* Linked-Edition linking
17.2.1. Linked-Duration
A Matroska Player MUST play the content of the linked Linked Segment from
the ChapterTimeStart until the ChapterTimeEnd timestamp in place of
the Linked Chapter.
ChapterTimeStart and ChapterTimeEnd represent timestamps in the
Linked Segment matching the value of ChapterSegmentUUID. Their
values MUST be in the range of the linked Linked Segment duration.
The ChapterTimeEnd value MUST be set when using linked-duration Linked-Duration
chapter linking. ChapterSegmentEditionUID MUST NOT be set.
17.2.2. Linked-Edition
A Matroska Player MUST play the whole linked Linked Edition of the linked Linked
Segment in place of the Linked Chapter.
ChapterSegmentEditionUID represents a valid Edition from the Linked
Segment matching the value of ChapterSegmentUUID.
When using linked-edition Linked-Edition chapter linking. linking, ChapterTimeEnd is
OPTIONAL.
18. Track Flags
18.1. Default flag Flag
The "default track" Default flag is a hint for a Matroska Player indicating that a
given track SHOULD be eligible to be automatically selected as the
default track for a given language. If no tracks in a given language
have the default track Default flag set, then all tracks in that language are
eligible for automatic selection. This can be used to indicate that
a track provides "regular service" that is suitable for users with
default settings, as opposed to specialized services, such as
commentary, hearing-impaired captions, captions for users with hearing impairments, or
descriptive audio.
The Matroska Player MAY override the "default track" Default flag for any reason,
including user preferences to prefer tracks providing accessibility
services.
18.2. Forced flag Flag
The "forced" Forced flag tells the Matroska Player that it SHOULD display this
subtitle track, even if user preferences usually would not call for
any subtitles to be displayed alongside the current selected audio track. track that is
currently selected. This can be used to indicate that a track
contains translations of onscreen text, on-screen text or of dialogue spoken in a
different language than the track's primary one. language.
18.3. Hearing-impaired flag Hearing-Impaired Flag
The "hearing impaired" Hearing-Impaired flag tells the Matroska Player that it SHOULD
prefer this track when selecting a default track for a hearing-
impaired user, user with a
hearing impairment and that it MAY prefer to select a different track
when selecting a default track for a non-hearing-impaired user. user that is not hearing
impaired.
18.4. Visual-impaired flag Visual-Impaired Flag
The "visual impaired" Visual-Impaired flag tells the Matroska Player that it SHOULD
prefer this track when selecting a default track for a visually-
impaired user, user with a
visual impairment and that it MAY prefer to select a different track
when selecting a default track for a non-visually-impaired user. user that is not visually
impaired.
18.5. Descriptions flag Flag
The "descriptions" Descriptions flag tells the Matroska Player that this track is
suitable to play via a text-to-speech system for a visually-impaired
user, user with a visual
impairment and that it SHOULD NOT automatically select this track
when selecting a default track for a non-visually-impaired user. user that is not visually
impaired.
18.6. Original flag Flag
The "original" Original flag tells the Matroska Player that this track is in the
original language, language and that it SHOULD prefer it this track if configured
to prefer original-language tracks of this track's type.
18.7. Commentary flag Flag
The "commentary" Commentary flag tells the Matroska Player that this track
contains commentary on the content.
18.8. Track Operation
TrackOperation allows combining for the combination of multiple tracks to make
a virtual one. It uses two separate system to combine tracks. One
to create a 3D "composition" (left/right/background planes) and one
to simplify join two tracks together to make a single track.
A track created with TrackOperation is a proper track with a UID and
all its flags. However, the codec ID is meaningless because each
"sub" track needs to be decoded by its own decoder before the
"operation" is applied. The Cues Elements elements corresponding to such a
virtual track SHOULD be the union of the Cues Elements elements for each of
the tracks it's composed of (when the Cues are defined per track).
In the case of TrackJoinBlocks, the Block Elements elements (from BlockGroup
and SimpleBlock) of all the tracks SHOULD be used as if they were
defined for this new virtual Track. When two Block Elements elements have
overlapping start or end timestamps, it's up to the underlying system
to either drop some of these frames or render them the way they
overlap. This situation SHOULD be avoided when creating such tracks tracks,
as you can never be sure of the end result on different platforms.
18.9. Overlay Track
Overlay tracks
An overlay track SHOULD be rendered in the same channel as the track
it's linked to. When content is found in such a track, it SHOULD be
played on the rendering channel instead of the original track.
18.10. Multi-planar and 3D videos Videos
There are two different ways to compress 3D videos: have each eye
track in a separate track and have one track have both eyes combined
inside (which is more efficient, efficient compression-wise). Matroska supports
both ways.
For the single track single-track variant, there is the StereoMode Element, element, which
defines how planes are assembled in the track (mono or left-right
combined). Odd values of StereoMode means the left plane comes first
for more convenient reading. The pixel count of the track
(PixelWidth/PixelHeight) is the raw amount number of pixels, for example pixels (for example,
3840x1080 for full HD side by side, side), and the DisplayWidth/
DisplayHeight in pixels is the amount number of pixels for one plane
(1920x1080 for that full HD stream). Old stereo 3D movies were
displayed using anaglyph (cyan and red colors separated). For
compatibility with such movies, there is a value of the StereoMode
that corresponds to AnaGlyph. anaglyph.
There is also a "packed" mode (values 13 and 14) which that consists of
packing two frames together in a Block using that uses lacing. The first
frame is the left eye and the other frame is the right eye (or vice
versa). The frames SHOULD be decoded in that order and are possibly
dependent on each other (P and B frames).
For separate tracks, Matroska needs to define exactly which track
does what. TrackOperation with TrackCombinePlanes do does that. For
more
details look at details, see Section 18.8 on how TrackOperation works.
The 3D support is still in infancy and may evolve to support more
features.
The StereoMode used to be part of Matroska v2 v2, but it didn't meet the
requirement for multiple tracks. There was also a bug in libmatroska
[libmatroska] prior to 0.9.0 that would save/read it as 0x53B9
instead of 0x53B8; see OldStereoMode (Section 5.1.4.1.28.5).
Matroska Readers MAY support these legacy files by checking Matroska
v2 or 0x53B9. The older values of StereoMode were 0: mono, 1: right eye, 2: left eye,
3: both eyes, 0 (mono), 1 (right
eye), 2 (left eye), and 3 (both eyes); these are the only values that
can be found in OldStereoMode. They are not compatible with the
StereoMode values found in Matroska v3 and above.
19. Default track selection Track Selection
This section provides some example sets of Tracks and hypothetical
user settings, along with indications of which ones a similarly- similarly
configured Matroska Player SHOULD automatically select for playback
by default in such a situation. A player MAY provide additional
settings with more detailed controls for more nuanced scenarios.
These examples are provided as guidelines to illustrate the intended
usages of the various supported Track flags, flags and their expected
behaviors.
Track names are shown in English for illustrative purposes; actual
files may have titles in the language of each track, track or provide titles
in multiple languages.
19.1. Audio Selection
Example track set:
+===+=====+====+======+========+=======+===============+===========+
|No.|Type |Lang|Layout|Original|Default|Other flags Flags |Name |
+===+=====+====+======+========+=======+===============+===========+
|1 |Video|und |N/A |N/A |N/A |None | |
+---+-----+----+------+--------+-------+---------------+-----------+
|2 |Audio|eng |5.1 |1 |1 |None | |
+---+-----+----+------+--------+-------+---------------+-----------+
|3 |Audio|eng |2.0 |1 |1 |None | |
+---+-----+----+------+--------+-------+---------------+-----------+
|4 |Audio|eng |2.0 |1 |0 |Visual-impaired|Descriptive| |Visual-Impaired|Descriptive|
| | | | | | | |audio |
+---+-----+----+------+--------+-------+---------------+-----------+
|5 |Audio|esp |5.1 |0 |1 |None | |
+---+-----+----+------+--------+-------+---------------+-----------+
|6 |Audio|esp |2.0 |0 |0 |Visual-impaired|Descriptive| |Visual-Impaired|Descriptive|
| | | | | | | |audio |
+---+-----+----+------+--------+-------+---------------+-----------+
|7 |Audio|eng |2.0 |1 |0 |Commentary |Director's |
| | | | | | | |Commentary |
+---+-----+----+------+--------+-------+---------------+-----------+
|8 |Audio|eng |2.0 |1 |0 |None |Karaoke |
+---+-----+----+------+--------+-------+---------------+-----------+
Table 45: 46: Audio Tracks for default selection
Here we have Default Selection
The table above shows a file with 7 seven audio tracks, of which 5 are tracks -- five in
English and 2 are two in Spanish.
The English tracks all have the Original flag, indicating that
English is the original content language.
Generally
Generally, the player will first consider the track languages: if languages. If
the player has an option to prefer original-language audio and the
user has enabled it, then it should prefer one of the Original-flagged
tracks. tracks with the
Original flag. If the user has configured to specifically prefer
audio tracks in English or Spanish, the player should select one of
the tracks in the corresponding language. The player may also wish
to prefer an
Original-flagged a track with the Original flag if no tracks matching any of
the user's
explicitly-preferred explicitly preferred languages are available.
Two of the tracks have the Visual-impaired Visual-Impaired flag. If the player has
been configured to prefer such tracks, it should select one;
otherwise, it should avoid them if possible.
If selecting an English track, when other settings have left multiple
possible options, it may be useful to exclude the tracks that lack
the Default flag: here, flag. Here, one provides descriptive service for the
visually impaired
individuals with visual impairments (which has its own flag and may
be automatically selected by user configuration, configuration but is unsuitable for
users with default-configured players), one is a commentary track
(which has its own flag, which flag and the player may or may not have
specialized handling for), and the last contains karaoke versions of
the music that plays during the film, which film (which is an unusual specialized
audio service that Matroska has no built-in support for indicating,
so it's indicated in the track name instead. instead). By not setting the
Default flag on these specialized tracks, the file's author hints
that they should not be automatically selected by a default-configured default-
configured player.
Having narrowed its choices down, our the example player now may have to
select between tracks 2 and 3. The only difference between these
tracks is their channel layouts: 2 is 5.1 surround, while 3 is
stereo. If the player is aware that the output device is a pair of
headphones or stereo speakers, it may wish to prefer the stereo mix
automatically. On the other hand, if it knows that the device is a
surround system, it may wish to prefer the surround mix.
If the player finishes analyzing all of the available audio tracks
and finds that multiple seems more than one seem equally and maximally preferable,
it SHOULD default to the first of the group.
19.2. Subtitle selection Selection
Example track set:
+===+===========+====+========+=======+======+==========+==========+
|No.| Type |Lang|Original|Default|Forced| Other
+===+=========+====+========+=======+======+========+==============+
|No.|Type |Lang|Original|Default|Forced|Other | Name |
| | | | | | | flags |Flags | |
+===+===========+====+========+=======+======+==========+==========+
+===+=========+====+========+=======+======+========+==============+
|1 | Video |Video |und |N/A |N/A |N/A | None |None | |
+---+-----------+----+--------+-------+------+----------+----------+
+---+---------+----+--------+-------+------+--------+--------------+
|2 | Audio |Audio |fra |1 |1 |N/A | None |None | |
+---+-----------+----+--------+-------+------+----------+----------+
+---+---------+----+--------+-------+------+--------+--------------+
|3 | Audio |Audio |por |0 |1 |N/A | None |None | |
+---+-----------+----+--------+-------+------+----------+----------+
+---+---------+----+--------+-------+------+--------+--------------+
|4 | Subtitles |fra |Subtitles|fra |1 |1 |0 | None |None | |
+---+-----------+----+--------+-------+------+----------+----------+
+---+---------+----+--------+-------+------+--------+--------------+
|5 | Subtitles |fra |Subtitles|fra |1 |0 |0 | Hearing- | |Hearing-| Captions for |
| | | | | | | impaired | for the |Impaired| users with |
| | | | | | | | hearing- hearing |
| | | | | | | | impaired impairments |
+---+-----------+----+--------+-------+------+----------+----------+
+---+---------+----+--------+-------+------+--------+--------------+
|6 | Subtitles |por |Subtitles|por |0 |1 |0 | None |None | |
+---+-----------+----+--------+-------+------+----------+----------+
+---+---------+----+--------+-------+------+--------+--------------+
|7 | Subtitles |por |Subtitles|por |0 |0 |1 | None |None | Signs |
+---+-----------+----+--------+-------+------+----------+----------+
+---+---------+----+--------+-------+------+--------+--------------+
|8 | Subtitles |por |Subtitles|por |0 |0 |0 | Hearing- | |Hearing-| SDH |
| | | | | | |Impaired| | impaired | |
+---+-----------+----+--------+-------+------+----------+----------+
+---+---------+----+--------+-------+------+--------+--------------+
Table 46: 47: Subtitle Tracks for default selection
Here we have 2 Default Selection
The table above shows two audio tracks and 5 five subtitle tracks. As
we can see, French is the original language.
We'll start by discussing the case where the user prefers French (or
Original-language)
original-language) audio (or has explicitly selected the French audio
track),
track) and also prefers French subtitles.
In this case, if the player isn't configured to display captions when
the audio matches their preferred subtitle languages, the player
doesn't need to select a subtitle track at all.
If the user _has_ indicated that they want captions to be displayed,
the selection simply comes down to whether Hearing-impaired hearing-impaired subtitles
are preferred.
The situation for a user who prefers Portuguese subtitles starts out
somewhat analogous. If they select the original French audio (either
by explicit audio language preference, preference for Original- original-
language tracks, or by explicitly selecting that track), then the
selection once again comes down to the hearing-impaired preference.
However, the case where the Portuguese audio track is selected has an
important catch: a Forced track in Portuguese is present. This may
contain translations of onscreen on-screen text from the video track, track or of
portions of the audio that are not translated (music, for instance).
This means that even if the user's preferences wouldn't normally call
for captions here, the Forced track should be selected nonetheless,
rather than selecting no track at all. On the other hand, if the
user's preferences _do_ call for captions, the non-Forced tracks
should be preferred, as the Forced track will not contain captioning
for the dialogue.
20. Chapters
The Matroska Chapters system can have multiple Editions Editions, and each
Edition can consist of Simple Chapters where a chapter start time is
used as a marker in the timeline only. An Edition can be more
complex with Ordered Chapters where a chapter end time stamp timestamp is
additionally used or much more complex with Linked Chapters. The
Matroska Chapters system can also have a menu structure, structure borrowed from
the DVD
menu DVD-menu system [DVD-Video], [DVD-Video] or have its own built-in Matroska
menu structure.
20.1. EditionEntry
The EditionEntry is also called an Edition. An Edition contains a
set of Edition flags and MUST contain at least one ChapterAtom
Element.
element. Chapters are always inside an Edition (or a Chapter itself
is part of an Edition). Multiple Editions are allowed. Some of
these Editions MAY be ordered and others not.
20.1.1. EditionFlagDefault
Only one Edition SHOULD have an EditionFlagDefault flag set to true.
20.1.2. Default Edition
The Default Edition is the Edition that a Matroska Player SHOULD use
for playback by default.
The first Edition with the EditionFlagDefault flag set to true is the
Default Edition.
When all EditionFlagDefault flags are set to false, then the first
Edition is the Default Edition.
+===========+=============+=================+
| Edition | FlagDefault | Default Edition |
+===========+=============+=================+
| Edition 1 | true | X |
+-----------+-------------+-----------------+
| Edition 2 | true | |
+-----------+-------------+-----------------+
| Edition 3 | true | |
+-----------+-------------+-----------------+
Table 47: 48: Default Edition, All Default edition, all default
+===========+=============+=================+
| Edition | FlagDefault | Default Edition |
+===========+=============+=================+
| Edition 1 | false | X |
+-----------+-------------+-----------------+
| Edition 2 | false | |
+-----------+-------------+-----------------+
| Edition 3 | false | |
+-----------+-------------+-----------------+
Table 48: 49: Default Edition, No Default edition, no default
+===========+=============+=================+
| Edition | FlagDefault | Default Edition |
+===========+=============+=================+
| Edition 1 | false | |
+-----------+-------------+-----------------+
| Edition 2 | true | X |
+-----------+-------------+-----------------+
| Edition 3 | false | |
+-----------+-------------+-----------------+
Table 49: 50: Default Edition, With Default edition, with default
20.1.3. EditionFlagOrdered
The EditionFlagOrdered Flag flag is a significant feature feature, as it enables
an Edition of Ordered Chapters which that defines and arranges a virtual
timeline rather than simply labeling points within the timeline. For
example, with Editions of Ordered Chapters Chapters, a single Matroska file
can present multiple edits of a film without duplicating content.
Alternatively, if a videotape is digitized in full, one Ordered
Edition could present the full content (including colorbars,
countdown, slate, a feature presentation, and black frames), while
another Edition of Ordered Chapters can use Chapters that only mark
the intended presentation with the colorbars and other ancillary
visual information excluded. If an Edition of Ordered Chapters is
enabled, then the Matroska Player MUST play those Chapters in their
stored order from the timestamp marked in the ChapterTimeStart
Element
element to the timestamp marked in to ChapterTimeEnd Element. element.
If the EditionFlagOrdered Flag flag evaluates to "0", Simple Chapters are
used and only the ChapterTimeStart of a Chapter is used as a chapter
mark to jump to the predefined point in the timeline. With Simple
Chapters, a Matroska Player MUST ignore certain Chapter Elements. elements inside a
Chapters element. In that case case, these elements are informational
only.
The following list shows the different Chapter Chapters elements only found
in Ordered Chapters.
+======================================+
| Ordered Chapter elements |
+======================================+
| ChapterAtom/ChapterSegmentUUID |
+--------------------------------------+
| ChapterAtom/ChapterSegmentEditionUID |
+--------------------------------------+
| ChapterAtom/ChapterTrack |
+--------------------------------------+
| ChapterAtom/ChapProcess |
+--------------------------------------+
| Info/ChapterTranslate |
+--------------------------------------+
| TrackEntry/TrackTranslate |
+--------------------------------------+
Table 50: elements only found in
ordered chapters
* ChapterAtom\ChapterSegmentUUID
* ChapterAtom\ChapterSegmentEditionUID
* ChapterAtom\ChapProcess
* Info\ChapterTranslate
* TrackEntry\TrackTranslate
Furthermore, there are other EBML Elements which elements that could be used if the
EditionFlagOrdered evaluates to "1".
20.1.3.1. Ordered-Edition and Matroska Segment-Linking
* Segment Linking
Hard Linking: Ordered-Chapters supersedes Ordered Chapters supersede the Hard Linking.
*
Medium Linking: Ordered Chapters are used in a normal way and can be
combined with the ChapterSegmentUUID element element, which establishes a
link to another Segment.
See Section 17 on the Linked Segments for more information about Hard
Linking and Medium Linking.
20.2. ChapterAtom
The ChapterAtom is also called a Chapter.
20.2.1. ChapterTimeStart
The
ChapterTimeStart is the timestamp of the start of Chapter with
nanosecond accuracy, accuracy and is not scaled by TimestampScale. For Simple Chapters
Chapters, this is the position of the chapter markers in the
timeline.
20.2.2. ChapterTimeEnd
The
ChapterTimeEnd is the timestamp of the end of Chapter with nanosecond accuracy,
accuracy and is not scaled by TimestampScale. The timestamp defined
by the ChapterTimeEnd is not part of the Chapter. A Matroska Player
calculates the duration of this Chapter using the difference between
the ChapterTimeEnd and ChapterTimeStart. The end timestamp MUST be
greater than or equal to the start timestamp.
When the ChapterTimeEnd timestamp is equal to the ChapterTimeStart
timestamp, the timestamps timestamp is included in the Chapter. It can be
useful to put markers in a file or add chapter commands with ordered
chapter commands without having to play anything; see
Section 5.1.7.1.4.14.
+===========+=================+===============+===============+
| Chapter | Start timestamp | End timestamp | Duration |
+===========+=================+===============+===============+
| Chapter 1 | 0 | 1000000000 | 1000000000 |
+-----------+-----------------+---------------+---------------+
| Chapter 2 | 1000000000 | 5000000000 | 4000000000 |
+-----------+-----------------+---------------+---------------+
| Chapter 3 | 6000000000 | 6000000000 | 0 |
+-----------+-----------------+---------------+---------------+
| Chapter 4 | 9000000000 | 8000000000 | Invalid |
| | | | (-1000000000) |
+-----------+-----------------+---------------+---------------+
Table 51: ChapterTimeEnd usage possibilities Usage Possibilities
20.2.3. Nested Chapters
A ChapterAtom element can contain other ChapterAtom elements. That
element is a Parent Chapter Chapter, and the ChapterAtom elements it contains
are Nested Chapters.
Nested Chapters can be useful to tag small parts of a Segment that
already have tags or add Chapter Codec commands on smaller parts of a
Segment that already have Chapter Codec commands.
The ChapterTimeStart of a Nested Chapter MUST be greater than or
equal to the ChapterTimeStart of its Parent Chapter.
If the Parent Chapter of a Nested Chapter has a ChapterTimeEnd, the
ChapterTimeStart of that Nested Chapter MUST be smaller than or equal
to the ChapterTimeEnd of the Parent Chapter.
20.2.4. Nested Chapters in Ordered Chapters
The ChapterTimeEnd of the lowest level of Nested Chapters MUST be set
for Ordered Chapters.
When used with Ordered Chapters, the ChapterTimeEnd value of a Parent
Chapter is useless for playback playback, as the proper playback sections are
described in its Nested Chapters. The ChapterTimeEnd SHOULD NOT be
set in Parent Chapters and MUST be ignored for playback.
20.2.5. ChapterFlagHidden
Each Chapter Chapter's ChapterFlagHidden flag works independently of parent
chapters. Parent
Chapters. A Nested Chapter with a ChapterFlagHidden flag that
evaluates to "0" remains visible in the user interface even if the
Parent
Chapter Chapter's ChapterFlagHidden flag is set to "1".
+==========================+===================+=========+
| Chapter + Nested Chapter | ChapterFlagHidden | visible |
+==========================+===================+=========+
| Chapter 1 | 0 | yes |
+--------------------------+-------------------+---------+
| Nested Chapter 1.1 | 0 | yes |
+--------------------------+-------------------+---------+
| Nested Chapter 1.2 | 1 | no |
+--------------------------+-------------------+---------+
| Chapter 2 | 1 | no |
+--------------------------+-------------------+---------+
| Nested Chapter 2.1 | 0 | yes |
+--------------------------+-------------------+---------+
| Nested Chapter 2.2 | 1 | no |
+--------------------------+-------------------+---------+
Table 52: ChapterFlagHidden nested visibility Nested Visibility
20.3. Menu features Features
The menu features are handled like a chapter codec. That means each
codec has a type, some private data data, and some data in the chapters.
The type of the menu system is defined by the ChapProcessCodecID
parameter. For now, only 2 two values are supported : supported: 0 matroska script, (Matroska
Script) and 1 menu (menu borrowed from the DVD [DVD-Video]. [DVD-Video]). The private
data depend on
the type of menu system (stored in ChapProcessPrivate), idem for the
data stored in ChapProcessPrivate and ChapProcessData depends on the chapters (stored in ChapProcessData).
ChapProcessCodecID value.
The menu system, as well as Chapter Codecs in general, can do perform
actions on the Matroska Player like Player, such as jumping to another Chapter or
Edition, selecting different tracks tracks, and possibly more. The scope of
all the possibilities of Chapter Codecs is not covered in this document
document, as it depends on the Chapter Codec features and its
integration in a Matroska Player.
20.4. Physical Types
Each level can have different meanings for audio and video. The
ORIGINAL_MEDIA_TYPE tag [MatroskaTags] can be used to specify a
string for ChapterPhysicalEquiv = 60. Here is the list of possible
levels for both audio and video:
+=======+=======================+=============+=====================+
| Value | Audio | Video | Comment |
+=======+=======================+=============+=====================+
| 70 | SET / PACKAGE | SET / | the collection of |
| | | PACKAGE | different media |
+-------+-----------------------+-------------+---------------------+
| 60 | CD / 12" / 10" / 7" / | DVD / VHS | the physical medium |
| | TAPE / MINIDISC / DAT | / | like a CD or a DVD |
| | | LASERDISC | |
+-------+-----------------------+-------------+---------------------+
| 50 | SIDE | SIDE | when the original |
| | | | medium (LP/DVD) has |
| | | | different sides |
+-------+-----------------------+-------------+---------------------+
| 40 | - | LAYER | another physical |
| | | | level on DVDs |
+-------+-----------------------+-------------+---------------------+
| 30 | SESSION | SESSION | as found on CDs and |
| | | | DVDs |
+-------+-----------------------+-------------+---------------------+
| 20 | TRACK | - | as found on audio |
| | | | CDs |
+-------+-----------------------+-------------+---------------------+
| 10 | INDEX | - | the first logical |
| | | | level of the side/ |
| | | | medium |
+-------+-----------------------+-------------+---------------------+
Table 53: ChapterPhysicalEquiv meaning Meaning per track type Track Type
20.5. Chapter Examples
20.5.1. Example 1 : basic chaptering 1: Basic Chaptering
In this example example, a movie is split in different chapters. It could
also just be an audio file (album) on in which each track corresponds to
a chapter.
* 00000 ms - 05000 ms : ms: Intro
* 05000 ms - 25000 ms : ms: Before the crime
* 25000 ms - 27500 ms : ms: The crime
* 27500 ms - 38000 ms : The killer arrested ms: After the crime
* 38000 ms - 43000 ms : ms: Credits
This would translate in the following matroska translates to Matroska form, with the EBML tree shown as XML : follows
in XML:
<Chapters>
<EditionEntry>
<EditionUID>16603393396715046047</EditionUID>
<ChapterAtom>
<ChapterUID>1193046</ChapterUID>
<ChapterTimeStart>0</ChapterTimeStart>
<ChapterTimeEnd>5000000000</ChapterTimeEnd>
<ChapterDisplay>
<ChapString>Intro</ChapString>
</ChapterDisplay>
</ChapterAtom>
<ChapterAtom>
<ChapterUID>2311527</ChapterUID>
<ChapterTimeStart>5000000000</ChapterTimeStart>
<ChapterTimeEnd>25000000000</ChapterTimeEnd>
<ChapterDisplay>
<ChapString>Before the crime</ChapString>
</ChapterDisplay>
<ChapterDisplay>
<ChapString>Avant le crime</ChapString>
<ChapLanguage>fra</ChapLanguage>
</ChapterDisplay>
</ChapterAtom>
<ChapterAtom>
<ChapterUID>3430008</ChapterUID>
<ChapterTimeStart>25000000000</ChapterTimeStart>
<ChapterTimeEnd>27500000000</ChapterTimeEnd>
<ChapterDisplay>
<ChapString>The crime</ChapString>
</ChapterDisplay>
<ChapterDisplay>
<ChapString>Le crime</ChapString>
<ChapLanguage>fra</ChapLanguage>
</ChapterDisplay>
</ChapterAtom>
<ChapterAtom>
<ChapterUID>4548489</ChapterUID>
<ChapterTimeStart>27500000000</ChapterTimeStart>
<ChapterTimeEnd>38000000000</ChapterTimeEnd>
<ChapterDisplay>
<ChapString>After the crime</ChapString>
</ChapterDisplay>
<ChapterDisplay>
<ChapString>Apres le crime</ChapString>
<ChapLanguage>fra</ChapLanguage>
</ChapterDisplay>
</ChapterAtom>
<ChapterAtom>
<ChapterUID>5666960</ChapterUID>
<ChapterTimeStart>38000000000</ChapterTimeStart>
<ChapterTimeEnd>43000000000</ChapterTimeEnd>
<ChapterDisplay>
<ChapString>Credits</ChapString>
</ChapterDisplay>
<ChapterDisplay>
<ChapString>Generique</ChapString>
<ChapLanguage>fra</ChapLanguage>
</ChapterDisplay>
</ChapterAtom>
</EditionEntry>
</Chapters>
Figure 16: 25: Basic Chapters Example. Example
20.5.2. Example 2 : nested chapters 2: Nested Chapters
In this example example, an (existing) album is split into different
chapters, and one of them contains another splitting.
20.5.2.1. The Micronauts "Bleep To Bleep"
* 00:00 - 12:28 : 12:28: Baby Wants To wants to Bleep/Rock
- 00:00 - 04:38 : 04:38: Baby wants to bleep (pt.1)
- 04:38 - 07:12 : 07:12: Baby wants to rock
- 07:12 - 10:33 : 10:33: Baby wants to bleep (pt.2)
- 10:33 - 12:28 : 12:28: Baby wants to bleep (pt.3)
* 12:30 - 19:38 : 19:38: Bleeper_O+2
* 19:40 - 22:20 : 22:20: Baby wants to bleep (pt.4)
* 22:22 - 25:18 : 25:18: Bleep to bleep
* 25:20 - 33:35 : 33:35: Baby wants to bleep (k)
* 33:37 - 44:28 : 44:28: Bleeper
This would translate in the following matroska translates to Matroska form, with the EBML tree shown as XML : follows
in XML:
<Chapters>
<EditionEntry>
<EditionUID>1281690858003401414</EditionUID>
<ChapterAtom>
<ChapterUID>1</ChapterUID>
<ChapterTimeStart>0</ChapterTimeStart>
<ChapterTimeEnd>748000000</ChapterTimeEnd>
<ChapterDisplay>
<ChapString>Baby wants to Bleep/Rock</ChapString>
</ChapterDisplay>
<ChapterAtom>
<ChapterUID>2</ChapterUID>
<ChapterTimeStart>0</ChapterTimeStart>
<ChapterTimeEnd>278000000</ChapterTimeEnd>
<ChapterDisplay>
<ChapString>Baby wants to bleep (pt.1)</ChapString>
</ChapterDisplay>
</ChapterAtom>
<ChapterAtom>
<ChapterUID>3</ChapterUID>
<ChapterTimeStart>278000000</ChapterTimeStart>
<ChapterTimeEnd>432000000</ChapterTimeEnd>
<ChapterDisplay>
<ChapString>Baby wants to rock</ChapString>
</ChapterDisplay>
</ChapterAtom>
<ChapterAtom>
<ChapterUID>4</ChapterUID>
<ChapterTimeStart>432000000</ChapterTimeStart>
<ChapterTimeEnd>633000000</ChapterTimeEnd>
<ChapterDisplay>
<ChapString>Baby wants to bleep (pt.2)</ChapString>
</ChapterDisplay>
</ChapterAtom>
<ChapterAtom>
<ChapterUID>5</ChapterUID>
<ChapterTimeStart>633000000</ChapterTimeStart>
<ChapterTimeEnd>748000000</ChapterTimeEnd>
<ChapterDisplay>
<ChapString>Baby wants to bleep (pt.3)</ChapString>
</ChapterDisplay>
</ChapterAtom>
</ChapterAtom>
<ChapterAtom>
<ChapterUID>6</ChapterUID>
<ChapterTimeStart>750000000</ChapterTimeStart>
<ChapterTimeEnd>1178500000</ChapterTimeEnd>
<ChapterDisplay>
<ChapString>Bleeper_O+2</ChapString>
</ChapterDisplay>
</ChapterAtom>
<ChapterAtom>
<ChapterUID>7</ChapterUID>
<ChapterTimeStart>1180500000</ChapterTimeStart>
<ChapterTimeEnd>1340000000</ChapterTimeEnd>
<ChapterDisplay>
<ChapString>Baby wants to bleep (pt.4)</ChapString>
</ChapterDisplay>
</ChapterAtom>
<ChapterAtom>
<ChapterUID>8</ChapterUID>
<ChapterTimeStart>1342000000</ChapterTimeStart>
<ChapterTimeEnd>1518000000</ChapterTimeEnd>
<ChapterDisplay>
<ChapString>Bleep to bleep</ChapString>
</ChapterDisplay>
</ChapterAtom>
<ChapterAtom>
<ChapterUID>9</ChapterUID>
<ChapterTimeStart>1520000000</ChapterTimeStart>
<ChapterTimeEnd>2015000000</ChapterTimeEnd>
<ChapterDisplay>
<ChapString>Baby wants to bleep (k)</ChapString>
</ChapterDisplay>
</ChapterAtom>
<ChapterAtom>
<ChapterUID>10</ChapterUID>
<ChapterTimeStart>2017000000</ChapterTimeStart>
<ChapterTimeEnd>2668000000</ChapterTimeEnd>
<ChapterDisplay>
<ChapString>Bleeper</ChapString>
</ChapterDisplay>
</ChapterAtom>
</EditionEntry>
</Chapters>
Figure 17: 26: Nested Chapters Example. Example
21. Attachments
Matroska supports storage of related files and data in the
Attachments Element element (a Top-Level Element). Attachment Elements Attachments elements can
be used to store related cover art, font files, transcripts, reports,
error recovery files, picture, or pictures, text-based annotations, copies of
specifications, or other ancillary files related to the Segment.
Matroska Readers MUST NOT execute files stored as Attachment
Elements. Attachments
elements.
21.1. Cover Art
This section defines a set of guidelines for the storage of cover art
in Matroska files. A Matroska Reader MAY use embedded cover art to
display a representational still-image depiction of the multimedia
contents of the Matroska file.
Only [JPEG] and PNG [RFC2083] image formats SHOULD be used for cover
art pictures.
There can be two different covers for a movie/album: a portrait style
(e.g., a DVD case) and a landscape style (e.g., a wide banner ad).
There can be two versions of the same cover, cover: the normal cover and the
small cover. The dimension of the normal cover SHOULD be 600 pixels
on the smallest side -- for example, (e.g., 960x600 for landscape, 600x800 for
portrait, or 600x600 for square. square). The dimension of the small cover
SHOULD be 120 pixels on the smallest side -- for example, (e.g., 192x120 or 120x160. 120x160).
Versions of cover art can be differentiated by the filename, which is
stored in the FileName Element. element. The default filename of the normal
cover in square or portrait mode is cover.(jpg|png). When stored,
the normal cover SHOULD be the first Attachment Attachments element in storage
order. The small cover SHOULD be prefixed with "small_", such as
small_cover.(jpg|png). The landscape variant SHOULD be suffixed with
"_land", such as cover_land.(jpg|png). The filenames are case-
sensitive.
The following table provides examples of file names for cover art in
Attachments.
+======================+===================+=================+
| FileName File Name | Image Orientation | Pixel Length of |
| | | Smallest Side |
+======================+===================+=================+
| cover.jpg | Portrait or | 600 |
| | square | |
+----------------------+-------------------+-----------------+
| small_cover.png | Portrait or | 120 |
| | square | |
+----------------------+-------------------+-----------------+
| cover_land.png | Landscape | 600 |
+----------------------+-------------------+-----------------+
| small_cover_land.jpg | Landscape | 120 |
+----------------------+-------------------+-----------------+
Table 54: Cover Art Filenames
21.2. Font files Files
Font files MAY be added to a Matroska file as Attachments so that the
font file may be used to display an associated subtitle track. This
allows the presentation of a Matroska file to be consistent in
various environments where the needed fonts might not be available on
the local system.
Depending on the font format in question, each font file can contain
multiple font variants. Each font variant has a name which that will be
referred to as Font Name from now on. This Font Name can be
different from the Attachment's FileName, even when disregarding the
extension. In order to select a font for display, a Matroska player Player
SHOULD consider both the Font Name and the base name of the
Attachment's FileName, preferring the former when there are multiple
matches.
Subtitle codecs, such as SubStation Alpha (SSA/ASS), (SSA) and Advanced
SubStation Alpha (ASS), usually refer to a font by its Font Name, not
by its filename. If none of the Attachments are a match for the Font
Name, the Matroska player Player SHOULD attempt to find a system font whose
Font Name matches the one used in the subtitle track.
Since loading fonts temporarily can take a while, a Matroska player Player
usually loads or installs all the fonts found in attachments so they
are ready to be used during playback. Failure to use the font
attachment might result in incorrect rendering of the subtitles.
If a selected subtitle track has some AttachmentLink elements, the
player MAY restrict its font rendering to use only these fonts.
A Matroska player Player SHOULD handle the official font media types from
[RFC8081] when the system can handle the type:
* font/sfnt: Generic SFNT Font Type, Type
* font/ttf: TTF TrueType Font Type, (TTF) Font Type
* font/otf: OpenType Layout (OTF) Font Type, Type
* font/collection: Collection Font Type, Type
* font/woff: WOFF 1.0, 1.0
* font/woff2: WOFF 2.0. 2.0
Fonts in Matroska existed long before [RFC8081]. A few unofficial
media types for fonts were used in existing files. Therefore, it is
RECOMMENDED for a Matroska player Player to support the following legacy
media types for font attachments:
* application/x-truetype-font: Truetype TrueType fonts, equivalent to font/
ttf and sometimes font/otf, font/otf
* application/x-font-ttf: TTF TrueType fonts, equivalent to font/ttf, font/ttf
* application/vnd.ms-opentype: OpenType Layout fonts, equivalent to
font/otf
* application/font-sfnt: Generic SFNT Font Type, equivalent to font/
sfnt
* application/font-woff: WOFF 1.0, equivalent to font/woff
There may also be some font attachments with the application/octet-
stream media type. In that case case, the Matroska player Player MAY try to
guess the font type by checking the file extension of the
AttachedFile\FileName string. Common file extensions for fonts are:
* .ttf for Truetype TrueType fonts, equivalent to font/ttf, font/ttf
* .otf for OpenType Layout fonts, equivalent to font/otf, font/otf
* .ttc for Collection fonts, equivalent to font/collection
The file extension check MUST be case-insensitive.
Matroska writers Writers SHOULD use a valid font media type from [RFC8081] in
the AttachedFile\FileMediaType of the font attachment. They MAY use
the media types found in older files when compatibility with older
players is necessary.
22. Cues
The Cues Element element provides an index of certain Cluster Elements elements to
allow for optimized seeking to absolute timestamps within the
Segment. The Cues Element element contains one or many CuePoint Elements
which elements,
each of which MUST reference an absolute timestamp (via the CueTime
Element),
element), a Track (via the CueTrack Element), element), and a Segment Position
(via the CueClusterPosition Element). element). Additional non-mandated
Elements
elements are part of the CuePoint Element element, such as CueDuration,
CueRelativePosition, CueCodecState CueCodecState, and others which that provide any
Matroska Reader with additional information to use in the
optimization of seeking performance.
22.1. Recommendations
The following recommendations are provided to optimize Matroska
performance.
* Unless Matroska is used as a live stream, it SHOULD contain a Cues
Element.
element.
* For each video track, each keyframe SHOULD be referenced by a
CuePoint Element. element.
* It is RECOMMENDED to not reference non-keyframes of video tracks
in Cues unless it references a Cluster Element which element that contains a
CodecState Element element but no keyframes.
* For each subtitle track present, each subtitle frame SHOULD be
referenced by a CuePoint Element element with a CueDuration Element. element.
* References to audio tracks MAY be skipped in CuePoint Elements elements if
a video track is present. When included included, the CuePoint Elements elements
SHOULD reference audio keyframes at most once every 500
milliseconds. milliseconds at
most.
* If the referenced frame is not stored within the first
SimpleBlock, SimpleBlock
or first BlockGroup within its Cluster Element, element, then the
CueRelativePosition Element element SHOULD be written to reference where
in the Cluster the reference frame is stored.
* If a CuePoint Element element references a Cluster Element element that includes a
CodecState Element, element, then that CuePoint Element element MUST use a
CueCodecState Element. element.
* CuePoint Elements elements SHOULD be numerically sorted in storage order by
the value of the CueTime Element. element.
23. Matroska Streaming
In Matroska, there are two kinds of streaming: file access and
livestreaming.
23.1. File Access
File access can simply be reading a file located on your computer,
but it also includes accessing a file from an HTTP (web) server or CIFS
Common Internet File System (CIFS) (Windows share) server. These
protocols are usually safe from reading errors errors, and seeking in the
stream is possible. However, when a file is stored far away or on a
slow server, seeking can be an expensive operation and should be
avoided. The When followed, the guidelines in Section 25, when followed, 25 help reduce the
number of seeking operations for regular playback and also have the
playback start quickly without a needing to read lot of data needed to read first
(like a Cues
Element, Attachment Element element, Attachments element, or SeekHead Element). element).
Matroska, having a small overhead, is well suited for storing music/
videos on file servers without a big impact on the bandwidth used.
Matroska does not require the index to be loaded before playing,
which allows playback to start very quickly. The index can be loaded
only when seeking is requested the first time.
23.2. Livestreaming
Livestreaming is the equivalent of television broadcasting on the
internet.
Internet. There are 2 two families of servers for livestreaming: RTP/
RTSP RTP /
Real-Time Streaming Protocol (RTSP) and HTTP. Matroska is not meant
to be used over RTP. RTP already has timing and channel mechanisms
that would be wasted if doubled in Matroska. Additionally, having
the same information at the RTP and Matroska level would be a source
of confusion if they do not match. Livestreaming of Matroska over
file-like protocols like HTTP, QUIC, etc. etc., is possible.
A live Matroska stream is different from a file because it usually
has no known end (only ending when the client disconnects). For
this, all bits of the "size" portion of the Segment Element element MUST be
set to 1. Another option is to concatenate Segment Elements elements with
known sizes, one after the other. This solution allows a change of
codec/resolution between each segment. For example, this allows for
a switch between 4:3 and 16:9 in a television program.
When Segment Elements elements are continuous, certain Elements, like elements (like
SeekHead, Cues, Chapters, and Attachments, Attachments) MUST NOT be used.
It is possible for a Matroska Player to detect that a stream is not
seekable. If the stream has neither a SeekHead list nor a Cues list
at the beginning of the stream, it SHOULD be considered non-seekable.
Even though it is possible to seek forward in the stream, it is NOT
RECOMMENDED.
In the context of live radio or web TV, it is possible to "tag" the
content while it is playing. The Tags Element element can be placed between
Clusters each time it is necessary. In that case, the new Tags
Element
element MUST reset the previously encountered Tags Elements elements and use
the new values instead.
24. Tags
24.1. Tags Precedence
Tags allow tagging all kinds of Matroska parts with very detailed
metadata in multiple languages.
Some Matroska elements also contain their own string value value, like the
Track
track Name element (Section 5.1.4.1.18) or the Chapter String ChapString element
(Section 5.1.7.1.4.10).
The following Matroska elements can also be defined with tags:
* The Track track Name Element element (Section 5.1.4.1.18) corresponds to a tag
with the TagTrackUID (Section 5.1.8.1.1.3) set to the given track,
a TagName of TITLE (Section 5.1.8.1.2.1) 5.1.8.1.2.1), and a TagLanguage
(Section 5.1.8.1.2.2) or TagLanguageBCP47 (Section 5.1.8.1.2.3) of
"und".
* The Chapter String Element ChapString element (Section 5.1.7.1.4.10) corresponds to a tag
with the TagChapterUID (Section 5.1.8.1.1.5) set to the same
chapter UID, a TagName of TITLE (Section 5.1.8.1.2.1) 5.1.8.1.2.1), and a
TagLanguage (Section 5.1.8.1.2.2) or TagLanguageBCP47
(Section 5.1.8.1.2.3) matching the ChapLanguage
(Section 5.1.7.1.4.11) or ChapLanguageBCP47
(Section 5.1.7.1.4.12) 5.1.7.1.4.12), respectively.
* The FileDescription Element element (Section 5.1.6.1.1) of an attachment
corresponds to a tag with the TagAttachmentUID
(Section 5.1.8.1.1.6) set to the given attachment, a TagName of
TITLE (Section 5.1.8.1.2.1) 5.1.8.1.2.1), and a TagLanguage
(Section 5.1.8.1.2.2) or TagLanguageBCP47 (Section 5.1.8.1.2.3) of
"und".
When both values exist in the file, the value found in Tags takes
precedence over the value found in the original location of the
element. For example, if you have a TrackEntry\Name element and Tag a
tag value TITLE for that track in a Matroska Segment, the Tag tag value
string SHOULD be used and
not instead of the TrackEntry\Name string to
identify the track.
As the Tag element is optional, a lot of Matroska Readers do not
handle it and will not use the tags value when it's found. So Thus, for
maximum compatibility, it's usually better to put the strings in the
TrackEntry, ChapterAtom ChapterAtom, and Attachment Attachments elements and keep the tags
matching these values if tags are also used.
24.2. Tag Levels
Tag elements allow tagging information on multiple levels, with each
level having a TargetTypeValue Section 5.1.8.1.1.1. An element for a
given TargetTypeValue also applies to the lower levels denoted by
smaller TargetTypeValue values. If an upper value doesn't apply to a
level but the actual value to use is not known, an empty TagString
(Section 5.1.8.1.2.5) or an empty TagBinary (Section 5.1.8.1.2.6)
element
MUST be used as the tag value for this level.
See [MatroskaTags] for more details on common tag names, types types, and
descriptions.
25. Implementation Recommendations
25.1. Cluster
It is RECOMMENDED that each individual Cluster Element contains element contain no
more than 5 five seconds or 5 five megabytes of content.
25.2. SeekHead
It is RECOMMENDED that the first SeekHead Element element be followed by a
Void Element element to allow for the SeekHead Element element to be expanded to
cover new Top-Level Elements that could be added to the Matroska
file, such as Tags, Chapters, and Attachments Elements. elements.
The size of this Void Element element should be adjusted depending on the
Matroska file already having
Tags, Chapters, and Attachments
Elements. elements in the Matroska file.
25.3. Optimum Layouts
While there can be Top-Level Elements in any order, some ordering orderings of
Elements
elements are better than others. Here are few The following subsections detail
optimum layouts for different use case: cases.
25.3.1. Optimum layout Layout for a muxer Muxer
This is the basic layout muxers should be using for an efficient
playback experience. experience:
* SeekHead
* Info
* Tracks
* Chapters
* Attachments
* Tags
* Clusters
* Cues
25.3.2. Optimum layout Layout after editing tags Editing Tags
When tags from the previous layout need to be extended, they are
moved to the end with the extra information. The location where the
old tags were located is voided.
* SeekHead
* Info
* Tracks
* Chapters
* Attachments
* Void
* Clusters
* Cues
* Tags
25.3.3. Optimum layout Layout with Cues at the front Front
Cues are usually a big chunk of data referencing a lot of locations
in the file. For players Players that want to seek in the file they need to seek to
the end of the file to access these locations. It is often better if
they are placed early in the file. On the other hand hand, that means
players that don't intend to seek will have to read/skip these data
no matter what.
Because the Cues reference locations further in the file, it's often
complicated to allocate the proper space for that element before all
the locations are known. Therefore, this layout is rarely used. used:
* SeekHead
* Info
* Tracks
* Chapters
* Attachments
* Tags
* Cues
* Clusters
25.3.4. Optimum layout Layout for livestreaming
In Livestreaming
In livestreaming (Section 23.2) 23.2), only a few elements make sense. For
example, SeekHead and Cues are useless for example. useless. All elements other than the
Clusters MUST be placed before the Clusters.
* Info
* Tracks
* Attachments (rare)
* Tags
* Clusters
26. Security Considerations
Matroska inherits security considerations from EBML. EBML [RFC8794].
Attacks on a Matroska Reader could include:
* Storage of an arbitrary and potentially executable data within an
Attachment Element.
Attachments element. Matroska Readers that extract or use data
from Matroska Attachments SHOULD check that the data adheres to
expectations or not use the attachement. attachment.
* A Matroska Attachment with an inaccurate media type.
* Damage to the Encryption and Compression fields (Section 14) that
would result in bogus binary data interpreted by the decoder.
* Chapter Codecs running unwanted commands on the host system.
The same error handling done for EBML applies to Matroska files.
Particular error handling is not covered in this specification specification, as
this is depends on the goal of the Matroska Readers. It is up to the
decision of the Matroska
Readers on decide how to handle the errors if whether or not they are
recoverable in their code or not. code. For example, if the checksum of the
\Segment\Tracks is invalid invalid, some could decide to try to read the data
anyway, some will just reject the file, and most will not even check
it.
Matroska Reader implementations need to be robust against malicious
payloads. Those related to denial of service are outlined in
Section 2.1 of [RFC4732].
Although rarer, the same may apply to a Matroska Writer. Malicious
stream data must not cause the Matroska Writer to misbehave, as this
might allow an attacker access to transcoding gateways.
As an audio and visual audio/video container format, a Matroska file or stream will
potentially encapsulate numerous byte streams created with a variety
of codecs. Implementers will need to consider the security
considerations of these encapsulated formats.
27. IANA Considerations
27.1. Matroska Element IDs Registry
This document creates
IANA has created a new IANA registry called the "Matroska Element IDs"
registry.
To register a new Element ID in this registry, one needs an Element
ID, an Element Name, a Change Controller (IETF or email of registrant)
registrant), and an optional Reference to a document describing the
Element ID.
Element IDs are encoded using the VINT mechanism described in
Section 4 of [RFC8794] and can be between one and five octets long.
Five-octet-long
Five-octet Element IDs are possible only if declared in the EBML
header.
Header.
Element IDs are described in Section 5 of [RFC8794] [RFC8794], with errata 7189 the changes
in [Err7189] and 7191. [Err7191].
One-octet Matroska Element IDs (range 0x80-0xFE) are to be allocated
according to the "RFC Required" policy [RFC8126].
Two-octet Matroska Element IDs (range 0x407F-0x7FFE) are to be
allocated according to the "Specification Required" policy [RFC8126].
Two-octet Matroska Element IDs between 0x0100 and 0x407E are not
valid for use as an Element ID.
Three-octet (range 0x203FFF-0x3FFFFE) and four-octet Matroska Element
IDs (range 0x101FFFFF-0x1FFFFFFE) are to be allocated according to
the "First Come First Served" policy [RFC8126].
Three-octet Matroska Element IDs between 0x010000 and 0x203FFE are
not valid for use as an Element ID.
Four-octet Matroska Element IDs between 0x01000000 and 0x101FFFFE are
not valid for use as an Element ID.
The allowed values in the Elements IDs "Matroska Element IDs" registry are similar
to the ones found in the EBML "EBML Element IDs IDs" registry defined in
Section 17.1 of [RFC8794].
EBML Element IDs defined for the EBML Header -- as defined in
Section 17.1 of [RFC8794] -- MUST NOT be used as Matroska Element
IDs.
Given the scarcity of the One-octet one-octet Element IDs, they should only be
created to save space for elements found many times in a file. For file (for
example, within a BlockGroup or Chapters. Chapters). The Four-octet four-octet Element IDs are
mostly for synchronization of large elements. They should only be
used for such high level high-level elements. Elements that are not expected to
be used often should use Three-octet three-octet Element IDs.
Elements found in Section 28 Appendix A have an assigned Matroska Element ID for
historical reasons. These elements are not in use and SHOULD NOT be
reused unless there is are no other IDs available with the desired size.
Such IDs are considered marked as reclaimed to "Reclaimed" in the IANA registry "Matroska Element IDs"
registry, as they could be used for other things in the future.
Matroska
Table 55 shows the initial contents of the "Matroska Element IDs Values found in this document are assigned as IDs"
registry. The Change Controller for the initial values as follows: entries is the IETF.
+============+=============================+======================+
| Element ID | Element Name | Reference |
+============+=============================+======================+
| 0x80 | ChapterDisplay | Described in RFC 9559, |
| | | Section 5.1.7.1.4.9 |
+------------+-----------------------------+----------------------+
| 0x83 | TrackType | Described in RFC 9559, |
| | | Section 5.1.4.1.3 |
+------------+-----------------------------+----------------------+
| 0x85 | ChapString | Described in RFC 9559, |
| | | Section 5.1.7.1.4.10 |
+------------+-----------------------------+----------------------+
| 0x86 | CodecID | Described in RFC 9559, |
| | | Section 5.1.4.1.21 |
+------------+-----------------------------+----------------------+
| 0x88 | FlagDefault | Described in RFC 9559, |
| | | Section 5.1.4.1.5 |
+------------+-----------------------------+----------------------+
| 0x8E | Slices | Reclaimed (RFC 9559, |
| | | (Section 28.5) Appendix A.5) |
+------------+-----------------------------+----------------------+
| 0x91 | ChapterTimeStart | Described in RFC 9559, |
| | | Section 5.1.7.1.4.3 |
+------------+-----------------------------+----------------------+
| 0x92 | ChapterTimeEnd | Described in RFC 9559, |
| | | Section 5.1.7.1.4.4 |
+------------+-----------------------------+----------------------+
| 0x96 | CueRefTime | Described in RFC 9559, |
| | | Section 5.1.5.1.2.8 |
+------------+-----------------------------+----------------------+
| 0x97 | CueRefCluster | Reclaimed (RFC 9559, |
| | | (Section 28.37) Appendix A.37) |
+------------+-----------------------------+----------------------+
| 0x98 | ChapterFlagHidden | Described in RFC 9559, |
| | | Section 5.1.7.1.4.5 |
+------------+-----------------------------+----------------------+
| 0x9A | FlagInterlaced | Described in RFC 9559, |
| | | Section 5.1.4.1.28.1 |
+------------+-----------------------------+----------------------+
| 0x9B | BlockDuration | Described in RFC 9559, |
| | | Section 5.1.3.5.3 |
+------------+-----------------------------+----------------------+
| 0x9C | FlagLacing | Described in RFC 9559, |
| | | Section 5.1.4.1.12 |
+------------+-----------------------------+----------------------+
| 0x9D | FieldOrder | Described in RFC 9559, |
| | | Section 5.1.4.1.28.2 |
+------------+-----------------------------+----------------------+
| 0x9F | Channels | Described in RFC 9559, |
| | | Section 5.1.4.1.29.3 |
+------------+-----------------------------+----------------------+
| 0xA0 | BlockGroup | Described in RFC 9559, |
| | | Section 5.1.3.5 |
+------------+-----------------------------+----------------------+
| 0xA1 | Block | Described in RFC 9559, |
| | | Section 5.1.3.5.1 |
+------------+-----------------------------+----------------------+
| 0xA2 | BlockVirtual | Reclaimed (RFC 9559, |
| | | (Section 28.3) Appendix A.3) |
+------------+-----------------------------+----------------------+
| 0xA3 | SimpleBlock | Described in RFC 9559, |
| | | Section 5.1.3.4 |
+------------+-----------------------------+----------------------+
| 0xA4 | CodecState | Described in RFC 9559, |
| | | Section 5.1.3.5.6 |
+------------+-----------------------------+----------------------+
| 0xA5 | BlockAdditional | Described in RFC 9559, |
| | | Section 5.1.3.5.2.2 |
+------------+-----------------------------+----------------------+
| 0xA6 | BlockMore | Described in RFC 9559, |
| | | Section 5.1.3.5.2.1 |
+------------+-----------------------------+----------------------+
| 0xA7 | Position | Described in RFC 9559, |
| | | Section 5.1.3.2 |
+------------+-----------------------------+----------------------+
| 0xAA | CodecDecodeAll | Reclaimed (RFC 9559, |
| | | (Section 28.22) Appendix A.22) |
+------------+-----------------------------+----------------------+
| 0xAB | PrevSize | Described in RFC 9559, |
| | | Section 5.1.3.3 |
+------------+-----------------------------+----------------------+
| 0xAE | TrackEntry | Described in RFC 9559, |
| | | Section 5.1.4.1 |
+------------+-----------------------------+----------------------+
| 0xAF | EncryptedBlock | Reclaimed (RFC 9559, |
| | | (Section 28.15) Appendix A.15) |
+------------+-----------------------------+----------------------+
| 0xB0 | PixelWidth | Described in RFC 9559, |
| | | Section 5.1.4.1.28.6 |
+------------+-----------------------------+----------------------+
| 0xB2 | CueDuration | Described in RFC 9559, |
| | | Section 5.1.5.1.2.4 |
+------------+-----------------------------+----------------------+
| 0xB3 | CueTime | Described in RFC 9559, |
| | | Section 5.1.5.1.1 |
+------------+-----------------------------+----------------------+
| 0xB5 | SamplingFrequency | Described in RFC 9559, |
| | | Section 5.1.4.1.29.1 |
+------------+-----------------------------+----------------------+
| 0xB6 | ChapterAtom | Described in RFC 9559, |
| | | Section 5.1.7.1.4 |
+------------+-----------------------------+----------------------+
| 0xB7 | CueTrackPositions | Described in RFC 9559, |
| | | Section 5.1.5.1.2 |
+------------+-----------------------------+----------------------+
| 0xB9 | FlagEnabled | Described in RFC 9559, |
| | | Section 5.1.4.1.4 |
+------------+-----------------------------+----------------------+
| 0xBA | PixelHeight | Described in RFC 9559, |
| | | Section 5.1.4.1.28.7 |
+------------+-----------------------------+----------------------+
| 0xBB | CuePoint | Described in RFC 9559, |
| | | Section 5.1.5.1 |
+------------+-----------------------------+----------------------+
| 0xC0 | TrickTrackUID | Reclaimed (RFC 9559, |
| | | (Section 28.28) Appendix A.28) |
+------------+-----------------------------+----------------------+
| 0xC1 | TrickTrackSegmentUID | Reclaimed (RFC 9559, |
| | | (Section 28.29) Appendix A.29) |
+------------+-----------------------------+----------------------+
| 0xC4 | TrickMasterTrackSegmentUID | Reclaimed (RFC 9559, |
| | | (Section 28.32) Appendix A.32) |
+------------+-----------------------------+----------------------+
| 0xC6 | TrickTrackFlag | Reclaimed (RFC 9559, |
| | | (Section 28.30) Appendix A.30) |
+------------+-----------------------------+----------------------+
| 0xC7 | TrickMasterTrackUID | Reclaimed (RFC 9559, |
| | | (Section 28.31) Appendix A.31) |
+------------+-----------------------------+----------------------+
| 0xC8 | ReferenceFrame | Reclaimed (RFC 9559, |
| | | (Section 28.12) Appendix A.12) |
+------------+-----------------------------+----------------------+
| 0xC9 | ReferenceOffset | Reclaimed (RFC 9559, |
| | | (Section 28.13) Appendix A.13) |
+------------+-----------------------------+----------------------+
| 0xCA | ReferenceTimestamp | Reclaimed (RFC 9559, |
| | | (Section 28.14) Appendix A.14) |
+------------+-----------------------------+----------------------+
| 0xCB | BlockAdditionID | Reclaimed (RFC 9559, |
| | | (Section 28.9) Appendix A.9) |
+------------+-----------------------------+----------------------+
| 0xCC | LaceNumber | Reclaimed (RFC 9559, |
| | | (Section 28.7) Appendix A.7) |
+------------+-----------------------------+----------------------+
| 0xCD | FrameNumber | Reclaimed (RFC 9559, |
| | | (Section 28.8) Appendix A.8) |
+------------+-----------------------------+----------------------+
| 0xCE | Delay | Reclaimed (RFC 9559, |
| | | (Section 28.10) Appendix A.10) |
+------------+-----------------------------+----------------------+
| 0xCF | SliceDuration | Reclaimed (RFC 9559, |
| | | (Section 28.11) Appendix A.11) |
+------------+-----------------------------+----------------------+
| 0xD7 | TrackNumber | Described in RFC 9559, |
| | | Section 5.1.4.1.1 |
+------------+-----------------------------+----------------------+
| 0xDB | CueReference | Described in RFC 9559, |
| | | Section 5.1.5.1.2.7 |
+------------+-----------------------------+----------------------+
| 0xE0 | Video | Described in RFC 9559, |
| | | Section 5.1.4.1.28 |
+------------+-----------------------------+----------------------+
| 0xE1 | Audio | Described in RFC 9559, |
| | | Section 5.1.4.1.29 |
+------------+-----------------------------+----------------------+
| 0xE2 | TrackOperation | Described in RFC 9559, |
| | | Section 5.1.4.1.30 |
+------------+-----------------------------+----------------------+
| 0xE3 | TrackCombinePlanes | Described in RFC 9559, |
| | | Section 5.1.4.1.30.1 |
+------------+-----------------------------+----------------------+
| 0xE4 | TrackPlane | Described in RFC 9559, |
| | | Section 5.1.4.1.30.2 |
+------------+-----------------------------+----------------------+
| 0xE5 | TrackPlaneUID | Described in RFC 9559, |
| | | Section 5.1.4.1.30.3 |
+------------+-----------------------------+----------------------+
| 0xE6 | TrackPlaneType | Described in RFC 9559, |
| | | Section 5.1.4.1.30.4 |
+------------+-----------------------------+----------------------+
| 0xE7 | Timestamp | Described in RFC 9559, |
| | | Section 5.1.3.1 |
+------------+-----------------------------+----------------------+
| 0xE8 | TimeSlice | Reclaimed (RFC 9559, |
| | | (Section 28.6) Appendix A.6) |
+------------+-----------------------------+----------------------+
| 0xE9 | TrackJoinBlocks | Described in RFC 9559, |
| | | Section 5.1.4.1.30.5 |
+------------+-----------------------------+----------------------+
| 0xEA | CueCodecState | Described in RFC 9559, |
| | | Section 5.1.5.1.2.6 |
+------------+-----------------------------+----------------------+
| 0xEB | CueRefCodecState | Reclaimed (RFC 9559, |
| | | (Section 28.39) Appendix A.39) |
+------------+-----------------------------+----------------------+
| 0xED | TrackJoinUID | Described in RFC 9559, |
| | | Section 5.1.4.1.30.6 |
+------------+-----------------------------+----------------------+
| 0xEE | BlockAddID | Described in RFC 9559, |
| | | Section 5.1.3.5.2.3 |
+------------+-----------------------------+----------------------+
| 0xF0 | CueRelativePosition | Described in RFC 9559, |
| | | Section 5.1.5.1.2.3 |
+------------+-----------------------------+----------------------+
| 0xF1 | CueClusterPosition | Described in RFC 9559, |
| | | Section 5.1.5.1.2.2 |
+------------+-----------------------------+----------------------+
| 0xF7 | CueTrack | Described in RFC 9559, |
| | | Section 5.1.5.1.2.1 |
+------------+-----------------------------+----------------------+
| 0xFA | ReferencePriority | Described in RFC 9559, |
| | | Section 5.1.3.5.4 |
+------------+-----------------------------+----------------------+
| 0xFB | ReferenceBlock | Described in RFC 9559, |
| | | Section 5.1.3.5.5 |
+------------+-----------------------------+----------------------+
| 0xFD | ReferenceVirtual | Reclaimed (RFC 9559, |
| | | (Section 28.4) Appendix A.4) |
+------------+-----------------------------+----------------------+
| 0xFF | Reserved | RFC 9559 |
+------------+-----------------------------+----------------------+
| 0x41A4 | BlockAddIDName | Described in RFC 9559, |
| | | Section 5.1.4.1.17.2 |
+------------+-----------------------------+----------------------+
| 0x41E4 | BlockAdditionMapping | Described in RFC 9559, |
| | | Section 5.1.4.1.17 |
+------------+-----------------------------+----------------------+
| 0x41E7 | BlockAddIDType | Described in RFC 9559, |
| | | Section 5.1.4.1.17.3 |
+------------+-----------------------------+----------------------+
| 0x41ED | BlockAddIDExtraData | Described in RFC 9559, |
| | | Section 5.1.4.1.17.4 |
+------------+-----------------------------+----------------------+
| 0x41F0 | BlockAddIDValue | Described in RFC 9559, |
| | | Section 5.1.4.1.17.1 |
+------------+-----------------------------+----------------------+
| 0x4254 | ContentCompAlgo | Described in RFC 9559, |
| | | Section 5.1.4.1.31.6 |
+------------+-----------------------------+----------------------+
| 0x4255 | ContentCompSettings | Described in RFC 9559, |
| | | Section 5.1.4.1.31.7 |
+------------+-----------------------------+----------------------+
| 0x437C | ChapLanguage | Described in RFC 9559, |
| | | Section 5.1.7.1.4.11 |
+------------+-----------------------------+----------------------+
| 0x437D | ChapLanguageBCP47 | Described in RFC 9559, |
| | | Section 5.1.7.1.4.12 |
+------------+-----------------------------+----------------------+
| 0x437E | ChapCountry | Described in RFC 9559, |
| | | Section 5.1.7.1.4.13 |
+------------+-----------------------------+----------------------+
| 0x4444 | SegmentFamily | Described in RFC 9559, |
| | | Section 5.1.2.7 |
+------------+-----------------------------+----------------------+
| 0x4461 | DateUTC | Described in RFC 9559, |
| | | Section 5.1.2.11 |
+------------+-----------------------------+----------------------+
| 0x447A | TagLanguage | Described in RFC 9559, |
| | | Section 5.1.8.1.2.2 |
+------------+-----------------------------+----------------------+
| 0x447B | TagLanguageBCP47 | Described in RFC 9559, |
| | | Section 5.1.8.1.2.3 |
+------------+-----------------------------+----------------------+
| 0x4484 | TagDefault | Described in RFC 9559, |
| | | Section 5.1.8.1.2.4 |
+------------+-----------------------------+----------------------+
| 0x4485 | TagBinary | Described in RFC 9559, |
| | | Section 5.1.8.1.2.6 |
+------------+-----------------------------+----------------------+
| 0x4487 | TagString | Described in RFC 9559, |
| | | Section 5.1.8.1.2.5 |
+------------+-----------------------------+----------------------+
| 0x4489 | Duration | Described in RFC 9559, |
| | | Section 5.1.2.10 |
+------------+-----------------------------+----------------------+
| 0x44B4 | TagDefaultBogus | Reclaimed (RFC 9559, |
| | | (Section 28.43) Appendix A.43) |
+------------+-----------------------------+----------------------+
| 0x450D | ChapProcessPrivate | Described in RFC 9559, |
| | | Section 5.1.7.1.4.16 |
+------------+-----------------------------+----------------------+
| 0x45A3 | TagName | Described in RFC 9559, |
| | | Section 5.1.8.1.2.1 |
+------------+-----------------------------+----------------------+
| 0x45B9 | EditionEntry | Described in RFC 9559, |
| | | Section 5.1.7.1 |
+------------+-----------------------------+----------------------+
| 0x45BC | EditionUID | Described in RFC 9559, |
| | | Section 5.1.7.1.1 |
+------------+-----------------------------+----------------------+
| 0x45DB | EditionFlagDefault | Described in RFC 9559, |
| | | Section 5.1.7.1.2 |
+------------+-----------------------------+----------------------+
| 0x45DD | EditionFlagOrdered | Described in RFC 9559, |
| | | Section 5.1.7.1.3 |
+------------+-----------------------------+----------------------+
| 0x465C | FileData | Described in RFC 9559, |
| | | Section 5.1.6.1.4 |
+------------+-----------------------------+----------------------+
| 0x4660 | FileMediaType | Described in RFC 9559, |
| | | Section 5.1.6.1.3 |
+------------+-----------------------------+----------------------+
| 0x4661 | FileUsedStartTime | Reclaimed (RFC 9559, |
| | | (Section 28.41) Appendix A.41) |
+------------+-----------------------------+----------------------+
| 0x4662 | FileUsedEndTime | Reclaimed (RFC 9559, |
| | | (Section 28.42) Appendix A.42) |
+------------+-----------------------------+----------------------+
| 0x466E | FileName | Described in RFC 9559, |
| | | Section 5.1.6.1.2 |
+------------+-----------------------------+----------------------+
| 0x4675 | FileReferral | Reclaimed (RFC 9559, |
| | | (Section 28.40) Appendix A.40) |
+------------+-----------------------------+----------------------+
| 0x467E | FileDescription | Described in RFC 9559, |
| | | Section 5.1.6.1.1 |
+------------+-----------------------------+----------------------+
| 0x46AE | FileUID | Described in RFC 9559, |
| | | Section 5.1.6.1.5 |
+------------+-----------------------------+----------------------+
| 0x47E1 | ContentEncAlgo | Described in RFC 9559, |
| | | Section 5.1.4.1.31.9 |
+------------+-----------------------------+----------------------+
| 0x47E2 | ContentEncKeyID | Described in RFC 9559, Section |
| | | 5.1.4.1.31.10 |
+------------+-----------------------------+----------------------+
| 0x47E3 | ContentSignature | Reclaimed (RFC 9559, |
| | | (Section 28.33) Appendix A.33) |
+------------+-----------------------------+----------------------+
| 0x47E4 | ContentSigKeyID | Reclaimed (RFC 9559, |
| | | (Section 28.34) Appendix A.34) |
+------------+-----------------------------+----------------------+
| 0x47E5 | ContentSigAlgo | Reclaimed (RFC 9559, |
| | | (Section 28.35) Appendix A.35) |
+------------+-----------------------------+----------------------+
| 0x47E6 | ContentSigHashAlgo | Reclaimed (RFC 9559, |
| | | (Section 28.36) Appendix A.36) |
+------------+-----------------------------+----------------------+
| 0x47E7 | ContentEncAESSettings | Described in RFC 9559, Section |
| | | 5.1.4.1.31.11 |
+------------+-----------------------------+----------------------+
| 0x47E8 | AESSettingsCipherMode | Described in RFC 9559, Section |
| | | 5.1.4.1.31.12 |
+------------+-----------------------------+----------------------+
| 0x4D80 | MuxingApp | Described in RFC 9559, |
| | | Section 5.1.2.13 |
+------------+-----------------------------+----------------------+
| 0x4DBB | Seek | Described in RFC 9559, |
| | | Section 5.1.1.1 |
+------------+-----------------------------+----------------------+
| 0x5031 | ContentEncodingOrder | Described in RFC 9559, |
| | | Section 5.1.4.1.31.2 |
+------------+-----------------------------+----------------------+
| 0x5032 | ContentEncodingScope | Described in RFC 9559, |
| | | Section 5.1.4.1.31.3 |
+------------+-----------------------------+----------------------+
| 0x5033 | ContentEncodingType | Described in RFC 9559, |
| | | Section 5.1.4.1.31.4 |
+------------+-----------------------------+----------------------+
| 0x5034 | ContentCompression | Described in RFC 9559, |
| | | Section 5.1.4.1.31.5 |
+------------+-----------------------------+----------------------+
| 0x5035 | ContentEncryption | Described in RFC 9559, |
| | | Section 5.1.4.1.31.8 |
+------------+-----------------------------+----------------------+
| 0x535F | CueRefNumber | Reclaimed (RFC 9559, |
| | | (Section 28.38) Appendix A.38) |
+------------+-----------------------------+----------------------+
| 0x536E | Name | Described in RFC 9559, |
| | | Section 5.1.4.1.18 |
+------------+-----------------------------+----------------------+
| 0x5378 | CueBlockNumber | Described in RFC 9559, |
| | | Section 5.1.5.1.2.5 |
+------------+-----------------------------+----------------------+
| 0x537F | TrackOffset | Reclaimed (RFC 9559, |
| | | (Section 28.18) Appendix A.18) |
+------------+-----------------------------+----------------------+
| 0x53AB | SeekID | Described in RFC 9559, |
| | | Section 5.1.1.1.1 |
+------------+-----------------------------+----------------------+
| 0x53AC | SeekPosition | Described in RFC 9559, |
| | | Section 5.1.1.1.2 |
+------------+-----------------------------+----------------------+
| 0x53B8 | StereoMode | Described in RFC 9559, |
| | | Section 5.1.4.1.28.3 |
+------------+-----------------------------+----------------------+
| 0x53B9 | OldStereoMode | Described in RFC 9559, |
| | | Section 5.1.4.1.28.5 |
+------------+-----------------------------+----------------------+
| 0x53C0 | AlphaMode | Described in RFC 9559, |
| | | Section 5.1.4.1.28.4 |
+------------+-----------------------------+----------------------+
| 0x54AA | PixelCropBottom | Described in RFC 9559, |
| | | Section 5.1.4.1.28.8 |
+------------+-----------------------------+----------------------+
| 0x54B0 | DisplayWidth | Described in RFC 9559, Section |
| | | 5.1.4.1.28.12 |
+------------+-----------------------------+----------------------+
| 0x54B2 | DisplayUnit | Described in RFC 9559, Section |
| | | 5.1.4.1.28.14 |
+------------+-----------------------------+----------------------+
| 0x54B3 | AspectRatioType | Reclaimed (RFC 9559, |
| | | (Section 28.24) Appendix A.24) |
+------------+-----------------------------+----------------------+
| 0x54BA | DisplayHeight | Described in RFC 9559, Section |
| | | 5.1.4.1.28.13 |
+------------+-----------------------------+----------------------+
| 0x54BB | PixelCropTop | Described in RFC 9559, |
| | | Section 5.1.4.1.28.9 |
+------------+-----------------------------+----------------------+
| 0x54CC | PixelCropLeft | Described in RFC 9559, Section |
| | | 5.1.4.1.28.10 |
+------------+-----------------------------+----------------------+
| 0x54DD | PixelCropRight | Described in RFC 9559, Section |
| | | 5.1.4.1.28.11 |
+------------+-----------------------------+----------------------+
| 0x55AA | FlagForced | Described in RFC 9559, |
| | | Section 5.1.4.1.6 |
+------------+-----------------------------+----------------------+
| 0x55AB | FlagHearingImpaired | Described in RFC 9559, |
| | | Section 5.1.4.1.7 |
+------------+-----------------------------+----------------------+
| 0x55AC | FlagVisualImpaired | Described in RFC 9559, |
| | | Section 5.1.4.1.8 |
+------------+-----------------------------+----------------------+
| 0x55AD | FlagTextDescriptions | Described in RFC 9559, |
| | | Section 5.1.4.1.9 |
+------------+-----------------------------+----------------------+
| 0x55AE | FlagOriginal | Described in RFC 9559, |
| | | Section 5.1.4.1.10 |
+------------+-----------------------------+----------------------+
| 0x55AF | FlagCommentary | Described in RFC 9559, |
| | | Section 5.1.4.1.11 |
+------------+-----------------------------+----------------------+
| 0x55B0 | Colour | Described in RFC 9559, Section |
| | | 5.1.4.1.28.16 |
+------------+-----------------------------+----------------------+
| 0x55B1 | MatrixCoefficients | Described in RFC 9559, Section |
| | | 5.1.4.1.28.17 |
+------------+-----------------------------+----------------------+
| 0x55B2 | BitsPerChannel | Described in RFC 9559, Section |
| | | 5.1.4.1.28.18 |
+------------+-----------------------------+----------------------+
| 0x55B3 | ChromaSubsamplingHorz | Described in RFC 9559, Section |
| | | 5.1.4.1.28.19 |
+------------+-----------------------------+----------------------+
| 0x55B4 | ChromaSubsamplingVert | Described in RFC 9559, Section |
| | | 5.1.4.1.28.20 |
+------------+-----------------------------+----------------------+
| 0x55B5 | CbSubsamplingHorz | Described in RFC 9559, Section |
| | | 5.1.4.1.28.21 |
+------------+-----------------------------+----------------------+
| 0x55B6 | CbSubsamplingVert | Described in RFC 9559, Section |
| | | 5.1.4.1.28.22 |
+------------+-----------------------------+----------------------+
| 0x55B7 | ChromaSitingHorz | Described in RFC 9559, Section |
| | | 5.1.4.1.28.23 |
+------------+-----------------------------+----------------------+
| 0x55B8 | ChromaSitingVert | Described in RFC 9559, Section |
| | | 5.1.4.1.28.24 |
+------------+-----------------------------+----------------------+
| 0x55B9 | Range | Described in RFC 9559, Section |
| | | 5.1.4.1.28.25 |
+------------+-----------------------------+----------------------+
| 0x55BA | TransferCharacteristics | Described in RFC 9559, Section |
| | | 5.1.4.1.28.26 |
+------------+-----------------------------+----------------------+
| 0x55BB | Primaries | Described in RFC 9559, Section |
| | | 5.1.4.1.28.27 |
+------------+-----------------------------+----------------------+
| 0x55BC | MaxCLL | Described in RFC 9559, Section |
| | | 5.1.4.1.28.28 |
+------------+-----------------------------+----------------------+
| 0x55BD | MaxFALL | Described in RFC 9559, Section |
| | | 5.1.4.1.28.29 |
+------------+-----------------------------+----------------------+
| 0x55D0 | MasteringMetadata | Described in RFC 9559, Section |
| | | 5.1.4.1.28.30 |
+------------+-----------------------------+----------------------+
| 0x55D1 | PrimaryRChromaticityX | Described in RFC 9559, Section |
| | | 5.1.4.1.28.31 |
+------------+-----------------------------+----------------------+
| 0x55D2 | PrimaryRChromaticityY | Described in RFC 9559, Section |
| | | 5.1.4.1.28.32 |
+------------+-----------------------------+----------------------+
| 0x55D3 | PrimaryGChromaticityX | Described in RFC 9559, Section |
| | | 5.1.4.1.28.33 |
+------------+-----------------------------+----------------------+
| 0x55D4 | PrimaryGChromaticityY | Described in RFC 9559, Section |
| | | 5.1.4.1.28.34 |
+------------+-----------------------------+----------------------+
| 0x55D5 | PrimaryBChromaticityX | Described in RFC 9559, Section |
| | | 5.1.4.1.28.35 |
+------------+-----------------------------+----------------------+
| 0x55D6 | PrimaryBChromaticityY | Described in RFC 9559, Section |
| | | 5.1.4.1.28.36 |
+------------+-----------------------------+----------------------+
| 0x55D7 | WhitePointChromaticityX | Described in RFC 9559, Section |
| | | 5.1.4.1.28.37 |
+------------+-----------------------------+----------------------+
| 0x55D8 | WhitePointChromaticityY | Described in RFC 9559, Section |
| | | 5.1.4.1.28.38 |
+------------+-----------------------------+----------------------+
| 0x55D9 | LuminanceMax | Described in RFC 9559, Section |
| | | 5.1.4.1.28.39 |
+------------+-----------------------------+----------------------+
| 0x55DA | LuminanceMin | Described in RFC 9559, Section |
| | | 5.1.4.1.28.40 |
+------------+-----------------------------+----------------------+
| 0x55EE | MaxBlockAdditionID | Described in RFC 9559, |
| | | Section 5.1.4.1.16 |
+------------+-----------------------------+----------------------+
| 0x5654 | ChapterStringUID | Described in RFC 9559, |
| | | Section 5.1.7.1.4.2 |
+------------+-----------------------------+----------------------+
| 0x56AA | CodecDelay | Described in RFC 9559, |
| | | Section 5.1.4.1.25 |
+------------+-----------------------------+----------------------+
| 0x56BB | SeekPreRoll | Described in RFC 9559, |
| | | Section 5.1.4.1.26 |
+------------+-----------------------------+----------------------+
| 0x5741 | WritingApp | Described in RFC 9559, |
| | | Section 5.1.2.14 |
+------------+-----------------------------+----------------------+
| 0x5854 | SilentTracks | Reclaimed (RFC 9559, |
| | | (Section 28.1) Appendix A.1) |
+------------+-----------------------------+----------------------+
| 0x58D7 | SilentTrackNumber | Reclaimed (RFC 9559, |
| | | (Section 28.2) Appendix A.2) |
+------------+-----------------------------+----------------------+
| 0x61A7 | AttachedFile | Described in RFC 9559, |
| | | Section 5.1.6.1 |
+------------+-----------------------------+----------------------+
| 0x6240 | ContentEncoding | Described in RFC 9559, |
| | | Section 5.1.4.1.31.1 |
+------------+-----------------------------+----------------------+
| 0x6264 | BitDepth | Described in RFC 9559, |
| | | Section 5.1.4.1.29.4 |
+------------+-----------------------------+----------------------+
| 0x63A2 | CodecPrivate | Described in RFC 9559, |
| | | Section 5.1.4.1.22 |
+------------+-----------------------------+----------------------+
| 0x63C0 | Targets | Described in RFC 9559, |
| | | Section 5.1.8.1.1 |
+------------+-----------------------------+----------------------+
| 0x63C3 | ChapterPhysicalEquiv | Described in RFC 9559, |
| | | Section 5.1.7.1.4.8 |
+------------+-----------------------------+----------------------+
| 0x63C4 | TagChapterUID | Described in RFC 9559, |
| | | Section 5.1.8.1.1.5 |
+------------+-----------------------------+----------------------+
| 0x63C5 | TagTrackUID | Described in RFC 9559, |
| | | Section 5.1.8.1.1.3 |
+------------+-----------------------------+----------------------+
| 0x63C6 | TagAttachmentUID | Described in RFC 9559, |
| | | Section 5.1.8.1.1.6 |
+------------+-----------------------------+----------------------+
| 0x63C9 | TagEditionUID | Described in RFC 9559, |
| | | Section 5.1.8.1.1.4 |
+------------+-----------------------------+----------------------+
| 0x63CA | TargetType | Described in RFC 9559, |
| | | Section 5.1.8.1.1.2 |
+------------+-----------------------------+----------------------+
| 0x6624 | TrackTranslate | Described in RFC 9559, |
| | | Section 5.1.4.1.27 |
+------------+-----------------------------+----------------------+
| 0x66A5 | TrackTranslateTrackID | Described in RFC 9559, |
| | | Section 5.1.4.1.27.1 |
+------------+-----------------------------+----------------------+
| 0x66BF | TrackTranslateCodec | Described in RFC 9559, |
| | | Section 5.1.4.1.27.2 |
+------------+-----------------------------+----------------------+
| 0x66FC | TrackTranslateEditionUID | Described in RFC 9559, |
| | | Section 5.1.4.1.27.3 |
+------------+-----------------------------+----------------------+
| 0x67C8 | SimpleTag | Described in RFC 9559, |
| | | Section 5.1.8.1.2 |
+------------+-----------------------------+----------------------+
| 0x68CA | TargetTypeValue | Described in RFC 9559, |
| | | Section 5.1.8.1.1.1 |
+------------+-----------------------------+----------------------+
| 0x6911 | ChapProcessCommand | Described in RFC 9559, |
| | | Section 5.1.7.1.4.17 |
+------------+-----------------------------+----------------------+
| 0x6922 | ChapProcessTime | Described in RFC 9559, |
| | | Section 5.1.7.1.4.18 |
+------------+-----------------------------+----------------------+
| 0x6924 | ChapterTranslate | Described in RFC 9559, |
| | | Section 5.1.2.8 |
+------------+-----------------------------+----------------------+
| 0x6933 | ChapProcessData | Described in RFC 9559, |
| | | Section 5.1.7.1.4.19 |
+------------+-----------------------------+----------------------+
| 0x6944 | ChapProcess | Described in RFC 9559, |
| | | Section 5.1.7.1.4.14 |
+------------+-----------------------------+----------------------+
| 0x6955 | ChapProcessCodecID | Described in RFC 9559, |
| | | Section 5.1.7.1.4.15 |
+------------+-----------------------------+----------------------+
| 0x69A5 | ChapterTranslateID | Described in RFC 9559, |
| | | Section 5.1.2.8.1 |
+------------+-----------------------------+----------------------+
| 0x69BF | ChapterTranslateCodec | Described in RFC 9559, |
| | | Section 5.1.2.8.2 |
+------------+-----------------------------+----------------------+
| 0x69FC | ChapterTranslateEditionUID | Described in RFC 9559, |
| | | Section 5.1.2.8.3 |
+------------+-----------------------------+----------------------+
| 0x6D80 | ContentEncodings | Described in RFC 9559, |
| | | Section 5.1.4.1.31 |
+------------+-----------------------------+----------------------+
| 0x6DE7 | MinCache | Reclaimed (RFC 9559, |
| | | (Section 28.16) Appendix A.16) |
+------------+-----------------------------+----------------------+
| 0x6DF8 | MaxCache | Reclaimed (RFC 9559, |
| | | (Section 28.17) Appendix A.17) |
+------------+-----------------------------+----------------------+
| 0x6E67 | ChapterSegmentUUID | Described in RFC 9559, |
| | | Section 5.1.7.1.4.6 |
+------------+-----------------------------+----------------------+
| 0x6EBC | ChapterSegmentEditionUID | Described in RFC 9559, |
| | | Section 5.1.7.1.4.7 |
+------------+-----------------------------+----------------------+
| 0x6FAB | TrackOverlay | Reclaimed (RFC 9559, |
| | | (Section 28.23) Appendix A.23) |
+------------+-----------------------------+----------------------+
| 0x7373 | Tag | Described in RFC 9559, |
| | | Section 5.1.8.1 |
+------------+-----------------------------+----------------------+
| 0x7384 | SegmentFilename | Described in RFC 9559, |
| | | Section 5.1.2.2 |
+------------+-----------------------------+----------------------+
| 0x73A4 | SegmentUUID | Described in RFC 9559, |
| | | Section 5.1.2.1 |
+------------+-----------------------------+----------------------+
| 0x73C4 | ChapterUID | Described in RFC 9559, |
| | | Section 5.1.7.1.4.1 |
+------------+-----------------------------+----------------------+
| 0x73C5 | TrackUID | Described in RFC 9559, |
| | | Section 5.1.4.1.2 |
+------------+-----------------------------+----------------------+
| 0x7446 | AttachmentLink | Described in RFC 9559, |
| | | Section 5.1.4.1.24 |
+------------+-----------------------------+----------------------+
| 0x75A1 | BlockAdditions | Described in RFC 9559, |
| | | Section 5.1.3.5.2 |
+------------+-----------------------------+----------------------+
| 0x75A2 | DiscardPadding | Described in RFC 9559, |
| | | Section 5.1.3.5.7 |
+------------+-----------------------------+----------------------+
| 0x7670 | Projection | Described in RFC 9559, Section |
| | | 5.1.4.1.28.41 |
+------------+-----------------------------+----------------------+
| 0x7671 | ProjectionType | Described in RFC 9559, Section |
| | | 5.1.4.1.28.42 |
+------------+-----------------------------+----------------------+
| 0x7672 | ProjectionPrivate | Described in RFC 9559, Section |
| | | 5.1.4.1.28.43 |
+------------+-----------------------------+----------------------+
| 0x7673 | ProjectionPoseYaw | Described in RFC 9559, Section |
| | | 5.1.4.1.28.44 |
+------------+-----------------------------+----------------------+
| 0x7674 | ProjectionPosePitch | Described in RFC 9559, Section |
| | | 5.1.4.1.28.45 |
+------------+-----------------------------+----------------------+
| 0x7675 | ProjectionPoseRoll | Described in RFC 9559, Section |
| | | 5.1.4.1.28.46 |
+------------+-----------------------------+----------------------+
| 0x78B5 | OutputSamplingFrequency | Described in RFC 9559, |
| | | Section 5.1.4.1.29.2 |
+------------+-----------------------------+----------------------+
| 0x7BA9 | Title | Described in RFC 9559, |
| | | Section 5.1.2.12 |
+------------+-----------------------------+----------------------+
| 0x7D7B | ChannelPositions | Reclaimed (RFC 9559, |
| | | (Section 28.27) Appendix A.27) |
+------------+-----------------------------+----------------------+
| 0x7FFF | Reserved | RFC 9559 |
+------------+-----------------------------+----------------------+
| 0x22B59C | Language | Described in RFC 9559, |
| | | Section 5.1.4.1.19 |
+------------+-----------------------------+----------------------+
| 0x22B59D | LanguageBCP47 | Described in RFC 9559, |
| | | Section 5.1.4.1.20 |
+------------+-----------------------------+----------------------+
| 0x23314F | TrackTimestampScale | Described in RFC 9559, |
| | | Section 5.1.4.1.15 |
+------------+-----------------------------+----------------------+
| 0x234E7A | DefaultDecodedFieldDuration | Described in RFC 9559, |
| | | Section 5.1.4.1.14 |
+------------+-----------------------------+----------------------+
| 0x2383E3 | FrameRate | Reclaimed (RFC 9559, |
| | | (Section 28.26) Appendix A.26) |
+------------+-----------------------------+----------------------+
| 0x23E383 | DefaultDuration | Described in RFC 9559, |
| | | Section 5.1.4.1.13 |
+------------+-----------------------------+----------------------+
| 0x258688 | CodecName | Described in RFC 9559, |
| | | Section 5.1.4.1.23 |
+------------+-----------------------------+----------------------+
| 0x26B240 | CodecDownloadURL | Reclaimed (RFC 9559, |
| | | (Section 28.21) Appendix A.21) |
+------------+-----------------------------+----------------------+
| 0x2AD7B1 | TimestampScale | Described in RFC 9559, |
| | | Section 5.1.2.9 |
+------------+-----------------------------+----------------------+
| 0x2EB524 | UncompressedFourCC | Described in RFC 9559, Section |
| | | 5.1.4.1.28.15 |
+------------+-----------------------------+----------------------+
| 0x2FB523 | GammaValue | Reclaimed (RFC 9559, |
| | | (Section 28.25) Appendix A.25) |
+------------+-----------------------------+----------------------+
| 0x3A9697 | CodecSettings | Reclaimed (RFC 9559, |
| | | (Section 28.19) Appendix A.19) |
+------------+-----------------------------+----------------------+
| 0x3B4040 | CodecInfoURL | Reclaimed (RFC 9559, |
| | | (Section 28.20) Appendix A.20) |
+------------+-----------------------------+----------------------+
| 0x3C83AB | PrevFilename | Described in RFC 9559, |
| | | Section 5.1.2.4 |
+------------+-----------------------------+----------------------+
| 0x3CB923 | PrevUUID | Described in RFC 9559, |
| | | Section 5.1.2.3 |
+------------+-----------------------------+----------------------+
| 0x3E83BB | NextFilename | Described in RFC 9559, |
| | | Section 5.1.2.6 |
+------------+-----------------------------+----------------------+
| 0x3EB923 | NextUUID | Described in RFC 9559, |
| | | Section 5.1.2.5 |
+------------+-----------------------------+----------------------+
| 0x3FFFFF | Reserved | RFC 9559 |
+------------+-----------------------------+----------------------+
| 0x1043A770 | Chapters | Described in RFC 9559, |
| | | Section 5.1.7 |
+------------+-----------------------------+----------------------+
| 0x114D9B74 | SeekHead | Described in RFC 9559, |
| | | Section 5.1.1 |
+------------+-----------------------------+----------------------+
| 0x1254C367 | Tags | Described in RFC 9559, |
| | | Section 5.1.8 |
+------------+-----------------------------+----------------------+
| 0x1549A966 | Info | Described in RFC 9559, |
| | | Section 5.1.2 |
+------------+-----------------------------+----------------------+
| 0x1654AE6B | Tracks | Described in RFC 9559, |
| | | Section 5.1.4 |
+------------+-----------------------------+----------------------+
| 0x18538067 | Segment | Described in RFC 9559, |
| | | Section 5.1 |
+------------+-----------------------------+----------------------+
| 0x1941A469 | Attachments | Described in RFC 9559, |
| | | Section 5.1.6 |
+------------+-----------------------------+----------------------+
| 0x1C53BB6B | Cues | Described in RFC 9559, |
| | | Section 5.1.5 |
+------------+-----------------------------+----------------------+
| 0x1F43B675 | Cluster | Described in RFC 9559, |
| | | Section 5.1.3 |
+------------+-----------------------------+----------------------+
| 0x1FFFFFFF | Reserved | RFC 9559 |
+------------+-----------------------------+----------------------+
Table 55: IDs and Names for Matroska Initial Contents of "Matroska Element IDs assigned by
this document IDs" Registry
27.2. Chapter Codec IDs Registry
This document creates
IANA has created a new IANA registry called the "Matroska Chapter Codec
IDs" registry. The values correspond to the unsigned integer ChapProcessCodecID value
ChapProcessCodecID, ChapterTranslateCodec, and TrackTranslateCodec
values described in Section 5.1.7.1.4.15. 5.1.7.1.4.15, Section 5.1.2.8.2, and
Section 5.1.4.1.27.2, respectively.
To register a new Chapter Codec ID in this registry, one needs a
Chapter Codec ID, a description, a Change Controller (IETF or email
of registrant) registrant), and an optional Reference to a document describing
the Chapter Codec ID.
The Chapter Codec IDs are to be allocated according to the
"Specification Required" policy [RFC8126].
Table 56 shows the initial contents of the "Chapter Codec IDs"
registry. The Change Controller for the initial entries is the IETF.
+==================+=================+===================+
| Chapter Codec ID | Description | Reference |
+==================+=================+===================+
| 0 | Matroska Script | RFC 9559, Section |
| | | 5.1.7.1.4.15 |
+------------------+-----------------+-------------------+
| 1 | DVD-Menu | RFC 9559, Section |
| | | 5.1.7.1.4.15 |
+------------------+-----------------+-------------------+
Table 56: Initial Contents of "Chapter Codec IDs" Registry
27.3. Track Types Registry
IANA has created a new registry called the "Track Types" registry.
The values correspond to the unsigned integer TrackType value
described in Section 5.1.4.1.3.
To register a new Track Type in this registry, one needs a Track Type
value, a description, a Change Controller (IETF or email of
registrant), and an optional Reference to a document describing the
Track Type.
The Track Types are to be allocated according to the "Specification
Required" policy [RFC8126].
Table 57 shows the initial contents of the "Track Types" registry.
The Change Controller for the initial entries is the IETF.
+============+=============+=============================+
| Track Type | Description | Reference |
+============+=============+=============================+
| 1 | video | RFC 9559, Section 5.1.4.1.3 |
+------------+-------------+-----------------------------+
| 2 | audio | RFC 9559, Section 5.1.4.1.3 |
+------------+-------------+-----------------------------+
| 3 | complex | RFC 9559, Section 5.1.4.1.3 |
+------------+-------------+-----------------------------+
| 16 | logo | RFC 9559, Section 5.1.4.1.3 |
+------------+-------------+-----------------------------+
| 17 | subtitle | RFC 9559, Section 5.1.4.1.3 |
+------------+-------------+-----------------------------+
| 18 | buttons | RFC 9559, Section 5.1.4.1.3 |
+------------+-------------+-----------------------------+
| 32 | control | RFC 9559, Section 5.1.4.1.3 |
+------------+-------------+-----------------------------+
| 33 | metadata | RFC 9559, Section 5.1.4.1.3 |
+------------+-------------+-----------------------------+
Table 57: Initial Contents of "Track Types" Registry
27.4. Tags Target Types Registry
IANA has created a new registry called the "Tags Target Types"
registry. The values correspond to the unsigned integer
TargetTypeValue value described in Section 5.1.8.1.1.1.
To register a new Tags Target Type in this registry, one needs a Tags
Target Type value, a description, a Change Controller (IETF or email
of registrant), and an optional Reference to a document describing
the Tags Target Type.
The Tags Track Types are to be allocated according to the
"Specification Required" policy [RFC8126].
Table 58 shows the initial contents of the "Tags Target Types"
registry. The Change Controller for the initial entries is the IETF.
+==================+==========================+===================+
| Tags Target Type | Description | Reference |
+==================+==========================+===================+
| 70 | COLLECTION | RFC 9559, Section |
| | | 5.1.8.1.1.1 |
+------------------+--------------------------+-------------------+
| 60 | EDITION / ISSUE / VOLUME | RFC 9559, Section |
| | / OPUS / SEASON / SEQUEL | 5.1.8.1.1.1 |
+------------------+--------------------------+-------------------+
| 50 | ALBUM / OPERA / CONCERT | RFC 9559, Section |
| | / MOVIE / EPISODE | 5.1.8.1.1.1 |
+------------------+--------------------------+-------------------+
| 40 | PART / SESSION | RFC 9559, Section |
| | | 5.1.8.1.1.1 |
+------------------+--------------------------+-------------------+
| 30 | TRACK / SONG / CHAPTER | RFC 9559, Section |
| | | 5.1.8.1.1.1 |
+------------------+--------------------------+-------------------+
| 20 | SUBTRACK / MOVEMENT / | RFC 9559, Section |
| | SCENE | 5.1.8.1.1.1 |
+------------------+--------------------------+-------------------+
| 10 | SHOT | RFC 9559, Section |
| | | 5.1.8.1.1.1 |
+------------------+--------------------------+-------------------+
Table 58: Initial Contents of "Tags Target Types" Registry
27.5. Alpha Modes Registry
IANA has created a new registry called the "Alpha Modes" registry.
The values correspond to the unsigned integer AlphaMode value
described in Section 5.1.4.1.28.4.
To register a new Alpha Mode in this registry, one needs an Alpha
Mode value, a description, a Change Controller (IETF or email of
registrant), and an optional Reference to a document describing the
Alpha Mode.
The Alpha Modes are to be allocated according to the "First Come
First Served" policy [RFC8126].
ChapProcessCodecID
Table 59 shows the initial contents of the "Alpha Modes" registry.
The Change Controller for the initial entries is the IETF.
+============+=============+================================+
| Alpha Mode | Description | Reference |
+============+=============+================================+
| 0 | none | RFC 9559, Section 5.1.4.1.28.4 |
+------------+-------------+--------------------------------+
| 1 | present | RFC 9559, Section 5.1.4.1.28.4 |
+------------+-------------+--------------------------------+
Table 59: Initial Contents of "Alpha Modes" Registry
27.6. Content Encoding Scopes Registry
IANA has created a new registry called the "Content Encoding Scopes"
registry. The values correspond to the unsigned integer
ContentEncodingScope value described in Section 5.1.4.1.31.3.
To register a new Content Encoding Scope in this registry, one needs
a Content Encoding Scope value, a description, a Change Controller
(IETF or email of "0" registrant), and "1" an optional Reference to a
document describing the Content Encoding Scope.
The Content Encoding Scopes are RESERVED to be allocated according to the IETF
"Specification Required" policy [RFC8126].
Table 60 shows the initial contents of the "Content Encoding Scopes"
registry. The Change Controller for
future use.
27.3. the initial entries is the IETF.
+========================+=============+===================+
| Content Encoding Scope | Description | Reference |
+========================+=============+===================+
| 1 | Block | RFC 9559, Section |
| | | 5.1.4.1.31.3 |
+------------------------+-------------+-------------------+
| 2 | Private | RFC 9559, Section |
| | | 5.1.4.1.31.3 |
+------------------------+-------------+-------------------+
| 4 | Next | RFC 9559, Section |
| | | 5.1.4.1.31.3 |
+------------------------+-------------+-------------------+
Table 60: Initial Contents of "Content Encoding Scopes"
Registry
27.7. Content Encoding Types Registry
IANA has created a new registry called the "Content Encoding Types"
registry. The values correspond to the unsigned integer
ContentEncodingType value described in Section 5.1.4.1.31.4.
To register a new Content Encoding Type in this registry, one needs a
Content Encoding Type value, a description, a Change Controller (IETF
or email of registrant), and an optional Reference to a document
describing the Content Encoding Type.
The Content Encoding Types are to be allocated according to the
"Specification Required" policy [RFC8126].
Table 61 shows the initial contents of the "Content Encoding Types"
registry. The Change Controller for the initial entries is the IETF.
+=======================+=============+===================+
| Content Encoding Type | Description | Reference |
+=======================+=============+===================+
| 0 | Compression | RFC 9559, Section |
| | | 5.1.4.1.31.4 |
+-----------------------+-------------+-------------------+
| 1 | Encryption | RFC 9559, Section |
| | | 5.1.4.1.31.4 |
+-----------------------+-------------+-------------------+
Table 61: Initial Contents of "Content Encoding Types"
Registry
27.8. Compression Algorithms Registry
IANA has created a new registry called the "Compression Algorithms"
registry. The values correspond to the unsigned integer
ContentCompAlgo value described in Section 5.1.4.1.31.6.
To register a new Compression Algorithm in this registry, one needs a
Compression Algorithm value, a description, a Change Controller (IETF
or email of registrant), and an optional Reference to a document
describing the Compression Algorithm.
The Compression Algorithms are to be allocated according to the
"Specification Required" policy [RFC8126].
Table 62 shows the initial contents of the "Compression Algorithms"
registry. The Change Controller for the initial entries is the IETF.
+=======================+=============+===================+
| Compression Algorithm | Description | Reference |
+=======================+=============+===================+
| 0 | zlib | RFC 9559, Section |
| | | 5.1.4.1.31.6 |
+-----------------------+-------------+-------------------+
| 1 | bzlib | RFC 9559, Section |
| | | 5.1.4.1.31.6 |
+-----------------------+-------------+-------------------+
| 2 | lzo1x | RFC 9559, Section |
| | | 5.1.4.1.31.6 |
+-----------------------+-------------+-------------------+
| 3 | Header | RFC 9559, Section |
| | Stripping | 5.1.4.1.31.6 |
+-----------------------+-------------+-------------------+
Table 62: Initial Contents of "Compression Algorithms"
Registry
27.9. Encryption Algorithms Registry
IANA has created a new registry called the "Encryption Algorithms"
registry. The values correspond to the unsigned integer
ContentEncAlgo value described in Section 5.1.4.1.31.9.
To register a new Encryption Algorithm in this registry, one needs an
Encryption Algorithm value, a description, a Change Controller (IETF
or email of registrant), and an optional Reference to a document
describing the Encryption Algorithm.
The Encryption Algorithms are to be allocated according to the "First
Come First Served" policy [RFC8126].
Table 63 shows the initial contents of the "Encryption Algorithms"
registry. The Change Controller for the initial entries is the IETF.
+======================+===============+===================+
| Encryption Algorithm | Description | Reference |
+======================+===============+===================+
| 0 | Not encrypted | RFC 9559, Section |
| | | 5.1.4.1.31.9 |
+----------------------+---------------+-------------------+
| 1 | DES | RFC 9559, Section |
| | | 5.1.4.1.31.9 |
+----------------------+---------------+-------------------+
| 2 | 3DES | RFC 9559, Section |
| | | 5.1.4.1.31.9 |
+----------------------+---------------+-------------------+
| 3 | Twofish | RFC 9559, Section |
| | | 5.1.4.1.31.9 |
+----------------------+---------------+-------------------+
| 4 | Blowfish | RFC 9559, Section |
| | | 5.1.4.1.31.9 |
+----------------------+---------------+-------------------+
| 5 | AES | RFC 9559, Section |
| | | 5.1.4.1.31.9 |
+----------------------+---------------+-------------------+
Table 63: Initial Contents of "Encryption Algorithms"
Registry
27.10. AES Cipher Modes Registry
IANA has created a new registry called the "AES Cipher Modes"
registry. The values correspond to the unsigned integer
AESSettingsCipherMode value described in Section 5.1.4.1.31.12.
To register a new AES Cipher Mode in this registry, one needs an AES
Cipher Mode value, a description, a Change Controller (IETF or email
of registrant), and an optional Reference to a document describing
the AES Cipher Mode.
The AES Cipher Modes are to be allocated according to the "First Come
First Served" policy [RFC8126].
Table 64 shows the initial contents of the "AES Cipher Modes"
registry. The Change Controller for the initial entries is the IETF.
+=================+=============+=================================+
| AES Cipher Mode | Description | Reference |
+=================+=============+=================================+
| 1 | AES-CTR | RFC 9559, Section 5.1.4.1.31.12 |
+-----------------+-------------+---------------------------------+
| 2 | AES-CBC | RFC 9559, Section 5.1.4.1.31.12 |
+-----------------+-------------+---------------------------------+
Table 64: Initial Contents of "AES Cipher Modes" Registry
27.11. Stereo Modes Registry
IANA has created a new registry called the "Stereo Modes" registry.
The values correspond to the unsigned integer StereoMode value
described in Section 5.1.4.1.28.3.
To register a new Stereo Mode in this registry, one needs a Stereo
Mode value, a description, a Change Controller (IETF or email of
registrant), and an optional Reference to a document describing the
Stereo Mode.
The Stereo Modes are to be allocated according to the "Specification
Required" policy [RFC8126].
Table 65 shows the initial contents of the "Stereo Modes" registry.
The Change Controller for the initial entries is the IETF.
+=============+====================+================================+
| Stereo Mode | Description | Reference |
+=============+====================+================================+
| 0 | mono | RFC 9559, Section |
| | | 5.1.4.1.28.3 |
+-------------+--------------------+--------------------------------+
| 1 | Side By Side (left | RFC 9559, Section |
| | first) | 5.1.4.1.28.3 |
+-------------+--------------------+--------------------------------+
| 2 | Top Bottom (right | RFC 9559, Section |
| | first) | 5.1.4.1.28.3 |
+-------------+--------------------+--------------------------------+
| 3 | Top Bottom (left | RFC 9559, Section |
| | first) | 5.1.4.1.28.3 |
+-------------+--------------------+--------------------------------+
| 4 | Checkboard (right | RFC 9559, Section |
| | first) | 5.1.4.1.28.3 |
+-------------+--------------------+--------------------------------+
| 5 | Checkboard (left | RFC 9559, Section |
| | first) | 5.1.4.1.28.3 |
+-------------+--------------------+--------------------------------+
| 6 | Row Interleaved | RFC 9559, Section |
| | (right first) | 5.1.4.1.28.3 |
+-------------+--------------------+--------------------------------+
| 7 | Row Interleaved | RFC 9559, Section |
| | (left first) | 5.1.4.1.28.3 |
+-------------+--------------------+--------------------------------+
| 8 | Column Interleaved | RFC 9559, Section |
| | (right first) | 5.1.4.1.28.3 |
+-------------+--------------------+--------------------------------+
| 9 | Column Interleaved | RFC 9559, Section |
| | (left first) | 5.1.4.1.28.3 |
+-------------+--------------------+--------------------------------+
| 10 | Anaglyph (cyan/ | RFC 9559, Section |
| | red) | 5.1.4.1.28.3 |
+-------------+--------------------+--------------------------------+
| 11 | Side By Side | RFC 9559, Section |
| | (right first) | 5.1.4.1.28.3 |
+-------------+--------------------+--------------------------------+
| 12 | Anaglyph (green/ | RFC 9559, Section |
| | magenta) | 5.1.4.1.28.3 |
+-------------+--------------------+--------------------------------+
| 13 | Both in Block | RFC 9559, Section |
| | (left first) | 5.1.4.1.28.3 |
+-------------+--------------------+--------------------------------+
| 14 | Both in Block | RFC 9559, Section |
| | (right first) | 5.1.4.1.28.3 |
+-------------+--------------------+--------------------------------+
Table 65: Initial Contents of "Stereo Modes" Registry
27.12. Display Units Registry
IANA has created a new registry called the "Display Units" registry.
The values correspond to the unsigned integer DisplayUnit value
described in Section 5.1.4.1.28.14.
To register a new Display Unit in this registry, one needs a Display
Unit value, a description, a Change Controller (IETF or email of
registrant), and an optional Reference to a document describing the
Display Unit.
The Display Units are to be allocated according to the "Specification
Required" policy [RFC8126].
Table 66 shows the initial contents of the "Display Units" registry.
The Change Controller for the initial entries is the IETF.
+==============+===============+=================================+
| Display Unit | Description | Reference |
+==============+===============+=================================+
| 0 | Pixels | RFC 9559, Section 5.1.4.1.28.14 |
+--------------+---------------+---------------------------------+
| 1 | Centimeters | RFC 9559, Section 5.1.4.1.28.14 |
+--------------+---------------+---------------------------------+
| 2 | Inches | RFC 9559, Section 5.1.4.1.28.14 |
+--------------+---------------+---------------------------------+
| 3 | Display | RFC 9559, Section 5.1.4.1.28.14 |
| | Aspect Ration | |
+--------------+---------------+---------------------------------+
| 4 | Unknown | RFC 9559, Section 5.1.4.1.28.14 |
+--------------+---------------+---------------------------------+
Table 66: Initial Contents of "Display Units" Registry
27.13. Projection Types Registry
IANA has created a new registry called the "Projection Types"
registry. The values correspond to the unsigned integer
ProjectionType value described in Section 5.1.4.1.28.42.
To register a new Projection Type in this registry, one needs a
Projection Type value, a description, a Change Controller (IETF or
email of registrant), and an optional Reference to a document
describing the Projection Type.
The Projection Types are to be allocated according to the "First Come
First Served" policy [RFC8126].
Table 67 shows the initial contents of the "Projection Types"
registry. The Change Controller for the initial entries is the IETF.
+=================+=================+===================+
| Projection Type | Description | Reference |
+=================+=================+===================+
| 0 | Rectangular | RFC 9559, Section |
| | | 5.1.4.1.28.42 |
+-----------------+-----------------+-------------------+
| 1 | Equirectangular | RFC 9559, Section |
| | | 5.1.4.1.28.42 |
+-----------------+-----------------+-------------------+
| 2 | Cubemap | RFC 9559, Section |
| | | 5.1.4.1.28.42 |
+-----------------+-----------------+-------------------+
| 3 | Mesh | RFC 9559, Section |
| | | 5.1.4.1.28.42 |
+-----------------+-----------------+-------------------+
Table 67: Initial Contents of "Projection Types" Registry
27.14. Track Plane Types Registry
IANA has created a new registry called the "Track Plane Types"
registry. The values correspond to the unsigned integer
TrackPlaneType value described in Section 5.1.4.1.30.4.
To register a new Track Plane Type in this registry, one needs a
Track Plane Type value, a description, a Change Controller (IETF or
email of registrant), and an optional Reference to a document
describing the Track Plane Type.
The Track Plane Types are to be allocated according to the "First
Come First Served" policy [RFC8126].
Table 68 shows the initial contents of the "Track Plane Types"
registry. The Change Controller for the initial entries is the IETF.
+==================+=============+================================+
| Track Plane Type | Description | Reference |
+==================+=============+================================+
| 0 | Left Eye | RFC 9559, Section 5.1.4.1.30.4 |
+------------------+-------------+--------------------------------+
| 1 | Right Eye | RFC 9559, Section 5.1.4.1.30.4 |
+------------------+-------------+--------------------------------+
| 2 | Background | RFC 9559, Section 5.1.4.1.30.4 |
+------------------+-------------+--------------------------------+
Table 68: Initial Contents of "Track Plane Types" Registry
27.15. Horizontal Chroma Sitings Registry
IANA has created a new registry called the "Horizontal Chroma
Sitings" registry. The values correspond to the unsigned integer
ChromaSitingHorz value described in Section 5.1.4.1.28.23.
To register a new Horizontal Chroma Siting in this registry, one
needs a Horizontal Chroma Siting value, a description, a Change
Controller (IETF or email of registrant), and an optional Reference
to a document describing the Horizontal Chroma Siting.
The Horizontal Chroma Sitings are to be allocated according to the
"First Come First Served" policy [RFC8126].
Table 69 shows the initial contents of the "Horizontal Chroma
Sitings" registry. The Change Controller for the initial entries is
the IETF.
+==========================+=============+===================+
| Horizontal Chroma Siting | Description | Reference |
+==========================+=============+===================+
| 0 | unspecified | RFC 9559, Section |
| | | 5.1.4.1.28.23 |
+--------------------------+-------------+-------------------+
| 1 | left | RFC 9559, Section |
| | collocated | 5.1.4.1.28.23 |
+--------------------------+-------------+-------------------+
| 2 | half | RFC 9559, Section |
| | | 5.1.4.1.28.23 |
+--------------------------+-------------+-------------------+
Table 69: Initial Contents of "Horizontal Chroma Sitings"
Registry
27.16. Vertical Chroma Sitings Registry
IANA has created a new registry called the "Vertical Chroma Sitings"
registry. The values correspond to the unsigned integer
ChromaSitingVert value described in Section 5.1.4.1.28.24.
To register a new Vertical Chroma Siting in this registry, one needs
a Vertical Chroma Siting value, a description, a Change Controller
(IETF or email of registrant), and an optional Reference to a
document describing the Vertical Chroma Siting.
The Vertical Chroma Sitings are to be allocated according to the
"First Come First Served" policy [RFC8126].
Table 70 shows the initial contents of the "Vertical Chroma Sitings"
registry. The Change Controller for the initial entries is the IETF.
+========================+=============+===================+
| Vertical Chroma Siting | Description | Reference |
+========================+=============+===================+
| 0 | unspecified | RFC 9559, Section |
| | | 5.1.4.1.28.24 |
+------------------------+-------------+-------------------+
| 1 | top | RFC 9559, Section |
| | collocated | 5.1.4.1.28.24 |
+------------------------+-------------+-------------------+
| 2 | half | RFC 9559, Section |
| | | 5.1.4.1.28.24 |
+------------------------+-------------+-------------------+
Table 70: Initial Contents of "Vertical Chroma Sitings"
Registry
27.17. Color Ranges Registry
IANA has created a new registry called the "Color Ranges" registry.
The values correspond to the unsigned integer Range value described
in Section 5.1.4.1.28.25.
To register a new Color Range in this registry, one needs a Color
Range value, a description, a Change Controller (IETF or email of
registrant), and an optional Reference to a document describing the
Color Range.
The Color Ranges are to be allocated according to the "Specification
Required" policy [RFC8126].
Table 71 shows the initial contents of the "Color Ranges" registry.
The Change Controller for the initial entries is the IETF.
+=============+===============================+===================+
| Color Range | Description | Reference |
+=============+===============================+===================+
| 0 | unspecified | RFC 9559, Section |
| | | 5.1.4.1.28.25 |
+-------------+-------------------------------+-------------------+
| 1 | broadcast range | RFC 9559, Section |
| | | 5.1.4.1.28.25 |
+-------------+-------------------------------+-------------------+
| 2 | full range | RFC 9559, Section |
| | | 5.1.4.1.28.25 |
+-------------+-------------------------------+-------------------+
| 3 | defined by MatrixCoefficients | RFC 9559, Section |
| | / TransferCharacteristics | 5.1.4.1.28.25 |
+-------------+-------------------------------+-------------------+
Table 71: Initial Contents of "Color Ranges" Registry
27.18. Media Types
Matroska files and streams are found in three main forms: audio-video
files, audio-only audio-
video, audio-only, and occasionally with (occasionally) stereoscopic video tracks.
Historically video.
Historically, Matroska files and streams have used the following
media types with a an "x-" prefix. For better compatibility compatibility, a system
SHOULD be able to handle both formats. Newer systems SHOULD NOT use
the historic format and use the format that follows the [RFC6838] format in
[RFC6838] instead.
Please register
IANA has registered three media types, types per the [RFC6838] templates are below:
27.3.1. (see
[RFC6838]) in the following subsections.
27.18.1. For files containing video tracks Files Containing Video Tracks
Type name: video
Subtype name: matroska
Required parameters: N/A
Optional parameters: N/A
Encoding considerations: as As per this document RFCs 9559 and RFC8794 8794
Security considerations: See Section 26. 26 of RFC 9559.
Interoperability considerations: Due to the extensibility of
Matroska, it is possible to encounter files with unknown but valid
EBML Elements. Readers should be ready to handle this case. The
fixed byte order, octet boundaries boundaries, and UTF-8 usage allow for
broad
interoparability. interoperability.
Published specification: THISRFC RFC 9559
Applications that use this media type: FFmpeg, VLC, ... etc.
Fragment identifier considerations: N/A
Additional information:
*
Deprecated alias names for this type: video/x-matroska
*
Magic number(s): N/A
*
File extension(s): mkv
*
Macintosh file type code(s): N/A
Person & email address to contact for further information: IETF
CELLAR WG cellar@ietf.org (cellar@ietf.org)
Intended usage: COMMON
Restrictions on usage: None
Author: IETF CELLAR WG
Change controller: IETF
Provisional registration? (standards tree only): No
27.3.2.
27.18.2. For files containing audio tracks Files Containing Audio Tracks with no video tracks No Video Tracks
Type name: audio
Subtype name: matroska
Required parameters: N/A
Optional parameters: N/A
Encoding considerations: as As per this document RFCs 9559 and RFC8794 8794
Security considerations: See Section 26. 26 of RFC 9559.
Interoperability considerations: Due to the extensibility of
Matroska, it is possible to encounter files with unknown but valid
EBML Elements. Readers should be ready to handle this case. The
fixed byte order, octet boundaries boundaries, and UTF-8 usage allow for
broad
interoparability. interoperability.
Published specification: THISRFC RFC 9559
Applications that use this media type: FFmpeg, VLC, ... etc.
Fragment identifier considerations: N/A
Additional information:
*
Deprecated alias names for this type: audio/x-matroska
*
Magic number(s): N/A
*
File extension(s): mka
*
Macintosh file type code(s): N/A
Person & email address to contact for further information: IETF
CELLAR WG cellar@ietf.org (cellar@ietf.org)
Intended usage: COMMON
Restrictions on usage: None
Author: IETF CELLAR WG
Change controller: IETF
Provisional registration? (standards tree only): No
27.3.3.
27.18.3. For files containing Files Containing a stereoscopic video track Stereoscopic Video Track
Type name: video
Subtype name: matroska-3d
Required parameters: N/A
Optional parameters: N/A
Encoding considerations: as As per this document RFCs 9559 and RFC8794 8794
Security considerations: See Section 26. 26 of RFC 9559.
Interoperability considerations: Due to the extensibility of
Matroska, it is possible to encounter files with unknown but valid
EBML Elements. Readers should be ready to handle this case. The
fixed byte order, octet boundaries boundaries, and UTF-8 usage allow for
broad
interoparability. interoperability.
Published specification: THISRFC RFC 9559
Applications that use this media type: FFmpeg, VLC, ... etc.
Fragment identifier considerations: N/A
Additional information:
*
Deprecated alias names for this type: video/x-matroska-3d
*
Magic number(s): N/A
*
File extension(s): mk3d
*
Macintosh file type code(s): N/A
Person & email address to contact for further information: IETF
CELLAR WG cellar@ietf.org (cellar@ietf.org)
Intended usage: COMMON
Restrictions on usage: None
Author: IETF CELLAR WG
Change controller: IETF
Provisional registration? (standards tree only): No
29.
28. References
28.1. Normative References
[BCP47] Phillips, A., Ed. and M. Davis, Ed., "Tags for Identifying
Languages", BCP 47, RFC 5646, DOI 10.17487/RFC5646, September
2009, <https://www.rfc-editor.org/info/rfc5646>.
[CIE-1931] Commission Internationale de l'Eclairage, Wikipedia, "CIE 1931 Standard
Colorimetric System", 1931, color space",
<https://en.wikipedia.org/wiki/CIE_1931_color_space>.
[ISO639-2] United States Library Of Congress, International Organization for Standardization, "Codes for
the Representation of Names of Languages", ISO 639-2:1998, 21 639-2,
December 2017, <https://www.loc.gov/standards/iso639-
2/php/code_list.php>.
[ISO9899] International Organization for Standardization,
"Information technology -- Programming languages -- C",
ISO/IEC 9899:2011,
2011, <https://www.iso.org/standard/57853.html>. 9899:2018, June 2018,
<https://www.iso.org/standard/74528.html>.
[ITU-H.273] International Telecommunication Union,
ITU-T, "Coding-independent code points for video signal
type identification", ITU ITU-T Recommendation H.273, 24
September 2021, <https://www.itu.int/rec/T-REC-H.273/en>. 2023,
<https://www.itu.int/rec/T-REC-H.273-202309-P/en>.
[RFC1950] Deutsch, P. and J. Gailly, "ZLIB Compressed Data Format
Specification version 3.3", RFC 1950,
DOI 10.17487/RFC1950, May 1996,
<https://www.rfc-editor.org/info/rfc1950>.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>.
[RFC4122] Leach, P., Mealling, M., and R. Salz, "A Universally
Unique IDentifier (UUID) URN Namespace", RFC 4122,
DOI 10.17487/RFC4122, July 2005,
<https://www.rfc-editor.org/info/rfc4122>.
[RFC5646] Phillips, A., Ed. and M. Davis, Ed., "Tags for Identifying
Languages", BCP 47, RFC 5646, DOI 10.17487/RFC5646,
September 2009, <https://www.rfc-editor.org/info/rfc5646>.
[RFC6838] Freed, N., Klensin, J., and T. Hansen, "Media Type
Specifications and Registration Procedures", BCP 13,
RFC 6838, DOI 10.17487/RFC6838, January 2013,
<https://www.rfc-editor.org/info/rfc6838>.
[RFC8081] Lilley, C., "The "font" Top-Level Media Type", RFC 8081,
DOI 10.17487/RFC8081, February 2017,
<https://www.rfc-editor.org/info/rfc8081>.
[RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for
Writing an IANA Considerations Section in RFCs", BCP 26,
RFC 8126, DOI 10.17487/RFC8126, June 2017,
<https://www.rfc-editor.org/info/rfc8126>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>.
[RFC8794] Lhomme, S., Rice, D., and M. Bunkus, "Extensible Binary
Meta Language", RFC 8794, DOI 10.17487/RFC8794, July 2020,
<https://www.rfc-editor.org/info/rfc8794>.
30.
28.2. Informative References
[AVIFormat] Microsoft,
Microsoft Corporation, "AVI RIFF File Reference", 31 May 2018, June
2023, <https://docs.microsoft.com/en-
us/windows/win32/directshow/avi-riff-file-reference>.
[Blowfish] Schneier, B., "The Blowfish Encryption Algorithm", 1993,
<https://www.schneier.com/academic/blowfish/>.
[BZIP2] Seward, J., "bzip2", 18 July 1996, 2019,
<https://sourceware.org/bzip2/>.
[DivXTrickTrack] "DivX Trick Track Extensions", 14
"Smooth FF/RW", December 2010,
<https://web.archive.org/web/20101222001148/
http://labs.divx.com/node/16601>.
[DivXWorldFonts] "DivX World Fonts Extensions", 14
"World Fonts", December 2010,
<https://web.archive.org/web/20110214132246/
http://labs.divx.com/node/16602>.
[DVD-Video]
DVD Forum, "DVD-Books: Part 3 DVD-Video Book", 1 November
1995, <http://www.dvdforum.org/>.
[FIPS.197] US
[Err7189] RFC Errata, "Erratum ID 7189", RFC 8794,
<https://www.rfc-editor.org/errata/eid7189>.
[Err7191] RFC Errata, "Erratum ID 7191", RFC 8794,
<https://www.rfc-editor.org/errata/eid7191>.
[FIPS197] National Institute of Standards and Technology, Technology (NIST),
"Advanced Encryption Standard (AES)", FIPS PUB 197,
DOI 10.6028/NIST.FIPS.197, 26 November 2001,
<https://csrc.nist.gov/publications/detail/fips/197/
final>.
[FIPS.46-3] US
[FIPS46-3] National Institute of Standards and Technology, Technology (NIST),
"Data Encryption Standard (DES)", FIPS PUB 46, 25 October
1999,
<https://csrc.nist.gov/publications/detail/fips/46/3/
archive/1999-10-25>.
[FourCC-RGB] Silicon.dk ApS,
FOURCC, "RGB Pixel Format FourCCs", pixel formats",
<https://web.archive.org/web/20160609214806/
https://www.fourcc.org/rgb.php>. [FourCC-RGB] Silicon.dk ApS,
"RGB Pixel Format FourCCs",
<https://web.archive.org/web/20160609214806/
[FourCC-YUV] Silicon.dk ApS,
FOURCC, "YUV Pixel Format FourCCs", pixel formats",
<https://web.archive.org/web/20160609214806/
https://www.fourcc.org/yuv.php>.
[JPEG] International Telegraph and Telephone Consultative Committee,
"Digital Compression and Coding of Continuous- Tone Still
Images", ITU ITU-T, "INFORMATION TECHNOLOGY - DIGITAL COMPRESSION AND
CODING OF CONTINUOUS-TONE STILL IMAGES - REQUIREMENTS AND
GUIDELINES", ITU-T Recommendation T.81, September 1992,
<https://www.w3.org/Graphics/JPEG/itu-t81.pdf>.
[libmatroska]
"libmatroska", March 2024,
<https://github.com/Matroska-Org/libmatroska>.
[LZO] Tarreau, W., Rodgman, R., W. and M. Oberhumer, "Lempel-Ziv- Oberhumer
compression", 30 R. Rodgman, "LZO stream format as
understood by Linux's LZO decompressor", October 2018,
<https://www.kernel.org/doc/Documentation/lzo.txt>.
[MatroskaCodec]
Lhomme, S., Bunkus, M., and D. Rice, "Media "Matroska Media
Container Codec Specifications", Work in Progress,
Internet-Draft,
draft-ietf-cellar-codec-10, 12 April 2021, draft-ietf-cellar-codec-13, 5 May 2024,
<https://datatracker.ietf.org/doc/html/draft-ietf-cellar-
codec-10>.
codec-13>.
[MatroskaTags]
Lhomme, S., Bunkus, M., and D. Rice, "Matroska Media
Container Tag Specifications", Work in Progress, Internet-
Draft, draft-ietf-cellar-tags-10, 12 April 2021, draft-ietf-cellar-tags-13, 5 May 2024,
<https://datatracker.ietf.org/doc/html/draft-ietf-cellar-
tags-10>.
tags-13>.
[MCF] "Media Container Format", 17 July 2002, "MCF specification, introduction",
<http://mukoli.free.fr/mcf/>.
[MSRGB] Microsoft, "WMF Compression Microsoft Corporation, "Compression Enumeration", June
2021, <https://learn.microsoft.com/en-
us/openspecs/windows_protocols/ms-wmf/4e588f70-bd92-4a6f-
b77f-35d0feaf7a57>.
[MSYUV16] Microsoft, Microsoft Corporation, "10-bit and 16-bit YUV Video
Formats",
<https://learn.microsoft.com/en-us/windows/win32/
medfound/10-bit-and-16-bit-yuv-video-formats>. November 2022, <https://learn.microsoft.com/en-
us/windows/win32/medfound/10-bit-and-16-bit-yuv-video-
formats>.
[MSYUV8] Microsoft, Microsoft Corporation, "Recommended 8-Bit YUV Formats for
Video Rendering",
<https://learn.microsoft.com/en-
us/windows/win32/medfound/recommended-8-bit-yuv-formats-
for-video-rendering>. January 2021,
<https://learn.microsoft.com/en-us/windows/win32/medfound/
recommended-8-bit-yuv-formats-for-video-rendering>.
[RFC0959] Postel, J. and J. Reynolds, "File Transfer Protocol",
STD 9, RFC 959, DOI 10.17487/RFC0959, October 1985,
<https://www.rfc-editor.org/info/rfc959>.
[RFC2083] Boutell, T., "PNG (Portable Network Graphics)
Specification Version 1.0", RFC 2083,
DOI 10.17487/RFC2083, March 1997,
<https://www.rfc-editor.org/info/rfc2083>.
[RFC3533] Pfeiffer, S., "The Ogg Encapsulation Format Version 0",
RFC 3533, DOI 10.17487/RFC3533, May 2003,
<https://www.rfc-editor.org/info/rfc3533>.
[RFC4732] Handley, M., Ed., Rescorla, E., Ed., and IAB, "Internet
Denial-of-Service Considerations", RFC 4732,
DOI 10.17487/RFC4732, December 2006,
<https://www.rfc-editor.org/info/rfc4732>.
[RFC9110] Fielding, R., Ed., Nottingham, M., Ed., and J. Reschke,
Ed., "HTTP Semantics", STD 97, RFC 9110,
DOI 10.17487/RFC9110, June 2022,
<https://www.rfc-editor.org/info/rfc9110>.
[SMB-CIFS] Microsoft Corporation, "Common "[MS-CIFS]: Common Internet File
System (CIFS) Protocol", 1 October 2020,
<https://winprotocoldoc.blob.core.windows.net/
productionwindowsarchives/MS-CIFS/%5bMS-CIFS%5d.pdf>.
[SP.800-38A] US
[SP800-38A]
National Institute of Standards and Technology, Technology (NIST),
"Recommendation for Block Cipher Modes of Operation:
Methods and Techniques", DOI 10.6028/NIST.SP.800-38A, 1 NIST
Special Publication 800-38A, December 2001,
<https://csrc.nist.gov/publications/detail/fips/197/ final>.
[SP.800-67] US
<https://nvlpubs.nist.gov/nistpubs/Legacy/SP/
nistspecialpublication800-38a.pdf>.
[SP800-67] National Institute of Standards and Technology, Technology (NIST),
"Recommendation for the Triple Data Encryption Algorithm
(TDEA) Block Cipher", DOI 10.6028/10.6028/NIST.SP.800-67r2, 1 10.6028/NIST.SP.800-67r2, NIST
Special Publication 800-67, November 2017, <https://csrc.nist.gov/publications/detail/sp/800-67/rev-
2/final>.
<https://nvlpubs.nist.gov/nistpubs/SpecialPublications/
NIST.SP.800-67r2.pdf>.
[Twofish] Schneier, B., Kelsey, J., Whiting, D., Wagner, D., Hall,
C., and N. Ferguson, "Twofish: A 128-Bit Block Cipher", 15
June 1998,
<https://www.schneier.com/academic/twofish/>.
<https://www.schneier.com/academic/archives/1998/06/
twofish_a_128-bit_bl.html>.
[WebM-Enc] Galligan, F., "WebM Encryption", 19 September 2016,
<https://www.webmproject.org/docs/webm-encryption/>.
[WebVTT] Pieters, S., Pfeiffer, S., Ed., Jaegenstedt, P., and I.
Hickson,
"WebVTT Cue Identifier", 4 "WebVTT: The Web Video Text Tracks Format", W3C
Candidate Recommendation, April 2019,
<https://www.w3.org/TR/webvtt1/#webvtt-cue-identifier>.
28. Annex A:
<https://www.w3.org/TR/2019/CR-webvtt1-20190404/>.
Appendix A. Historic Deprecated Elements
As Matroska has evolved since 2002 2002, many parts that were considered
for use in the format were never used and often incorrectly designed.
Many of the elements that were then defined then are not found in any
known files but were part of public specs. DivX also had a few
custom elements that were designed for custom features.
We
In this appendix, we list these elements that have a known ID that SHOULD
NOT be reused to avoid colliding with existing files. They These might be
reassigned by IANA in the future if there are no more IDs for a given
size. A short description of what each ID was used for is included,
but the text is not normative.
28.1.
A.1. SilentTracks Element
type / id: master / 0x5854
path: \Segment\Cluster\SilentTracks
documentation: The list of tracks that are not used in that part of
the stream. It is useful when using overlay tracks on for seeking or
to decide
deciding what track to use.
28.2.
A.2. SilentTrackNumber Element
type / id: uinteger / 0x58D7
path: \Segment\Cluster\SilentTracks\SilentTrackNumber
documentation: One of the track number numbers that are is not used from now on
in the stream. It could change later if not specified as silent
in a further Cluster.
28.3.
A.3. BlockVirtual Element
type / id: binary / 0xA2
path: \Segment\Cluster\BlockGroup\BlockVirtual
documentation: A Block with no data. It must be stored in the
stream at the place the real Block would be in display order.
28.4.
A.4. ReferenceVirtual Element
type / id: integer / 0xFD
path: \Segment\Cluster\BlockGroup\ReferenceVirtual
documentation: The Segment Position of the data that would otherwise
be in position of the virtual block.
28.5.
A.5. Slices Element
type / id: master / 0x8E
path: \Segment\Cluster\BlockGroup\Slices
documentation: Contains slices description.
28.6.
A.6. TimeSlice Element
type / id: master / 0xE8
path: \Segment\Cluster\BlockGroup\Slices\TimeSlice
documentation: Contains extra time information about the data
contained in the Block. Being able to interpret this Element element is
not required for playback.
28.7.
A.7. LaceNumber Element
type / id: uinteger / 0xCC
path: \Segment\Cluster\BlockGroup\Slices\TimeSlice\LaceNumber
documentation: The reverse number of the frame in the lace (0 is the
last frame, 1 is the next to last, etc.). Being able to interpret
this Element element is not required for playback.
28.8.
A.8. FrameNumber Element
type / id: uinteger / 0xCD
path: \Segment\Cluster\BlockGroup\Slices\TimeSlice\FrameNumber
documentation: The number of the frame to generate from this lace
with this delay (allow you to generate (allows for the generation of many frames from the
same Block/Frame).
28.9.
A.9. BlockAdditionID Element
type / id: uinteger / 0xCB
path: \Segment\Cluster\BlockGroup\Slices\TimeSlice\BlockAdditionID
documentation: The ID of the BlockAdditional Element element (0 is the main
Block).
28.10.
A.10. Delay Element
type / id: uinteger / 0xCE
path: \Segment\Cluster\BlockGroup\Slices\TimeSlice\Delay
documentation: The delay to apply to the Element, element, expressed in Track
Ticks; see Section 11.1.
28.11.
A.11. SliceDuration Element
type / id: uinteger / 0xCF
path: \Segment\Cluster\BlockGroup\Slices\TimeSlice\SliceDuration
documentation: The duration to apply to the Element, element, expressed in
Track Ticks; see Section 11.1.
28.12.
A.12. ReferenceFrame Element
type / id: master / 0xC8
path: \Segment\Cluster\BlockGroup\ReferenceFrame
documentation: Contains information about the last reference frame.
See [DivXTrickTrack].
28.13.
A.13. ReferenceOffset Element
type / id: uinteger / 0xC9
path: \Segment\Cluster\BlockGroup\ReferenceFrame\ReferenceOffset
documentation: The relative offset, in bytes, from the previous
BlockGroup element for this Smooth FF/RW video track to the
containing BlockGroup element. See [DivXTrickTrack].
28.14.
A.14. ReferenceTimestamp Element
type / id: uinteger / 0xCA
path: \Segment\Cluster\BlockGroup\ReferenceFrame\ReferenceTimestamp
documentation: The timestamp of the BlockGroup pointed to by
ReferenceOffset, expressed in Track Ticks; see Section 11.1. See
[DivXTrickTrack].
28.15.
A.15. EncryptedBlock Element
type / id: binary / 0xAF
path: \Segment\Cluster\EncryptedBlock
documentation: Similar to SimpleBlock, see SimpleBlock (see Section 10.2, 10.2), but the
data inside the Block are Transformed (encrypt (encrypted and/or signed).
28.16.
A.16. MinCache Element
type / id: uinteger / 0x6DE7
path: \Segment\Tracks\TrackEntry\MinCache
documentation: The minimum number of frames a player should be able
to cache during playback. If set to 0, the reference pseudo-cache
system is not used.
28.17.
A.17. MaxCache Element
type / id: uinteger / 0x6DF8
path: \Segment\Tracks\TrackEntry\MaxCache
documentation: The maximum cache size necessary to store referenced
frames in and the current frame. 0 means no cache is needed.
28.18.
A.18. TrackOffset Element
type / id: integer / 0x537F
path: \Segment\Tracks\TrackEntry\TrackOffset
documentation: A value to add to the Block's Timestamp, expressed in
Matroska Ticks -- i.e., in nanoseconds; see Section 11.1. This
can be used to adjust the playback offset of a track.
28.19.
A.19. CodecSettings Element
type / id: utf-8 / 0x3A9697
path: \Segment\Tracks\TrackEntry\CodecSettings
documentation: A string describing the encoding setting used.
28.20.
A.20. CodecInfoURL Element
type / id: string / 0x3B4040
path: \Segment\Tracks\TrackEntry\CodecInfoURL
documentation: A URL to find information about the codec used.
28.21.
A.21. CodecDownloadURL Element
type / id: string / 0x26B240
path: \Segment\Tracks\TrackEntry\CodecDownloadURL
documentation: A URL to download information about the codec used.
28.22.
A.22. CodecDecodeAll Element
type / id: uinteger / 0xAA
path: \Segment\Tracks\TrackEntry\CodecDecodeAll
documentation: Set to 1 if the codec can decode potentially damaged
data.
28.23.
A.23. TrackOverlay Element
type / id: uinteger / 0x6FAB
path: \Segment\Tracks\TrackEntry\TrackOverlay
documentation: Specify that this track is an overlay track for the
Track specified (in the u-integer). That This means that when this
track has a gap on SilentTracks, the overlay track should be used
instead. The order of multiple TrackOverlay matters, matters; the first
one is the one that should be used. If the first one is not found
found, it should be the second, etc.
28.24.
A.24. AspectRatioType Element
type / id: uinteger / 0x54B3
path: \Segment\Tracks\TrackEntry\Video\AspectRatioType
documentation: Specify Specifies the possible modifications to the aspect
ratio.
28.25.
A.25. GammaValue Element
type / id: float / 0x2FB523
path: \Segment\Tracks\TrackEntry\Video\GammaValue
documentation: Gamma Value.
28.26. value.
A.26. FrameRate Element
type / id: float / 0x2383E3
path: \Segment\Tracks\TrackEntry\Video\FrameRate
documentation: Number of frames per second. This value is
Informational
informational only. It is intended for constant frame rate
streams,
streams and should not be used for a variable frame rate
TrackEntry.
28.27.
A.27. ChannelPositions Element
type / id: binary / 0x7D7B
path: \Segment\Tracks\TrackEntry\Audio\ChannelPositions
documentation: Table of horizontal angles for each successive
channel.
28.28.
A.28. TrickTrackUID Element
type / id: uinteger / 0xC0
path: \Segment\Tracks\TrackEntry\TrickTrackUID
documentation: The TrackUID of the Smooth FF/RW video in the paired
EBML structure corresponding to this video track. See
[DivXTrickTrack].
28.29.
A.29. TrickTrackSegmentUID Element
type / id: binary / 0xC1
path: \Segment\Tracks\TrackEntry\TrickTrackSegmentUID
documentation: The SegmentUID SegmentUUID of the Segment containing the track
identified by TrickTrackUID. See [DivXTrickTrack].
28.30.
A.30. TrickTrackFlag Element
type / id: uinteger / 0xC6
path: \Segment\Tracks\TrackEntry\TrickTrackFlag
documentation: Set to 1 if this video track is a Smooth FF/RW track.
If set to 1, MasterTrackUID and MasterTrackSegUID should be
present
present, and BlockGroups for this track must contain
ReferenceFrame structures. Otherwise, TrickTrackUID and
TrickTrackSegUID must be present if this track has a corresponding
Smooth FF/RW track. See [DivXTrickTrack].
28.31.
A.31. TrickMasterTrackUID Element
type / id: uinteger / 0xC7
path: \Segment\Tracks\TrackEntry\TrickMasterTrackUID
documentation: The TrackUID of the video track in the paired EBML
structure that corresponds to this Smooth FF/RW track. See
[DivXTrickTrack].
28.32.
A.32. TrickMasterTrackSegmentUID Element
type / id: binary / 0xC4
path: \Segment\Tracks\TrackEntry\TrickMasterTrackSegmentUID
documentation: The SegmentUID SegmentUUID of the Segment containing the track
identified by MasterTrackUID. See [DivXTrickTrack].
28.33.
A.33. ContentSignature Element
type / id: binary / 0x47E3
path: \Segment\Tracks\TrackEntry\ContentEncodings\ContentEncoding\Co
ntentEncryption\ContentSignature
documentation: A cryptographic signature of the contents.
28.34.
A.34. ContentSigKeyID Element
type / id: binary / 0x47E4
path: \Segment\Tracks\TrackEntry\ContentEncodings\ContentEncoding\Co
ntentEncryption\ContentSigKeyID
documentation: This is the ID of the private key that the data was
signed with.
28.35.
A.35. ContentSigAlgo Element
type / id: uinteger / 0x47E5
path: \Segment\Tracks\TrackEntry\ContentEncodings\ContentEncoding\Co
ntentEncryption\ContentSigAlgo
documentation: The algorithm used for the signature.
28.36.
A.36. ContentSigHashAlgo Element
type / id: uinteger / 0x47E6
path: \Segment\Tracks\TrackEntry\ContentEncodings\ContentEncoding\Co
ntentEncryption\ContentSigHashAlgo
documentation: The hash algorithm used for the signature.
28.37.
A.37. CueRefCluster Element
type / id: uinteger / 0x97
path: \Segment\Cues\CuePoint\CueTrackPositions\CueReference\CueRefCl
uster
documentation: The Segment Position of the Cluster containing the
referenced Block.
28.38.
A.38. CueRefNumber Element
type / id: uinteger / 0x535F
path: \Segment\Cues\CuePoint\CueTrackPositions\CueReference\CueRefNu
mber
documentation: Number of the referenced Block of Track X in the
specified Cluster.
28.39.
A.39. CueRefCodecState Element
type / id: uinteger / 0xEB
path: \Segment\Cues\CuePoint\CueTrackPositions\CueReference\CueRefCo
decState
documentation: The Segment Position of the Codec State corresponding
to this referenced Element. element. 0 means that the data is taken from
the initial Track Entry.
28.40. TrackEntry.
A.40. FileReferral Element
type / id: binary / 0x4675
path: \Segment\Attachments\AttachedFile\FileReferral
documentation: A binary value that a track/codec can refer to when
the attachment is needed.
28.41.
A.41. FileUsedStartTime Element
type / id: uinteger / 0x4661
path: \Segment\Attachments\AttachedFile\FileUsedStartTime
documentation: The timestamp at which this optimized font attachment
comes into context, expressed in Segment Ticks Ticks, which is are based on
TimestampScale. See [DivXWorldFonts].
28.42.
A.42. FileUsedEndTime Element
type / id: uinteger / 0x4662
path: \Segment\Attachments\AttachedFile\FileUsedEndTime
documentation: The timestamp at which this optimized font attachment
goes out of context, expressed in Segment Ticks Ticks, which is are based
on TimestampScale. See [DivXWorldFonts].
28.43.
A.43. TagDefaultBogus Element
type / id: uinteger / 0x44B4
path: \Segment\Tags\Tag\+SimpleTag\TagDefaultBogus
documentation: A variant of the TagDefault element with a bogus
Element
element ID; see Section 5.1.8.1.2.4.
Authors' Addresses
Steve Lhomme
Email: slhomme@matroska.org
Moritz Bunkus
Email: moritz@bunkus.org
Dave Rice
Email: dave@dericed.com