diff options
| author | Sid Rao <srao@positronnetworks.com> | 2024-03-03 18:31:32 -0500 |
|---|---|---|
| committer | Jean-Marc Valin <jmvalin@jmvalin.ca> | 2024-03-03 18:31:32 -0500 |
| commit | 1bb6d7899721f387255c62b12b2abf64f81a55ce (patch) | |
| tree | b3111f41a05e0bb202ad69c38d8c5ce640643b6f | |
| parent | 0ff629bf9706b016c0622a188ed8710b7a051cab (diff) | |
| download | libopus-1bb6d7899721f387255c62b12b2abf64f81a55ce.tar.gz | |
Update README for 1.5
| -rw-r--r-- | README | 24 |
1 files changed, 23 insertions, 1 deletions
@@ -22,7 +22,7 @@ This package implements a shared library for encoding and decoding raw Opus bitstreams. Raw Opus bitstreams should be used over RTP according to https://tools.ietf.org/html/rfc7587 -The package also includes a number of test tools used for testing the +The package also includes a number of test tools used for testing the correct operation of the library. The bitstreams read/written by these tools should not be used for Opus file distribution: They include additional debugging data and cannot support seeking. @@ -39,6 +39,28 @@ Opus-tools can be found at: or on the main Opus website: https://opus-codec.org/ +== Deep Learning and Opus == + +Lossy networks continue to be a challenge for real-time communications. +While the original implementation of Opus provides an excellent packet loss +concealment mechanism, the team has continued to advance the methodology used +to improve audio quality in challenge network environments. + +In Opus 1.5, we added a deep learning based redundancy encoder that enhances +audio in lossy networks by embedding one second of recovery data in the padding +data of each packet. The underlying algorithm behind encoding and decoding the +recovery data is called the deep redundancy (DRED) algorithm. By leveraging +the padding data within the packet, Opus 1.5 is fully backward compatible with +prior revisions of Opus. Please see the README under the "dnn" subdirectory to +understand DRED. + +DRED was developed by a team that Amazon Web Services initially sponsored, +who open-sourced the implementation as well as began the +standardization process at the IETF: + https://datatracker.ietf.org/doc/draft-ietf-mlcodec-opus-extension/ +The license behind Opus or the intellectual property position of Opus does +not change with Opus 1.5. + == Compiling libopus == To build from a distribution tarball, you only need to do the following: |