ref: 5b712da9c2faa51ebf3336161138b2d2fa54a47d
parent: 7424bb0a247c0692327001addb036f6e2313e970
author: Ralph Giles <giles@mozilla.com>
date: Sat Dec 20 07:37:48 EST 2014
Document the motivation for the 120 ms repacketizer limit. See the mailing list discussion at http://lists.xiph.org/pipermail/opus/2014-December/002802.html
--- a/include/opus.h
+++ b/include/opus.h
@@ -616,7 +616,10 @@
* merged. Splitting valid Opus packets is always guaranteed to succeed,
* whereas merging valid packets only succeeds if all frames have the same
* mode, bandwidth, and frame size, and when the total duration of the merged
- * packet is no more than 120 ms.
+ * packet is no more than 120 ms. The 120 ms limit comes from the
+ * specification and limits decoder memory requirements at a point where
+ * framing overhead becomes negligible.
+ *
* The repacketizer currently only operates on elementary Opus
* streams. It will not manipualte multistream packets successfully, except in
* the degenerate case where they consist of data from a single stream.