Difference between revisions of "Plenary87"

From IAB Wiki
Jump to navigation Jump to search
(Created page with "<pre> The OPUS codec, defined in RFC 6716, can scale from low bit-rate narrowband speech to very high quality stereo music, making it suitable for a wide range of...")
 
 
Line 1: Line 1:
<pre>
== IETF 87 Technical Plenary: OPUS Codec ==
    The OPUS codec, defined in RFC 6716, can scale from low bit-rate
 
    narrowband speech to very high quality stereo music, making it
The OPUS codec, defined in RFC 6716, can scale from low bit-rate
    suitable for a wide range of audio applications.  This session
narrowband speech to very high quality stereo music, making it
    covers the past and future of Opus as well as the lessons
suitable for a wide range of audio applications.  This session
    learned that could apply to future IETF work.   
covers the past and future of Opus as well as the lessons
learned from the standardization process that could apply  
to future IETF work.
   
Agenda:


     a. Introduction
     a. Introduction
     b. Overview of Opus
     b. Overview of Opus (JM Valin)
     c. Testing
     c. Testing (Greg Maxwell)
     d. History of Opus in the IETF
     d. History of Opus in the IETF (Peter St. Andre)
     e. Opus Deployment Panel
      1. History
    f. Future Work
      2. Lessons learned
</pre>
     e. Future Work (JM Valin & Tim Terriberry)
    f. Opus Deployment Panel (Tim Terriberry, Emil Ivov, Lorenzo Miniero, Justin Uberti)
 
== Remote Participation Experiment ==
 
During the IETF 87 Technical Plenary, the MeetEcho team will be running an experiment to enable remote
participation in the meeting using the OPUS codec.  Remote participants can access the session using a
WebRTC-compatible browser pointed at this location:
http://www.meetecho.com/ietf87/tech_plenary
 
In addition, recordings of this and other sessions at IETF 87 will be made available at the following location:
http://ietf87.conf.meetecho.com/index.php/Recorded_Sessions
 
== References ==
 
More Information on OPUS
* http://www.opus-codec.org/
* http://www.youtube.com/watch?feature=player_embedded&v=iaAD71h9gDU
* http://tools.ietf.org/html/draft-ietf-payload-rtp-opus
 
Test data
* http://tools.ietf.org/html/draft-ietf-codec-results-03
* http://trac.tools.ietf.org/wg/codec/trac/wiki/TestingResults
* http://www.opus-codec.org/comparison/
* http://research.nokia.com/files/public/%5B16%5D_InterSpeech2011_Voice_Quality_Characterization_of_IETF_Opus_Codec.pdf
 
Blogs
* http://jmspeex.livejournal.com/
* http://blogs.skype.com/2012/09/12/skype-and-a-new-audio-codec/
* http://blogs.computerworlduk.com/open-enterprise/2012/09/what-a-wonderful-piece-of-work-is-opus/index.htm
 
Licensing
* Licensing terms: http://www.opus-codec.org/license/
* IETF IPR Disclosures: https://datatracker.ietf.org/ipr/search/?option=rfc_search&rfc_search=6716
* Comments on other disclosures: http://www.opus-codec.org/license/#other
* Digium's Position:  http://www.ietf.org/mail-archive/web/codec/current/msg03017.html (clarifying original email in http://lists.digium.com/pipermail/asterisk-dev/2013-May/060419.html )

Latest revision as of 18:59, 21 September 2022

IETF 87 Technical Plenary: OPUS Codec

The OPUS codec, defined in RFC 6716, can scale from low bit-rate narrowband speech to very high quality stereo music, making it suitable for a wide range of audio applications. This session covers the past and future of Opus as well as the lessons learned from the standardization process that could apply to future IETF work.

Agenda:

   a. Introduction
   b. Overview of Opus (JM Valin)
   c. Testing (Greg Maxwell)
   d. History of Opus in the IETF (Peter St. Andre)
      1. History
      2. Lessons learned
   e. Future Work (JM Valin & Tim Terriberry)
   f. Opus Deployment Panel (Tim Terriberry, Emil Ivov, Lorenzo Miniero, Justin Uberti)

Remote Participation Experiment

During the IETF 87 Technical Plenary, the MeetEcho team will be running an experiment to enable remote participation in the meeting using the OPUS codec. Remote participants can access the session using a WebRTC-compatible browser pointed at this location: http://www.meetecho.com/ietf87/tech_plenary

In addition, recordings of this and other sessions at IETF 87 will be made available at the following location: http://ietf87.conf.meetecho.com/index.php/Recorded_Sessions

References

More Information on OPUS

Test data

Blogs

Licensing