On Thu, Feb 18, 2021 at 11:39 AM Philip-Dylan Gleonec
wrote:
>
> Here is the reworked patch properly attached.
> Sorry about the duplicate mail, I just noticed I had a mishap with my
> mail client and the previous patch was scrubbed.
>
> Signed-off-by: Philip-Dylan Gleonec
>
> Co-developed-by: S
On Thu, Feb 18, 2021 at 11:39 AM Philip-Dylan Gleonec
wrote:
>
> Here is the reworked patch properly attached.
> Sorry about the duplicate mail, I just noticed I had a mishap with my
> mail client and the previous patch was scrubbed.
>
> Signed-off-by: Philip-Dylan Gleonec
>
> Co-developed-by: S
Mar 3, 2021, 16:51 by philip-dylan.gleo...@savoirfairelinux.com:
> Le 18/02/2021 à 17:38, Philip-Dylan Gleonec a écrit :
>
>> Here is the reworked patch properly attached.
>> Sorry about the duplicate mail, I just noticed I had a mishap with my
>> mail client and the previous patch was scrubbed.
>
Le 18/02/2021 à 17:38, Philip-Dylan Gleonec a écrit :
Here is the reworked patch properly attached.
Sorry about the duplicate mail, I just noticed I had a mishap with my
mail client and the previous patch was scrubbed.
Hello,
Is someone interested in picking this up, or is there some further
Here is the reworked patch properly attached.
Sorry about the duplicate mail, I just noticed I had a mishap with my
mail client and the previous patch was scrubbed.
Signed-off-by: Philip-Dylan Gleonec
Co-developed-by: Steinar H. Gunderson
---
libavcodec/libopusdec.c | 107 ++
Andreas Rheinhardt:
>>> Could you elaborate?
>>> I would have expected that the normal use case is not have a
>>> lossy input and that the new feature is always useful if data
>>> was lost.
>>
>> The use-case for FEC is typically RTP stream where audio is compressed
>> with opus. In that case, de
Philip-Dylan Gleonec:
>> Could you elaborate?
>> I would have expected that the normal use case is not have a
>> lossy input and that the new feature is always useful if data
>> was lost.
>
> The use-case for FEC is typically RTP stream where audio is compressed
> with opus. In that case, dependin
> I've added him to the CC list
Now done.
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
>> Am Di., 16. Feb. 2021 um 15:02 Uhr schrieb Philip-Dylan Gleonec
>> :
>>
>>>
>>> Adds FEC/PLC support to libopus. The lost packets are detected as a
>>> discontinuity in the audio stream. When a discontinuity is used, this
>>> patch tries to decode the FEC data. If FEC data is present in the
>>>
> Could you elaborate?
> I would have expected that the normal use case is not have a
> lossy input and that the new feature is always useful if data
> was lost.
The use-case for FEC is typically RTP stream where audio is compressed
with opus. In that case, depending on the network conditions, pac
Feb 16, 2021, 20:07 by ceffm...@gmail.com:
> Am Di., 16. Feb. 2021 um 15:02 Uhr schrieb Philip-Dylan Gleonec
> :
>
>>
>> Adds FEC/PLC support to libopus. The lost packets are detected as a
>> discontinuity in the audio stream. When a discontinuity is used, this
>> patch tries to decode the FEC dat
Am Di., 16. Feb. 2021 um 15:02 Uhr schrieb Philip-Dylan Gleonec
:
>
> Adds FEC/PLC support to libopus. The lost packets are detected as a
> discontinuity in the audio stream. When a discontinuity is used, this
> patch tries to decode the FEC data. If FEC data is present in the
> packet, it is decod
12 matches
Mail list logo
