From 05aab66755e7f16d93836b29c8d37d3588eca6a0 Mon Sep 17 00:00:00 2001 From: Monty Date: Thu, 25 Mar 2010 20:28:17 +0000 Subject: Update CHANGES file Correct one last misleading caption in the stream documentation, pending the more complete examples rewrite langing post 1.2.0 git-svn-id: http://svn.xiph.org/trunk/ogg@17033 0101bb08-14d6-0310-b084-bc0e0c8e3800 --- doc/oggstream.html | 23 ++++++++++------------- 1 file changed, 10 insertions(+), 13 deletions(-) (limited to 'doc') diff --git a/doc/oggstream.html b/doc/oggstream.html index 29ecd82..485747d 100644 --- a/doc/oggstream.html +++ b/doc/oggstream.html @@ -462,7 +462,7 @@ preceding segment have terminated.

[More to come shortly; this section is currently being revised and expanded] -

Below, we present an example of a grouped and chained bitstream:

+

Below, we present an example of a multiplexed and chained bitstream:

stream

@@ -471,18 +471,15 @@ multiplexed into a physical bitstream. Note the following characteristics:

    -
  1. Grouped bitstreams begin together; all of the initial pages -must appear before any data pages. When concurrently multiplexed -groups are chained, the new group does not begin until all the -bitstreams in the previous group have terminated.
    2. - -
  2. The pages of concurrently multiplexed bitstreams need not conform -to a regular order; the only requirement is that page n of a -logical bitstream follow page n-1 in the physical bitstream. -There are no restrictions on intervening pages belonging to other -logical bitstreams. (Tying page appearance to bitrate demands is one -logical strategy, ie, the page appears at the chronological point -where decode requires more information).
    3. +
  3. Multiplexed bitstreams in a given link begin together; all of the +initial pages must appear before any data pages. When concurrently +multiplexed groups are chained, the new group does not begin until all +the bitstreams in the previous group have terminated.
    4. + +
  4. The ordering of pages of concurrently multiplexed bitstreams is +goverened by timestamp (not shown here); there is no regular +interleaving order. Pages within a logical bitstream appear in +sequence order.