Category:Ogg Mappings: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
(explain what an Ogg mapping is) |
||
| Line 1: | Line 1: | ||
[[Category:Ogg]] | [[Category:Ogg]] | ||
The way that data for each codec is stored in an Ogg container is called its "mapping" into Ogg. | |||
Data for a particular track of content is stored in a single Ogg logical bitstream. The mapping for each codec usually specifies: | |||
* The structure of the beginning-of-stream (BOS) page | |||
* Whether or not the codec uses [[VorbisComment]] metadata | |||
* Any other headers | |||
Additional information may be stored in a corresponding [[OggSkeleton]] fisbone entry. | |||
Latest revision as of 16:33, 11 July 2009
The way that data for each codec is stored in an Ogg container is called its "mapping" into Ogg.
Data for a particular track of content is stored in a single Ogg logical bitstream. The mapping for each codec usually specifies:
- The structure of the beginning-of-stream (BOS) page
- Whether or not the codec uses VorbisComment metadata
- Any other headers
Additional information may be stored in a corresponding OggSkeleton fisbone entry.