<div dir="ltr">Hi Mark,<div><br></div><div>Well, so do you think that any of this libraries probably won't provide correct audio conversion? Do you know any other possible solutions for described problems, ommiting trying to fix on my own any of this libraries or waiting for fix? Will you mind if I quote you in disscussion I mentioned? Sorry for asking you so many questions at once.</div><div><br></div><div><br></div><div>Regards,</div><div><br></div><div>Mateusz</div></div><div class="gmail_extra"><br><div class="gmail_quote">2015-07-08 17:42 GMT+02:00 Mark Harris <span dir="ltr"><<a href="mailto:mark.hsj@gmail.com" target="_blank">mark.hsj@gmail.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Mateusz,<br>
<br>
The Ogg Opus container does not have explicit per-packet timestamps,<br>
and so doesn't allow gaps in the audio. PLC packets may be generated<br>
to replace any packets that were lost or corrupted, as described in<br>
section 4.1 of the specification:<br>
<a href="https://tools.ietf.org/html/draft-ietf-codec-oggopus-08#section-4.1" rel="noreferrer" target="_blank">https://tools.ietf.org/html/draft-ietf-codec-oggopus-08#section-4.1</a><br>
These packets usually consist of just a single TOC byte. It looks<br>
like the tool you are using does not do this, and does not replace<br>
gaps with anything. Unfortunately FFmpeg has a similar issue:<br>
<a href="https://trac.ffmpeg.org/ticket/3391" rel="noreferrer" target="_blank">https://trac.ffmpeg.org/ticket/3391</a><br>
<span class="HOEnZb"><font color="#888888"><br>
- Mark<br>
</font></span></blockquote></div><br></div>