Ogg

Ogg
Filename extension .ogg, .ogv, .oga, .ogx, .ogm, .spx, .opus
Internet media type video/ogg, audio/ogg, application/ogg
Magic number OggS
Developed by Xiph.Org Foundation
Type of format Container format
Container for Vorbis, Theora, Opus, FLAC, Dirac, and others.
Open format? Yes
libogg
Developer(s) Xiph.Org Foundation
Stable release 1.3.2 / May 27, 2014 (2014-05-27)
Operating system Cross-platform
Type reference implementation (multiplexer/demultiplexer)
License BSD-style license[1]
Website Xiph.org downloads

Ogg is a free, open container format maintained by the Xiph.Org Foundation. The creators of the Ogg format state that it is unrestricted by software patents[2] and is designed to provide for efficient streaming and manipulation of high quality digital multimedia.

"Ogg" is derived from "ogging", jargon from the computer game Netrek:

3.3 Ogging: This is the art of killing a carrier, or potential carrier, by a suicide run.[3]

The Ogg container format can multiplex a number of independent streams for audio, video, text (such as subtitles), and metadata.

In the Ogg multimedia framework, Theora provides a lossy video layer. The audio layer is most commonly provided by the music-oriented Vorbis format but other codec options include the compression codec Opus, the lossless audio compression codec FLAC, and OggPCM.

Before 2007, the .ogg filename extension was used for all files whose content used the Ogg container format. Since 2007, the Xiph.Org Foundation recommends that .ogg only be used for Ogg Vorbis audio files. The Xiph.Org Foundation decided to create a new set of file extensions and media types to describe different types of content such as .oga for audio only files, .ogv for video with or without sound (including Theora), and .ogx for multiplexed Ogg.[4]

As of August 4, 2011, the current version of the Xiph.Org Foundation's reference implementation, is libogg 1.3.0.[5] Another version, libogg2, has been in development, but is awaiting a rewrite as of 2008.[6] Both software libraries are free software, released under the New BSD License. Ogg reference implementation was separated from Vorbis on September 2, 2000.[7]

Because the format is free, and its reference implementation is not subject to restrictions associated with copyright, Ogg's various codecs have been incorporated into a number of different free and proprietary media players, both commercial and non-commercial, as well as portable media players and GPS receivers from different manufacturers.

Naming

It is sometimes assumed that the name "Ogg" comes from the character of Nanny Ogg in Terry Pratchett's Discworld novels, but the Ogg developers say that is not true.[8] Ogg is derived from ogging, jargon from the computer game Netrek, which came to mean doing something forcefully, possibly without consideration of the drain on future resources. At its inception, the Ogg project was thought to be somewhat ambitious given the power of the PC hardware of the time.[8] Still, to quote the same reference: "Vorbis, on the other hand is named after the Terry Pratchett character from the book Small Gods".

The Ogg Vorbis project started in 1993. It was originally named "Squish" but that name was already trademarked, so the project underwent a name change. The new name, "OggSquish", was used until 2001 when it was changed again to "Ogg". Ogg has since come to refer to the container format, which is now part of the larger Xiph.org multimedia project. Today, "Squish" (now known as "Vorbis") refers to a particular codec typically stored in the Ogg container.[9]

File format

The "Ogg" bitstream format, spearheaded by the Xiph.Org Foundation, has been created as the framework of a larger initiative aimed at developing a set of components for the coding and decoding of multimedia content, which are available free of charge and freely re-implementable in software.

The format consists of chunks of data each called an "Ogg page". Each page begins with the characters, "OggS", to identify the file as Ogg format.

A "serial number" and "page number" in the page header identifies each page as part of a series of pages making up a bitstream. Multiple bitstreams may be multiplexed in the file where pages from each bitstream are ordered by the seek time of the contained data. Bitstreams may also be appended to existing files, a process known as "chaining", to cause the bitstreams to be decoded in sequence.

A BSD-licensed library, called "libvorbis", is available to encode and decode data from "Vorbis" streams. Independent Ogg implementations are used in several projects such as RealPlayer and a set of DirectShow filters.[10]

Page structure

Main article: Ogg page

The following is the field layout of an Ogg page header:

