From: mux47 via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: ffmpeg-devel@ffmpeg.org
Cc: mux47 <code@ffmpeg.org>
Subject: [FFmpeg-devel] [PATCH] Update libavcodec/opus/parser.c (PR #20959)
Date: Tue, 18 Nov 2025 16:45:00 -0000
Message-ID: <176348430109.25.13208355536444027300@2cb04c0e5124> (raw)
PR #20959 opened by mux47
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20959
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20959.patch
Avoid calling ff_opus_parse_packet() on flush (buf_size == 0)
Fixes spurious 'Error parsing Opus packet header' in complete-frames mode at EOF.
Related: FFmpeg/FFmpeg#20954
>From 635ccf83f312279157daed2ca1a79550ff51f3b1 Mon Sep 17 00:00:00 2001
From: mux47 <mux100@protonmail.com>
Date: Tue, 18 Nov 2025 16:43:49 +0000
Subject: [PATCH] Update libavcodec/opus/parser.c
Avoid calling ff_opus_parse_packet() on flush (buf_size == 0)
Fixes spurious 'Error parsing Opus packet header' in complete-frames mode at EOF.
Related: FFmpeg/FFmpeg#20954
---
libavcodec/opus/parser.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/libavcodec/opus/parser.c b/libavcodec/opus/parser.c
index ae3d66592c..bab0e50412 100644
--- a/libavcodec/opus/parser.c
+++ b/libavcodec/opus/parser.c
@@ -189,7 +189,7 @@ static int opus_parse(AVCodecParserContext *ctx, AVCodecContext *avctx,
if (ctx->flags & PARSER_FLAG_COMPLETE_FRAMES) {
next = buf_size;
- if (set_frame_duration(ctx, avctx, buf, buf_size) < 0)
+ if (buf_size && set_frame_duration(ctx, avctx, buf, buf_size) < 0)
goto fail;
} else {
next = opus_find_frame_end(ctx, avctx, buf, buf_size, &header_len);
--
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-11-18 16:45 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=176348430109.25.13208355536444027300@2cb04c0e5124 \
--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