aboutsummaryrefslogtreecommitdiff
path: root/doc/libogg/ogg_page.html
diff options
context:
space:
mode:
Diffstat (limited to 'doc/libogg/ogg_page.html')
-rw-r--r--doc/libogg/ogg_page.html11
1 files changed, 6 insertions, 5 deletions
diff --git a/doc/libogg/ogg_page.html b/doc/libogg/ogg_page.html
index e7867c6..0151a21 100644
--- a/doc/libogg/ogg_page.html
+++ b/doc/libogg/ogg_page.html
@@ -9,7 +9,7 @@
<table border=0 width=100%>
<tr>
<td><p class=tiny>libogg documentation</p></td>
-<td align=right><p class=tiny>libogg release 1.2.0 - 20100325</p></td>
+<td align=right><p class=tiny>libogg release 1.3.5 - 20210603</p></td>
</tr>
</table>
@@ -24,8 +24,9 @@ Ogg pages are the fundamental unit of framing and interleave in an ogg bitstream
They are made up of packet segments of 255 bytes each. There can be as many as
255 packet segments per page, for a maximum page size of a little under 64 kB.
This is not a practical limitation as the segments can be joined across
-page boundaries allowing packets of arbitrary size. In practice pages are
-usually around 4 kB.
+page boundaries allowing packets of arbitrary size. In practice many
+applications will not completely fill all pages because they flush the
+accumulated packets periodically order to bound latency more tightly.
<p>
<p>For a complete description of ogg pages and headers, please refer to the <a href="../framing.html">framing document</a>.
@@ -61,11 +62,11 @@ typedef struct {
<hr noshade>
<table border=0 width=100%>
<tr valign=top>
-<td><p class=tiny>copyright &copy; 2000-2010 Xiph.Org</p></td>
+<td><p class=tiny>copyright &copy; 2000-2021 Xiph.Org Foundation</p></td>
<td align=right><p class=tiny><a href="http://www.xiph.org/ogg/">Ogg Container Format</a></p></td>
</tr><tr>
<td><p class=tiny>libogg documentation</p></td>
-<td align=right><p class=tiny>libogg release 1.2.0 - 20100325</p></td>
+<td align=right><p class=tiny>libogg release 1.3.5 - 20210603</p></td>
</tr>
</table>