From: James Almer <jamrial@gmail.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH 1/4 v2] ffmpeg: flush delayed frames in codec copy scenarios
Date: Mon, 28 Feb 2022 09:30:19 -0300
Message-ID: <44f979b7-1148-8414-0df7-3228c9b87a29@gmail.com> (raw)
In-Reply-To: <20220223150355.944-1-jamrial@gmail.com>
On 2/23/2022 12:03 PM, James Almer wrote:
> Bitstream filters inserted between the input and output were
> never drained, resulting packets being lost if the bsf had any
> buffered.
>
> Signed-off-by: James Almer <jamrial@gmail.com>
> ---
> Now also flushing packets when forcing a record duration.
>
> fftools/ffmpeg.c | 13 ++++++++-----
> fftools/ffmpeg.h | 1 +
> fftools/ffmpeg_filter.c | 1 +
> fftools/ffmpeg_opt.c | 4 ++++
> 4 files changed, 14 insertions(+), 5 deletions(-)
Will apply.
_______________________________________________
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:[~2022-02-28 12:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-23 15:03 James Almer
2022-02-23 15:03 ` [FFmpeg-devel] [PATCH 2/4 v2] ffmpeg: ensure a keyframe was not seen before skipping packets James Almer
2022-03-31 11:47 ` Anton Khirnov
2022-03-31 11:51 ` James Almer
2022-02-23 15:03 ` [FFmpeg-devel] [PATCH 3/4] avcodec/setts_bsf: add NEXT_PTS/DTS expression constants James Almer
2022-02-23 15:03 ` [FFmpeg-devel] [PATCH 4/4 v2] avcodec/setts_bsf: add constants to modify packet duration James Almer
2022-02-28 12:30 ` James Almer [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=44f979b7-1148-8414-0df7-3228c9b87a29@gmail.com \
--to=jamrial@gmail.com \
--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