Ogg Skeleton 4 - Revision history

Martin.leese: /* Previous version */ No point displaying a broken link

2016-05-23T16:03:25Z

Previous version: No point displaying a broken link

← Older revision		Revision as of 16:03, 23 May 2016
Line 13:		Line 13:
	=== Previous version ===		=== Previous version ===

	The previous version of Ogg Skeleton was version 3, and its specification can be found on the wiki page [[Ogg Skeleton 3]]~~. It is not available at http://svn.annodex.net/standards/draft-pfeiffer-oggskeleton-current.txt anymore~~.		The previous version of Ogg Skeleton was version 3, and its specification can be found on the wiki page [[Ogg Skeleton 3]].

	=== How to describe the logical bitstreams within an Ogg container? ===		=== How to describe the logical bitstreams within an Ogg container? ===

MrZeus: /* Previous version */

2016-05-23T09:31:39Z

Previous version

← Older revision		Revision as of 09:31, 23 May 2016
Line 13:		Line 13:
	=== Previous version ===		=== Previous version ===

	The previous version of Ogg Skeleton was version 3, and its specification can be found on the wiki page [[Ogg Skeleton 3]]~~, or~~ at ~~[http://svn.annodex.net/standards/draft-pfeiffer-oggskeleton-current.txt~~ http://svn.annodex.net/standards/draft-pfeiffer-oggskeleton-current.txt].		The previous version of Ogg Skeleton was version 3, and its specification can be found on the wiki page [[Ogg Skeleton 3]]. It is not available at http://svn.annodex.net/standards/draft-pfeiffer-oggskeleton-current.txt anymore.

	=== How to describe the logical bitstreams within an Ogg container? ===		=== How to describe the logical bitstreams within an Ogg container? ===

Silvia: updated liboggz link

2016-05-22T07:50:15Z

updated liboggz link

← Older revision		Revision as of 07:50, 22 May 2016
Line 245:		Line 245:
	* speexenc (with --skeleton) & speexdec		* speexenc (with --skeleton) & speexdec
	* the Ogg Directshow filters: see [http://www.illiminable.com/ogg/ illiminable]		* the Ogg Directshow filters: see [http://www.illiminable.com/ogg/ illiminable]
	* liboggz: [~~http~~://~~svn~~.~~annodex~~.~~net~~/liboggz~~/ liboggz svn] or [http://annodex~~.~~net/software/liboggz/ liboggz~~]		* liboggz: [https://git.xiph.org/liboggz.git git]
	* the Annodex technology: ~~[http://www.annodex.net/ annodex.net]~~		* the Annodex technology: (not available any more)
	* [http://www.kfish.org/software/hogg/ HOgg] (Haskell)		* [http://www.kfish.org/software/hogg/ HOgg] (Haskell)
	* many more ...		* many more ...

Cpearce at 21:57, 11 May 2011

2011-05-11T21:57:25Z

← Older revision		Revision as of 21:57, 11 May 2011
Line 77:		Line 77:
	The Skeleton logical bitstream starts with an ident header that contains information about all of the logical bitstreams and is mapped into the Skeleton bos page.		The Skeleton logical bitstream starts with an ident header that contains information about all of the logical bitstreams and is mapped into the Skeleton bos page.
	The first 8 bytes provide the magic identifier "fishead\0".		The first 8 bytes provide the magic identifier "fishead\0".
	After the fishead follows a set of secondary header packets, each of which contains information about one logical bitstream. These secondary header packets are identified by an 8 byte code of "fisbone\0". The Skeleton logical bitstream has no actual content packets. Its ~~eos~~ page is included into the stream before any data pages of the other logical bitstreams appear and contains a packet of length 0.		After the fishead follows a set of secondary header packets, each of which contains information about one logical bitstream. These secondary header packets are identified by an 8 byte code of "fisbone\0". The Skeleton logical bitstream has no actual content packets. Its EOS page is included into the stream before any data pages of the other logical bitstreams appear and contains a packet of length 0. Note the EOS packet appears by itself on its own page (the "EOS page").

	The fishead ident header looks as follows ([http://annodex.org/w/images/3/39/FishHeads.JPG inspiration]):		The fishead ident header looks as follows ([http://annodex.org/w/images/3/39/FishHeads.JPG inspiration]):
Line 232:		Line 232:
	* the bos pages of all the other logical bistreams come next (a requirement of Ogg)		* the bos pages of all the other logical bistreams come next (a requirement of Ogg)
	* the secondary header pages of all logical bitstreams come next, including Skeleton's secondary header packets (the fisbone and index packets)		* the secondary header pages of all logical bitstreams come next, including Skeleton's secondary header packets (the fisbone and index packets)
	* the Skeleton ~~eos~~ page ~~end~~ the control section of the Ogg stream before any content pages of any of the other logical bitstreams appear.		* the Skeleton EOS packet appears by itself on the the last page of the Skeleton stream (the "EOS page").
			* the Skeleton EOS page ends the control section of the Ogg stream before any content pages of any of the other logical bitstreams appear.

	== Development ==		== Development ==

Martin.leese: Clarity

2010-11-24T19:06:29Z

Clarity

← Older revision		Revision as of 19:06, 24 November 2010
Line 1:		Line 1:
	'''Ogg Skeleton''' provides structuring information for multitrack [[Ogg]] files. It is compatible with Ogg [[Theora]] and provides extra clues for synchronization and content negotiation such as language selection. Skeleton version 4.0 also provides keyframe indexes to enable optimal seeking over high-latency connections, such as the internet.		'''Ogg Skeleton''' provides structuring information for multitrack [[Ogg]] files. It is compatible with Ogg [[Theora]] and provides extra clues for synchronization and content negotiation such as language selection. The latest version of Skeleton, version 4.0, also provides keyframe indexes to enable optimal seeking over high-latency connections, such as the internet.

	Ogg is a generic container format, enabling interleaving of several tracks of frame-wise encoded content in a time-multiplexed manner. As an example, an Ogg physical bitstream could encapsulate several tracks of video encoded in Theora and multiple tracks of audio encoded in Speex or Vorbis or FLAC at the same time. A player that decodes such a bitstream could then, for example, play one video channel as the main video playback, alpha-blend another one on top of it (e.g. a caption track), play a main Vorbis audio together with several FLAC audio tracks simultaneously (e.g. as sound effects), and provide a choice of Speex channels (e.g. providing commentary in different languages). Such a file is generally possible to create with Ogg, it is however not possible to generically parse such a file, seek on it, understand what codecs are contained in such a file, and dynamically handle and play back such content.		Ogg is a generic container format, enabling interleaving of several tracks of frame-wise encoded content in a time-multiplexed manner. As an example, an Ogg physical bitstream could encapsulate several tracks of video encoded in Theora and multiple tracks of audio encoded in Speex or Vorbis or FLAC at the same time. A player that decodes such a bitstream could then, for example, play one video channel as the main video playback, alpha-blend another one on top of it (e.g. a caption track), play a main Vorbis audio together with several FLAC audio tracks simultaneously (e.g. as sound effects), and provide a choice of Speex channels (e.g. providing commentary in different languages). Such a file is generally possible to create with Ogg, it is however not possible to generically parse such a file, seek on it, understand what codecs are contained in such a file, and dynamically handle and play back such content.

Martin.leese: Undo revision 12686 by Martin.leese (Talk) Unnecessary

2010-11-24T19:01:38Z

Undo revision 12686 by Martin.leese (Talk) Unnecessary

← Older revision		Revision as of 19:01, 24 November 2010
Line 1:		Line 1:
	'''Ogg Skeleton''' provides structuring information for multitrack [[Ogg]] files. It is compatible with Ogg [[Theora]] and provides extra clues for synchronization and content negotiation such as language selection. Skeleton version 4.0 also provides keyframe indexes to enable optimal seeking over high-latency connections, such as the internet. ~~(The previous version was [[Ogg Skeleton 3]].)~~		'''Ogg Skeleton''' provides structuring information for multitrack [[Ogg]] files. It is compatible with Ogg [[Theora]] and provides extra clues for synchronization and content negotiation such as language selection. Skeleton version 4.0 also provides keyframe indexes to enable optimal seeking over high-latency connections, such as the internet.

	Ogg is a generic container format, enabling interleaving of several tracks of frame-wise encoded content in a time-multiplexed manner. As an example, an Ogg physical bitstream could encapsulate several tracks of video encoded in Theora and multiple tracks of audio encoded in Speex or Vorbis or FLAC at the same time. A player that decodes such a bitstream could then, for example, play one video channel as the main video playback, alpha-blend another one on top of it (e.g. a caption track), play a main Vorbis audio together with several FLAC audio tracks simultaneously (e.g. as sound effects), and provide a choice of Speex channels (e.g. providing commentary in different languages). Such a file is generally possible to create with Ogg, it is however not possible to generically parse such a file, seek on it, understand what codecs are contained in such a file, and dynamically handle and play back such content.		Ogg is a generic container format, enabling interleaving of several tracks of frame-wise encoded content in a time-multiplexed manner. As an example, an Ogg physical bitstream could encapsulate several tracks of video encoded in Theora and multiple tracks of audio encoded in Speex or Vorbis or FLAC at the same time. A player that decodes such a bitstream could then, for example, play one video channel as the main video playback, alpha-blend another one on top of it (e.g. a caption track), play a main Vorbis audio together with several FLAC audio tracks simultaneously (e.g. as sound effects), and provide a choice of Speex channels (e.g. providing commentary in different languages). Such a file is generally possible to create with Ogg, it is however not possible to generically parse such a file, seek on it, understand what codecs are contained in such a file, and dynamically handle and play back such content.

Saoshyant: /* Previous version */

2010-11-24T18:16:41Z

Previous version

← Older revision		Revision as of 18:16, 24 November 2010
Line 13:		Line 13:
	=== Previous version ===		=== Previous version ===

	The previous version of Ogg Skeleton was version 3, and its specification can be found on the wiki page [[Ogg Skeleton]], or at [http://svn.annodex.net/standards/draft-pfeiffer-oggskeleton-current.txt http://svn.annodex.net/standards/draft-pfeiffer-oggskeleton-current.txt].		The previous version of Ogg Skeleton was version 3, and its specification can be found on the wiki page [[Ogg Skeleton 3]], or at [http://svn.annodex.net/standards/draft-pfeiffer-oggskeleton-current.txt http://svn.annodex.net/standards/draft-pfeiffer-oggskeleton-current.txt].

	=== How to describe the logical bitstreams within an Ogg container? ===		=== How to describe the logical bitstreams within an Ogg container? ===

Martin.leese: Added link to Ogg Skeleton 3

2010-11-23T21:01:30Z

Added link to Ogg Skeleton 3

← Older revision		Revision as of 21:01, 23 November 2010
Line 1:		Line 1:
	'''Ogg Skeleton''' provides structuring information for multitrack [[Ogg]] files. It is compatible with Ogg [[Theora]] and provides extra clues for synchronization and content negotiation such as language selection. Skeleton version 4.0 also provides keyframe indexes to enable optimal seeking over high-latency connections, such as the internet.		'''Ogg Skeleton''' provides structuring information for multitrack [[Ogg]] files. It is compatible with Ogg [[Theora]] and provides extra clues for synchronization and content negotiation such as language selection. Skeleton version 4.0 also provides keyframe indexes to enable optimal seeking over high-latency connections, such as the internet. (The previous version was [[Ogg Skeleton 3]].)

	Ogg is a generic container format, enabling interleaving of several tracks of frame-wise encoded content in a time-multiplexed manner. As an example, an Ogg physical bitstream could encapsulate several tracks of video encoded in Theora and multiple tracks of audio encoded in Speex or Vorbis or FLAC at the same time. A player that decodes such a bitstream could then, for example, play one video channel as the main video playback, alpha-blend another one on top of it (e.g. a caption track), play a main Vorbis audio together with several FLAC audio tracks simultaneously (e.g. as sound effects), and provide a choice of Speex channels (e.g. providing commentary in different languages). Such a file is generally possible to create with Ogg, it is however not possible to generically parse such a file, seek on it, understand what codecs are contained in such a file, and dynamically handle and play back such content.		Ogg is a generic container format, enabling interleaving of several tracks of frame-wise encoded content in a time-multiplexed manner. As an example, an Ogg physical bitstream could encapsulate several tracks of video encoded in Theora and multiple tracks of audio encoded in Speex or Vorbis or FLAC at the same time. A player that decodes such a bitstream could then, for example, play one video channel as the main video playback, alpha-blend another one on top of it (e.g. a caption track), play a main Vorbis audio together with several FLAC audio tracks simultaneously (e.g. as sound effects), and provide a choice of Speex channels (e.g. providing commentary in different languages). Such a file is generally possible to create with Ogg, it is however not possible to generically parse such a file, seek on it, understand what codecs are contained in such a file, and dynamically handle and play back such content.

Cpearce: /* Development */

2010-11-23T02:21:40Z

Development

← Older revision		Revision as of 02:21, 23 November 2010
Line 241:		Line 241:
	* Mozilla Firefox 4		* Mozilla Firefox 4

	The following projects currently support Ogg Skeleton 3.1, support for Ogg Skeleton 4 is planned:		The following projects currently support Ogg Skeleton 3, support for Ogg Skeleton 4 is planned:
	* speexenc (with --skeleton) & speexdec		* speexenc (with --skeleton) & speexdec
	* the Ogg Directshow filters: see [http://www.illiminable.com/ogg/ illiminable]		* the Ogg Directshow filters: see [http://www.illiminable.com/ogg/ illiminable]

Cpearce at 02:20, 23 November 2010

2010-11-23T02:20:30Z

← Older revision		Revision as of 02:20, 23 November 2010
Line 11:		Line 11:
	Ogg Skeleton is also designed to allow the creation of substreams from Ogg physical bitstreams that retain the original timing information. For example, when cutting out the segment between the 7th and the 59th second of an Ogg file, it would be nice to continue to start this cut out file with a playback time of 7 seconds and not of 0. This is of particular interest if you're streaming this file from a Web server after a query for a temporal subpart such as in http://example.com/video.ogv?t=7-59 .		Ogg Skeleton is also designed to allow the creation of substreams from Ogg physical bitstreams that retain the original timing information. For example, when cutting out the segment between the 7th and the 59th second of an Ogg file, it would be nice to continue to start this cut out file with a playback time of 7 seconds and not of 0. This is of particular interest if you're streaming this file from a Web server after a query for a temporal subpart such as in http://example.com/video.ogv?t=7-59 .

	== ~~Specification~~ ==		=== Previous version ===

	~~This is a motivation~~ and ~~design sketch.~~		The previous version of Ogg Skeleton was version 3, and its specification can be found on the wiki page [[Ogg Skeleton]], or at [http://svn.annodex.net/standards/draft-pfeiffer-oggskeleton-current.txt http://svn.annodex.net/standards/draft-pfeiffer-oggskeleton-current.txt].
	~~'''For~~ the ~~current specification see~~ http://svn.annodex.net/standards/draft-pfeiffer-oggskeleton-current.txt~~'''~~

	~~'''For the current specification for the keyframe index packets see~~
	http://~~github~~.~~com~~/~~cpearce~~/~~OggIndex/blob/master/Skeleton~~-~~4.0~~-~~Index~~-~~Specification~~.txt~~'''~~

	=== How to describe the logical bitstreams within an Ogg container? ===		=== How to describe the logical bitstreams within an Ogg container? ===