Ogg: Difference between revisions
Jump to navigation
Jump to search
Maikmerten (talk | contribs) (spam) |
|||
| Line 10: | Line 10: | ||
* Simple mechanism to ease limited editing, such as a simplified concatenation mechanism. | * 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. | * Detection of corruption, recapture after error and direct, random access to data at arbitrary positions in the bitstream. | ||
== Projects using Ogg == | == Projects using Ogg == | ||
Revision as of 11:00, 10 June 2005
About
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.