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.
Ogg derives from "ogging", jargon from the computer game Netrek. Ogg is not an acronym and should not be mentioned as "OGG".
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
The Ogg encapsulation format can be handled with the following libraries:
- libogg: libogg svn (C, cross-platform) Low-level Ogg parsing and writing.
- liboggz: liboggz svn or liboggz (C, cross-platform) liboggz wraps libogg and provides features such as seeking.
- the Ogg Directshow filters: see illiminable (C++, Win32)
- HOgg (pure Haskell)
- JOrbis (pure Java) contains com.jcraft.jogg
- Mutagen (pure Python)