<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta name=Generator content="Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.E-MailFormatvorlage17
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.E-MailFormatvorlage18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=DE link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='color:#1F497D'>Hello Milan Young,<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'>thanks for doing the ASR testing.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'>We would be happy to consider your results to be in included in the Opus characterization draft.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'>Please feel free to post them to the Opus IETF mailing list, too.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'>With best regards,<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'> Christian Hoene<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'><o:p> </o:p></span></p><div><p class=MsoNormal><span style='font-family:"Courier New";color:#1F497D'>--<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Courier New";color:#1F497D'>Universität Tübingen, Sand 13, 72076 Tübingen, Germany<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Courier New";color:#1F497D'>Tel +49 7071 2970532, Fax +49 7071 5220<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Courier New";color:#1F497D'><a href="http://kn.inf.uni-tuebingen.de/staff/hoene.html">http://kn.inf.uni-tuebingen.de/staff/hoene.html</a><o:p></o:p></span></p></div><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>Von:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> opus-bounces@xiph.org [mailto:opus-bounces@xiph.org] <b>Im Auftrag von </b>Young, Milan<br><b>Gesendet:</b> Mittwoch, 28. November 2012 12:51<br><b>An:</b> opus@xiph.org<br><b>Betreff:</b> [opus] Opus for ASR - update and questions<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span lang=EN-US>For the last couple months, Nuance has performed extensive testing on how the Opus codec performs in the speech recognition task. I’m hoping to publish a full report in the coming months, but until then all I have is a teaser. Opus performed within about 1% of the WER (Word Error Rate) of unencoded audio. This is compared to about 5% for Speex, which was the previous codec of choice. Well done to you all!<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US>As Nuance considers migrating to Opus, we’d like to consider the topic of transport. Traditionally we’ve relied on TCP for reasons of reliability. Opus, with its packet redundancy features, offers an attractive real-time alternative that we will soon be testing. But in order to apply an apples-apples comparison we need to model both data rates and latency in real world scenarios.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US>For UDP, I’m assuming that the redundancy feature adds no additional latency. Correct? On the data rate question, I see that the Opusenc tool provides an “expec-loss” parameter with the value expressed as a percentage. Could someone please describe how this is implemented? Are you simply removing some percentage of packets from the result, or is there a more complex model underpinning the exercise?<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US>Modeling TCP data rates and latency in similarly losssy scenarios seems much more difficult since dropped packets have cascading effects. Has anyone on this list considered this class of comparison? Any suggestions for modeling software that could aid my search?<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US>Thank you<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p></div></body></html>