Capture pattern – 32 bits
The capture pattern or sync code is a magic number used to ensure synchronization when parsing Ogg files. Every page starts with the four ASCII character sequence, "OggS". This assists in resynchronizing a parser in cases where data has been lost or is corrupted, and is a sanity check before commencing parsing the page structure.
Version – 8 bits
This field indicates the version of the Ogg bitstream format, to allow for future expansion. It is currently mandated to be 0.
Header type – 8 bits
This is an 8 bit field of flags, which indicates the type of page that follows.
Bit Value Flag Page type
0 0x01 Continuation The first packet on this page is a continuation of the previous packet in the logical bitstream.
1 0x02 BOS Beginning Of Stream. This page is the first page in the logical bitstream. The BOS flag must be set on the first page of every logical bitstream, and must not be set on any other page.
2 0x04 EOS End Of Stream. This page is the last page in the logical bitstream. The EOS flag must be set on the final page of every logical bitstream, and must not be set on any other page.
Granule position – 64 bits
A granule position is the time marker in Ogg files. It is an abstract value, whose meaning is determined by the codec. It may, for example, be a count of the number of samples, the number of frames or a more complex scheme.
Bitstream serial number – 32 bits
This field is a serial number that identifies a page as belonging to a particular logical bitstream. Each logical bitstream in a file has a unique value, and this field allows implementations to deliver the pages to the appropriate decoder. In a typical Vorbis and Theora file, one stream is the audio (Vorbis), and the other is the video (Theora)
Page sequence number – 32 bits
This field is a monotonically increasing field for each logical bitstream. The first page is 0, the second 1, etc. This allows implementations to detect when data has been lost.
Checksum – 32 bits
This field provides a CRC32 checksum of the data in the entire page (including the page header, calculated with the checksum field set to 0). This allows verification that the data has not been corrupted since it was created. Pages that fail the checksum should be discarded. The checksum is generated using a polynomial value of 0x04C11DB7.
Page segments – 8 bits
This field indicates the number of segments that exist in this page. It also indicates how many bytes are in the segment table that follows this field. There can be a maximum of 255 segments in any one page.
Segment table
The segment table is a vector of 8-bit values, each indicating the length of the corresponding segment within the page body. The number of segments is determined from the preceding Page Segments field. Each segment is between 0 and 255 bytes in length.

The segments provide a way to group segments into packets, which are meaningful units of data for the decoder. When the segment's length is indicated to be 255, this indicates that the following segment is to be concatenated to this one and is part of the same packet. When the segment's length is 0–254, this indicates that this segment is the final segment in this packet. Where a packet's length is a multiple of 255, the final segment is length 0.

Where the final packet continues on the next page, the final segment value is 255, and the continuation flag is set on the following page to indicate that the start of the new page is a continuation of last page.

Metadata

Currently, there is no official standard for including metadata in Ogg containers. Implementation is still a long way off as of Quarter 3, 2007. The Xiph.Org Foundation are currently welcoming suggestions and feedback. Suggested metadata implementation methods include the following:[11]

Metadata must currently be included in the codec. There is fairly good software support for Vorbis metadata—often referred to as comments. But software support for Theora and FLAC comments in Ogg containers is very limited.

History

The Play Ogg web button

The Ogg project began with a simple audio compression package as part of a larger project in 1993.[8] The software was originally named Squish but due to an existing trade mark it was renamed to OggSquish. This name was later used for the whole Ogg project. In 1997, the Xiphophorus OggSquish was described as "an attempt both to create a flexible compressed audio format for modern audio applications as well as to provide the first audio format that is common on any and every modern computer platform".[12] The OggSquish was in 2000 referred to as "a group of several related multimedia and signal processing projects". In 2000, two projects were in active development for planned release: Ogg Vorbis format and libvorbis - the reference implementation of Vorbis. Research also included work on future video and lossless audio coding.[8][13][14][15][16] In 2001, OggSquish was renamed to Ogg and it was described as "the umbrella for a group of several related multimedia and signal processing projects".[17] Ogg has come to stand for the file format, as part of the larger Xiph.org multimedia project. Squish became just the name of one of the Ogg codecs.[9] In 2009, Ogg is described as "a multimedia container format, and the native file and stream format for the Xiph.org multimedia codecs".[18]

Ogg reference implementation was separated from Vorbis on September 2, 2000.[7]

In May 2003, two Internet RFCs were published relating to the format. The Ogg bitstream was defined in RFC 3533 (which is classified as 'informative') and its Internet content type (application/ogg) in RFC 3534 (which is, as of 2006, a proposed standard protocol). In September 2008, RFC 3534 was obsoleted by RFC 5334, which added content types video/ogg, audio/ogg and filename extensions .ogx, .ogv, .oga, .spx.

