From: Andreas Rheinhardt <andreas.rheinhardt@outlook.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] avformat/mux: Remove check for AVFMT_ALLOW_FLUSH
Date: Mon, 25 Mar 2024 02:55:05 +0100
Message-ID: <GV1P250MB07377FFC7FC3F55980ED7BB88F362@GV1P250MB0737.EURP250.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <GV1P250MB0737C9361C37D0A5D337585B8F302@GV1P250MB0737.EURP250.PROD.OUTLOOK.COM>
Andreas Rheinhardt:
> Due to the bump it is now certain that all devices
> that support flushing have the proper internal flag set.
> (Notice that the check for LIBAVFORMAT_VERSION was wrong.)
>
> Signed-off-by: Andreas Rheinhardt <andreas.rheinhardt@outlook.com>
> ---
> libavformat/mux.c | 6 ------
> 1 file changed, 6 deletions(-)
>
> diff --git a/libavformat/mux.c b/libavformat/mux.c
> index f23eb0188d..630204a8ec 100644
> --- a/libavformat/mux.c
> +++ b/libavformat/mux.c
> @@ -1236,13 +1236,7 @@ int av_write_frame(AVFormatContext *s, AVPacket *in)
> int ret;
>
> if (!in) {
> -#if FF_API_ALLOW_FLUSH || LIBAVFORMAT_VERSION_MAJOR >= 61
> - // Hint: The pulse audio output device has this set,
> - // so we can't switch the check to FF_OFMT_FLAG_ALLOW_FLUSH immediately.
> - if (s->oformat->flags & AVFMT_ALLOW_FLUSH) {
> -#else
> if (ffofmt(s->oformat)->flags_internal & FF_OFMT_FLAG_ALLOW_FLUSH) {
> -#endif
> ret = ffofmt(s->oformat)->write_packet(s, NULL);
> flush_if_needed(s);
> if (ret >= 0 && s->pb && s->pb->error < 0)
Will apply this patchset tomorrow unless there are objections.
- Andreas
_______________________________________________
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:[~2024-03-25 1:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-23 0:09 Andreas Rheinhardt
2024-03-25 1:55 ` Andreas Rheinhardt [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=GV1P250MB07377FFC7FC3F55980ED7BB88F362@GV1P250MB0737.EURP250.PROD.OUTLOOK.COM \
--to=andreas.rheinhardt@outlook.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