<div dir="ltr">You might want to consider using parts of the WebRTC library, instead of using Opus directly. In addition to Opus packetization, WebRTC also includes a component called "NetEQ" that corrects for clock drift by stretching the decoded audio, without using PLC.</div>
<div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, May 29, 2014 at 7:13 AM, Abhijit Patait <span dir="ltr"><<a href="mailto:apatait@nvidia.com" target="_blank">apatait@nvidia.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div lang="EN-US" link="blue" vlink="purple"><div><p class="MsoNormal">I have a question about PLC used by OPUS.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">We are using OPUS for streaming music in some application.<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">Due to some network problems, we are running into problems related to clock drifts. This causes jitter buffer underflows at the receiver and hence we need to rebuffer the jitter buffer periodically. We are looking at the root cause of this problem (drift), but that’s besides the point.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">During jitter buffer rebuffering, we are sending null frames to the OPUS decode, indicating lost frames. My question is – Is this the most effective way of handling this situation?<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">Or is it a better to detect such imminent underflow by some means and then insert “lost” frames in the middle sporadically to avoid the complete jitter buffer underflow?<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">Thanks for your help,<u></u><u></u></p><p class="MsoNormal">Abhijit<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p></div>
<div>
<hr>
</div>
<div>This email message is for the sole use of the intended recipient(s) and may
contain confidential information. Any unauthorized review, use, disclosure
or distribution is prohibited. If you are not the intended recipient,
please contact the sender by reply email and destroy all copies of the original
message. </div>
<div>
<hr>
</div>
</div>
<br>_______________________________________________<br>
opus mailing list<br>
<a href="mailto:opus@xiph.org">opus@xiph.org</a><br>
<a href="http://lists.xiph.org/mailman/listinfo/opus" target="_blank">http://lists.xiph.org/mailman/listinfo/opus</a><br>
<br></blockquote></div><br></div>