OGM

In 2002, the lack of formal video support in Ogg resulted in the creation of the OGM file format, a hack on Ogg that allowed embedding of video from the Microsoft DirectShow framework into an Ogg-based wrapper. OGM was initially supported only by closed source Windows-only tools, but the code base was subsequently opened. Later, video (and subtitle) support were formally specified for Ogg but in a manner incompatible with OGM. Independently, the Matroska container format reached maturity and provided another alternative for people interested in combining Vorbis audio and arbitrary video codecs. As a result, OGM is no longer supported or developed and is formally discouraged by Xiph.org.[19] Today, video in Ogg is found with the .ogv file extension, which is formally specified and officially supported.

2006

Although Ogg hadn't reached anywhere near the ubiquity of the MPEG standards[20][21] (e.g., MP3/MP4), as of 2006, it was commonly used to encode free content (such as free music, multimedia on Wikimedia projects and Creative Commons files) and had started to be supported by a significant minority of digital audio players. Also supporting the Ogg format were many popular video game engines, including Doom 3, Unreal Tournament 2004, Halo: Combat Evolved, Jets n Guns, Mafia: The City of Lost Heaven, Myst IV: Revelation, Stepmania, Serious Sam: The Second Encounter, Lineage 2, Vendetta Online, Battlefield 2, and the Grand Theft Auto engines, as well as the audio files of the Java-based game, Minecraft. The more popular Vorbis codec had built-in support on many software players, and extensions were available for nearly all the rest.

2007

On May 16, 2007, the Free Software Foundation started a campaign to increase the use of Vorbis "as an ethically, legally and technically superior audio alternative to the proprietary MP3 format."[22] People were also encouraged to support the campaign by adding a web button to their website or blog. For those who don't want to download and use FSF's suggested Ogg player (VLC), the Xiph.Org Foundation had an official codec[23] for QuickTime-based applications in Windows and Mac OS X, such as iTunes players and iMovie applications; and Windows users could install a Windows Media Player Ogg codec.[24]

2009

By June 30, 2009, the Ogg container, through the use of the Theora and Vorbis, was the only container format included in Firefox 3.5 web browser's implementation of the HTML 5 <video> and <audio> elements.[25][26] This was in accordance with the original recommendation outlined in, but later removed from, the HTML 5 draft specification (see Ogg controversy).

2010

On March 3, 2010, a technical analysis by an FFmpeg developer was critical about the general purpose abilities of Ogg as a multimedia container format.[27] In a lengthy response, the creator of Ogg refuted these claims.[28] By December 2010, browsers supporting Ogg had surpassed browsers supporting both MP4 and WebM.[29]

Ogg codecs

Ogg is only a container format. The actual audio or video encoded by a codec is stored inside an Ogg container. Ogg containers may contain streams encoded with multiple codecs, for example, a video file with sound contains data encoded by both an audio codec and a video codec.

Being a container format, Ogg can embed audio and video in various formats[30][31] (such as Dirac, MNG, CELT, MPEG-4, MP3 and others) but Ogg was intended to be, and usually is, used with the following Xiph.org free codecs:

See also

