1 / 4

draft-hoene-codec-quality-01

draft-hoene-codec-quality-01. IETF #81, Quebec City, Canada hoene@uni-tuebingen.de July 28 th , 2011. Missing Codec Tests (should be done soon). Based on my my previous email (11:22 28.07.2011) Sorted according priority Most important test

della
Télécharger la présentation

draft-hoene-codec-quality-01

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. draft-hoene-codec-quality-01 IETF #81, Quebec City, Canada hoene@uni-tuebingen.de July 28th, 2011

  2. Missing Codec Tests (should be done soon) • Based on my my previous email (11:22 28.07.2011) • Sorted according priority Most important test • two voices at the same time and stereo/binaural voice • Smooth bit rate changes/no artifacts at mode changes • Time stretching and shortening (if this feature is going to be supported) Not important • testing using real packet loss traces • up to 15% loss having acceptable intelligibility • Narrowband: 40 Mhz (2% of a 2 GHz CPU core) • Wideband: 80 Mhz (4% of a 2 GHz CPU core) • SWB/Full: 200 Mhz (10% of a 2 GHz CPU core) • Bit error robustness • Input robustness draft-hoene-codec-quality-01

  3. Codec Characterization(should be done later) Why? • Helps to compare different codec • Gives understanding how to use Opus optimally • Many people would love to see good tests and want to contribute How? • Formally, well-organized, by third parties (no codec developers) When? • Decoupled from codec standardization • Till most tests have been done draft-hoene-codec-quality-01

  4. Some Suggestion on Codec Characterization Action Points • Document shall be edited by some old guys • Objectivity is needed • Editors shall organize formal listening tests • suggest test vectors • avoid some tests are done again and again • Collect and describe formal tests made third party • Including results (Tables) • Change Charter to include Codec Characterization Document draft-hoene-codec-quality-01

More Related