From: rmmh via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: ffmpeg-devel@ffmpeg.org
Cc: rmmh <code@ffmpeg.org>
Subject: [FFmpeg-devel] [PATCH] avcodec/alac: fix decode errors on empty last frames (PR #21111)
Date: Fri, 05 Dec 2025 16:24:02 -0000
Message-ID: <176495184264.39.5596703958079514528@2cb04c0e5124> (raw)
PR #21111 opened by rmmh
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/21111
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/21111.patch
iOS Voice Memos frequently produces ALAC files with a zero-sample last
frame. Instead of bubbling up an error that might cause a transcode to
fail, simply don't decode the frame.
>From f2a31efae7c42aa8bac2a4747df0fcad40a62868 Mon Sep 17 00:00:00 2001
From: Ryan Hitchman <hitchmanr@gmail.com>
Date: Fri, 5 Dec 2025 09:20:29 -0700
Subject: [PATCH] avcodec/alac: fix decode errors on empty last frames
iOS Voice Memos frequently produces ALAC files with a zero-sample last
frame. Instead of bubbling up an error that might cause a transcode to
fail, simply don't decode the frame.
---
libavcodec/alac.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/libavcodec/alac.c b/libavcodec/alac.c
index f91288e97c..0acc568174 100644
--- a/libavcodec/alac.c
+++ b/libavcodec/alac.c
@@ -267,7 +267,9 @@ static int decode_element(AVCodecContext *avctx, AVFrame *frame, int ch_index,
output_samples = get_bits_long(gb, 32);
else
output_samples = alac->max_samples_per_frame;
- if (!output_samples || output_samples > alac->max_samples_per_frame) {
+ if (!output_samples)
+ return 0;
+ if (output_samples > alac->max_samples_per_frame) {
av_log(avctx, AV_LOG_ERROR, "invalid samples per frame: %"PRIu32"\n",
output_samples);
return AVERROR_INVALIDDATA;
--
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-12-05 16:24 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=176495184264.39.5596703958079514528@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