References

  1. ↑ "Sample Xiph.Org Variant of the BSD License". Xiph.Org Foundation. Retrieved 2009-08-29.
  2. ↑ http://www.vorbis.com/faq/#what
  3. ↑ http://www.netrek.org/clueguides/ogging-101.html
  4. ↑ "MIME Types and File Extensions". XiphWiki. 2007-09-07. Retrieved 2007-09-10.
  5. ↑ Montgomery, Christopher (2011-08-04). "libogg 1.3.0 release". ogg-dev (Mailing list). Retrieved 2011-09-23.
  6. ↑ Giles, Ralph (2008-01-05). "r14372 - in trunk/theora: . lib/dec lib/enc". xiph-commits (Mailing list). This library was never released and now looks like it needs to be redesigned.
  7. 1 2 Xiph.Org (2002-07-19) Ogg releases - libogg-1.0.tar.gz - CHANGES. Retrieved 2009-09-01.
  8. 1 2 3 4 "Xiph.org: naming". Xiph.org Foundation. 2006-01-07. Retrieved 2008-02-16. At the time Ogg was starting out, most personal computers were i386s and the i486 was new. I remember thinking about the algorithms I was considering, "Whoa, that's heavyweight. People are going to need a 486 to run that..." While the software ogged the music, there wasn't much processor left for anything else.
  9. 1 2 "Xiph.org: naming". Xiph.org Foundation. 2006-01-07. Retrieved 2009-09-02.
  10. ↑ Directshow Filters for Ogg Vorbis
  11. ↑ "Ogg Metadata". Xiph Wiki. 2005-12-20. Retrieved 2007-08-31.
  12. ↑ Christopher Montgomery (1997). "Ogg 98.9". Xiphophorus company. Retrieved 2009-09-02.
  13. ↑ Xiph.org (2000-01-18). "OggSquish Vorbis encoding format documentation". Archive.org. Retrieved 2008-09-02.
  14. ↑ Xiph.org (2000-01-18). "OggSquish logical and physical bitstream overview". Archive.org. Retrieved 2008-09-02.
  15. 1 2 Xiphophorus company (2001-04-05). "The Ogg project homepage". Archive.org. Retrieved 2009-09-02.
  16. ↑ Xiph.org (2001-12-04). "The Ogg project homepage". Archive.org. Retrieved 2008-09-02.
  17. ↑ Xiphophorus company (2001-12-04). "The Ogg project homepage". Archive.org. Retrieved 2009-09-02.
  18. ↑ "The Ogg container format". Xiph.Org Foundation. 2006-01-07. Retrieved 2009-09-02.
  19. ↑ "does not support OGM". Backup at WayBack Machine. 2004-07-07.
  20. ↑ "MP3's Loss, Open Source's Gain". Wired.com. 2007-02-23. Retrieved 2010-03-04.
  21. ↑ "MP3's Loss, Open Source's Gain". Wired.com. 2007-02-23. Retrieved 2015-02-04.
  22. ↑ "'Play Ogg': FSF launches free audio format campaign" (in Latin). Fsf.org. Retrieved 2010-03-04.
  23. ↑ "Foundation: Ogg QuickTime Components for iTunes and iMovie (Windows and Mac OS X)". Xiph.org. Retrieved 2010-03-04.
  24. ↑ "Directshow Filters for Ogg Vorbis, Speex, Theora and FLAC". Xiph.org. 2010-02-22. Retrieved 2010-03-04.
  25. ↑ "Mozilla Developer Center - HTML - Element - Video". September 2009. Retrieved 2009-12-28.
  26. ↑ "Mozilla Developer Center - HTML - Element - Audio". September 2009. Retrieved 2009-12-28.
  27. ↑ Rullgard, Mans (2010-03-03). "Ogg objections". hardwarebug.org. Retrieved 2010-05-02.
  28. ↑ Montgomery, Christopher (2010-04-27). "Monty - In Defense of Ogg's Good Name". people.xiph.org/~xiphmont. Retrieved 2010-05-02.
  29. ↑ "Over 50% of web users now support HTML5 Video". 2011-01-07. Retrieved 2011-06-26.
  30. ↑ "MIME Types and File Extensions". XiphWiki. 2009-10-04. Retrieved 2009-10-24.
  31. ↑ "RFC 5334 - Ogg Media Types". IETF. September 2008. Retrieved 2009-10-24.
  32. ↑ "OggPCM - XiphWiki". wiki.xiph.org. 2012. Retrieved 29 July 2012.
  33. ↑ Ralph Giles (2000-12-19) vorbis-dev - Tarkin video codec?, Xiph.org vorbis-dev mailinglist. Retrieved 2009-09-06.
  34. ↑ Jack Moffitt (2001-01-03) vorbis-dev - Tarkin at last, Xiph.org vorbis-dev mailinglist. Retrieved 2009-09-06.
  35. ↑ Chris Montgomery (2001-02-11) Tarkin developer mailing list, Retrieved on 2009-09-06
  36. ↑ Michael Smith (2005-08-29) Tarkin. Retrieved 2009-09-06.
  37. ↑ Dirac specification - integration of Dirac encoded video into commonly used container formats Retrieved on 2009-07-05
  38. ↑ "OggWrit". Xiph.org. 2007-11-10. Retrieved 2015-04-13. at best incomplete and at worst completely broken. In any case, it is not an "official" Xiph spec/codec

External links

Look up Ogg in Wiktionary, the free dictionary.
Wikimedia Commons has media related to Ogg files.
Look up ogg in Wiktionary, the free dictionary.
This article is issued from Wikipedia - version of the Wednesday, February 10, 2016. The text is available under the Creative Commons Attribution/Share Alike but additional terms may apply for the media files.