From: Gyan Doshi <ffmpeg@gyani.pro>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] swr/swresample: avoid reapplication of firstpts
Date: Fri, 15 Dec 2023 12:32:35 +0530
Message-ID: <5c2b818f-e693-4580-b529-212ee75b750d@gyani.pro> (raw)
In-Reply-To: <20231214191340.GK6420@pb2>
On 2023-12-15 12:43 am, Michael Niedermayer wrote:
> On Tue, Dec 12, 2023 at 04:50:08PM +0530, Gyan Doshi wrote:
>> During a resampling operation where
>>
>> 1) user has specified first_pts
>> 2) SWR_FLAG_RESAMPLE is not set initially (directly or otherwise)
>> 3) first_pts has been fulfilled (always using hard compensation)
>>
>> then upon first encountering a delay where a soft compensation is
>> required, swr_set_compensation will lead to another init of swr which
>> will reset outpts to the specified firstpts thus leading to an output
>> frame having its pts = firstpts. When the next input frame is received,
>> swr will see a large delay and inject silence from firstpts to the
>> current frame's pts. This can lead to severe desync and in worst case,
>> loss of audio playback.
>>
>> Parameter initcount added to keep track of swr_init calls of the swrcontext
>> and to ultimately avoid enforcing firstpts again.
>>
>> Fixes #4131.
>> ---
>> libswresample/swresample.c | 7 +++++--
>> libswresample/swresample_internal.h | 1 +
>> libswresample/version.h | 2 +-
>> 3 files changed, 7 insertions(+), 3 deletions(-)
> Would it work to instead set firstpts = AV_NOPTS_VALUE on allocation
> and then use firstpts == AV_NOPTS_VALUE to detect if it has been set
> already ?
> If that workes, that seems simpler than counting init
That does work. I avoided it since I didn't know if I needed to make
swr_alloc2() or change in place.
v2 sent.
Regards,
Gyan
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
prev parent reply other threads:[~2023-12-15 7:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-12 11:20 Gyan Doshi
2023-12-14 19:13 ` Michael Niedermayer
2023-12-15 7:02 ` Gyan Doshi [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5c2b818f-e693-4580-b529-212ee75b750d@gyani.pro \
--to=ffmpeg@gyani.pro \
--cc=ffmpeg-devel@ffmpeg.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
This inbox may be cloned and mirrored by anyone:
git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
ffmpegdev@gitmailbox.com
public-inbox-index ffmpegdev
Example config snippet for mirrors.
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git