From: Zhao Zhili via ffmpeg-devel <ffmpeg-devel@ffmpeg.org> To: ffmpeg-devel@ffmpeg.org Cc: Zhao Zhili <code@ffmpeg.org> Subject: [FFmpeg-devel] [PATCH] avformat/flvenc: fix event_flags check (PR #20527) Date: Mon, 15 Sep 2025 13:44:00 -0000 Message-ID: <175794384047.25.7979200112370469516@463a07221176> (raw) PR #20527 opened by Zhao Zhili (quink) URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20527 Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20527.patch AVFormatContext.event_flags is checked against AVSTREAM_EVENT_FLAG, which belongs to AVStream.event_flags. There is no real issue since these two flags have the same value. >From 87d1a763956da47482ad5ec3146f4dbd3c6f9219 Mon Sep 17 00:00:00 2001 From: Zhao Zhili <zhilizhao@tencent.com> Date: Mon, 15 Sep 2025 21:39:42 +0800 Subject: [PATCH] avformat/flvenc: fix event_flags check AVFormatContext.event_flags is checked against AVSTREAM_EVENT_FLAG, which belongs to AVStream.event_flags. There is no real issue since these two flags have the same value. --- libavformat/flvenc.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/libavformat/flvenc.c b/libavformat/flvenc.c index 570717320c..a0503c1799 100644 --- a/libavformat/flvenc.c +++ b/libavformat/flvenc.c @@ -1270,9 +1270,9 @@ static int flv_write_packet(AVFormatContext *s, AVPacket *pkt) ts = pkt->dts; - if (s->event_flags & AVSTREAM_EVENT_FLAG_METADATA_UPDATED) { + if (s->event_flags & AVFMT_EVENT_FLAG_METADATA_UPDATED) { write_metadata(s, ts); - s->event_flags &= ~AVSTREAM_EVENT_FLAG_METADATA_UPDATED; + s->event_flags &= ~AVFMT_EVENT_FLAG_METADATA_UPDATED; } avio_write_marker(pb, av_rescale(ts, AV_TIME_BASE, 1000), -- 2.49.1 _______________________________________________ ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org
reply other threads:[~2025-09-15 13:44 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=175794384047.25.7979200112370469516@463a07221176 \ --to=ffmpeg-devel@ffmpeg.org \ --cc=code@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