@@ -22,7 +22,7 @@ This package implements a shared library for encoding and decoding raw Opus
22
22
bitstreams. Raw Opus bitstreams should be used over RTP according to
23
23
https://tools.ietf.org/html/rfc7587
24
24
25
- The package also includes a number of test tools used for testing the
25
+ The package also includes a number of test tools used for testing the
26
26
correct operation of the library. The bitstreams read/written by these
27
27
tools should not be used for Opus file distribution: They include
28
28
additional debugging data and cannot support seeking.
@@ -39,6 +39,28 @@ Opus-tools can be found at:
39
39
or on the main Opus website:
40
40
https://opus-codec.org/
41
41
42
+ == Deep Learning and Opus ==
43
+
44
+ Lossy networks continue to be a challenge for real-time communications.
45
+ While the original implementation of Opus provides an excellent packet loss
46
+ concealment mechanism, the team has continued to advance the methodology used
47
+ to improve audio quality in challenge network environments.
48
+
49
+ In Opus 1.5, we added a deep learning based redundancy encoder that enhances
50
+ audio in lossy networks by embedding one second of recovery data in the padding
51
+ data of each packet. The underlying algorithm behind encoding and decoding the
52
+ recovery data is called the deep redundancy (DRED) algorithm. By leveraging
53
+ the padding data within the packet, Opus 1.5 is fully backward compatible with
54
+ prior revisions of Opus. Please see the README under the "dnn" subdirectory to
55
+ understand DRED.
56
+
57
+ DRED was developed by a team that Amazon Web Services initially sponsored,
58
+ who open-sourced the implementation as well as began the
59
+ standardization process at the IETF:
60
+ https://datatracker.ietf.org/doc/draft-ietf-mlcodec-opus-extension/
61
+ The license behind Opus or the intellectual property position of Opus does
62
+ not change with Opus 1.5.
63
+
42
64
== Compiling libopus ==
43
65
44
66
To build from a distribution tarball, you only need to do the following:
0 commit comments