Opus
The Opus audio codec
Within this page
Opus RFCs (7)
RFC 8486: Ambisonics in an Ogg Opus Container
Proposed Standard- J. Skoglund
- M. Graczyk
- October 2018
- IETF publication
- Applications and Real-Time Area
Abstract
This document defines an extension to the Opus audio codec to encapsulate coded Ambisonics using the Ogg format. It also contains updates to RFC 7845 to reflect necessary changes in the description of channel mapping families.
Abstract
This document defines an extension to the Opus audio codec to encapsulate coded Ambisonics using the Ogg format. It also contains updates to RFC 7845 to reflect necessary changes in the description of channel mapping families.
RFC 8251: Updates to the Opus Audio Codec
Proposed Standard- JM. Valin
- K. Vos
- October 2017
- IETF publication
- Applications and Real-Time Area
Abstract
This document addresses minor issues that were found in the specification of the Opus audio codec in RFC 6716. It updates the normative decoder implementation included in Appendix A of RFC 6716. The changes fix real and potential security-related issues, as well as minor quality-related issues.
Abstract
This document addresses minor issues that were found in the specification of the Opus audio codec in RFC 6716. It updates the normative decoder implementation included in Appendix A of RFC 6716. The changes fix real and potential security-related issues, as well as minor quality-related issues.
RFC 7845: Ogg Encapsulation for the Opus Audio Codec
Proposed Standard- T. Terriberry
- R. Lee
- R. Giles
- April 2016
- IETF publication
- Applications and Real-Time Area
Abstract
This document defines the Ogg encapsulation for the Opus interactive speech and audio codec. This allows data encoded in the Opus format to be stored in an Ogg logical bitstream.
Abstract
This document defines the Ogg encapsulation for the Opus interactive speech and audio codec. This allows data encoded in the Opus format to be stored in an Ogg logical bitstream.
RFC 7587: RTP Payload Format for the Opus Speech and Audio Codec
Proposed Standard- J. Spittka
- K. Vos
- JM. Valin
- June 2015
- IETF publication
- Applications and Real-Time Area
Abstract
This document defines the Real-time Transport Protocol (RTP) payload format for packetization of Opus-encoded speech and audio data necessary to integrate the codec in the most compatible way. It also provides an applicability statement for the use of Opus over RTP. Further, it describes media type registrations for the RTP payload format.
Abstract
This document defines the Real-time Transport Protocol (RTP) payload format for packetization of Opus-encoded speech and audio data necessary to integrate the codec in the most compatible way. It also provides an applicability statement for the use of Opus over RTP. Further, it describes media type registrations for the RTP payload format.
RFC 6716: Definition of the Opus Audio Codec
Proposed Standard- JM. Valin
- K. Vos
- T. Terriberry
- September 2012
- IETF publication
- Applications and Real-Time Area
Abstract
This document defines the Opus interactive speech and audio codec. Opus is designed to handle a wide range of interactive audio applications, including Voice over IP, videoconferencing, in-game chat, and even live, distributed music performances. It scales from low bitrate narrowband speech at 6 kbit/s to very high quality stereo music at 510 kbit/s. Opus uses both Linear Prediction (LP) and the Modified Discrete Cosine Transform (MDCT) to achieve good compression of both speech and music. [STANDARDS-TRACK]
Abstract
This document defines the Opus interactive speech and audio codec. Opus is designed to handle a wide range of interactive audio applications, including Voice over IP, videoconferencing, in-game chat, and even live, distributed music performances. It scales from low bitrate narrowband speech at 6 kbit/s to very high quality stereo music at 510 kbit/s. Opus uses both Linear Prediction (LP) and the Modified Discrete Cosine Transform (MDCT) to achieve good compression of both speech and music. [STANDARDS-TRACK]
RFC 6569: Guidelines for Development of an Audio Codec within the IETF
Informational- JM. Valin
- S. Borilin
- K. Vos
- C. Montgomery
- R. Chen
- March 2012
- IETF publication
- Applications and Real-Time Area
Abstract
This document provides general guidelines for work on developing and specifying an interactive audio codec within the IETF. These guidelines cover the development process, evaluation, requirements conformance, and intellectual property issues. This document is not an Internet Standards Track specification; it is published for informational purposes.
Abstract
This document provides general guidelines for work on developing and specifying an interactive audio codec within the IETF. These guidelines cover the development process, evaluation, requirements conformance, and intellectual property issues. This document is not an Internet Standards Track specification; it is published for informational purposes.
RFC 6366: Requirements for an Internet Audio Codec
Informational- J. Valin
- K. Vos
- August 2011
- IETF publication
- Applications and Real-Time Area
Abstract
This document provides specific requirements for an Internet audio codec. These requirements address quality, sampling rate, bit-rate, and packet-loss robustness, as well as other desirable properties. This document is not an Internet Standards Track specification; it is published for informational purposes.
Abstract
This document provides specific requirements for an Internet audio codec. These requirements address quality, sampling rate, bit-rate, and packet-loss robustness, as well as other desirable properties. This document is not an Internet Standards Track specification; it is published for informational purposes.
Subscribe to Opus
Get notified when:
- RFC changes to status, obsoleted by, updates, updated by, or subseries.
- New RFC added to this subject or below
- The subject was merged into another.