GstObuMetadata/GstObuMetadata Basics: Difference between revisions
mNo edit summary |
No edit summary |
||
| Line 4: | Line 4: | ||
== AV1 Standards Overview == | == AV1 Standards Overview == | ||
== Open bitstream units (OBU) == | == Open bitstream units (OBU) == | ||
An AV1 coded video is comprise of one or more temporal units. Each temorar unit is fed with a sequence of OBUs of different types like: Sequence Header, Temporal Delimiter, Frame Header, Tile Group, Metadata, Frame, Redundant Frame Header, Tile List and Padding. Each OBU contains a header and a payload byte, the header indicates the type of OBU and specifies the payload size. | |||
The GstObuMetadata plugin focuses on the OBU Metadata which carries information of different types such as high dynamic range, scalability, and timecode. | |||
== References == | == References == | ||
Revision as of 23:43, 20 February 2024
| GstObuMetadata |
|---|
 |
| GstObuMetadata Basics |
| Getting Started |
| User Guide |
| Examples |
| Contact Us |
AV1 Standards Overview
Open bitstream units (OBU)
An AV1 coded video is comprise of one or more temporal units. Each temorar unit is fed with a sequence of OBUs of different types like: Sequence Header, Temporal Delimiter, Frame Header, Tile Group, Metadata, Frame, Redundant Frame Header, Tile List and Padding. Each OBU contains a header and a payload byte, the header indicates the type of OBU and specifies the payload size.
The GstObuMetadata plugin focuses on the OBU Metadata which carries information of different types such as high dynamic range, scalability, and timecode.
References
Links to the AV1 websites: