Difference between revisions of "Ogg"
Jump to navigation
Jump to search
| Line 1: | Line 1: | ||
| − | + | The '''Ogg''' transport bitstream is designed to provide framing, error protection and seeking structure for higher-level codec streams that consist of raw, unencapsulated data packets, such as the [[Vorbis]] audio codec or [[Theora]] video codec. | |
| + | == Design constraints for Ogg bitstreams == | ||
| − | + | * True streaming; we must not need to seek to build a 100% complete bitstream. | |
| − | + | * Use no more than approximately 1-2% of bitstream bandwidth for packet boundary marking, high-level framing, sync and seeking. | |
| − | + | * Specification of absolute position within the original sample stream. | |
| − | + | * Simple mechanism to ease limited editing, such as a simplified concatenation mechanism. | |
| − | + | * Detection of corruption, recapture after error and direct, random access to data at arbitrary positions in the bitstream. | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | + | == Projects using Ogg == | |
| − | |||
| − | + | * [[Vorbis]] | |
| + | * [[Theora]] | ||
| + | * [[FLAC]] | ||
| + | * [[Speex]] | ||
| + | * [[Icecast]] | ||
| + | * [[Ogg_Skeleton]] | ||
| + | * [http://www.annodex.net/ CMML & Annodex] | ||
| + | * [[Writ]] | ||
| − | + | == External links == | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | [http://www. | + | * [http://www.xiph.org/ogg/doc/ Ogg documentation] |
| − | + | * [http://www.ietf.org/rfc/rfc3533.txt Ogg RFC] | |
| − | |||
| − | [http://www. | ||
| − | |||
| − | |||
| − | |||
| − | |||
Revision as of 02:57, 8 July 2006
The Ogg transport bitstream is designed to provide framing, error protection and seeking structure for higher-level codec streams that consist of raw, unencapsulated data packets, such as the Vorbis audio codec or Theora video codec.
Design constraints for Ogg bitstreams
- True streaming; we must not need to seek to build a 100% complete bitstream.
- Use no more than approximately 1-2% of bitstream bandwidth for packet boundary marking, high-level framing, sync and seeking.
- Specification of absolute position within the original sample stream.
- Simple mechanism to ease limited editing, such as a simplified concatenation mechanism.
- Detection of corruption, recapture after error and direct, random access to data at arbitrary positions in the bitstream.