From: ngaullier via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: ffmpeg-devel@ffmpeg.org
Cc: ngaullier <code@ffmpeg.org>
Subject: [FFmpeg-devel] [PATCH] avformat/isom_tags: fix fourcc for in24/in32 LE (PR #21110)
Date: Fri, 05 Dec 2025 16:09:25 -0000
Message-ID: <176495096647.39.9450858938903143903@2cb04c0e5124> (raw)
PR #21110 opened by ngaullier
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/21110
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/21110.patch
This fixes a sample I get recently (a supposed 'iso' mp4 file with 42ni tracks; I think its format is invalid/quicktime-based, but anyway should be supported).
(Note: VLC already supports 42ni/23ni: see fourcc_list.h and plays my sample successfully.)
>From 2f08cf6093c455c520e4725a9ec1ad43b7cdc4a9 Mon Sep 17 00:00:00 2001
From: Nicolas Gaullier <nicolas.gaullier@cji.paris>
Date: Fri, 5 Dec 2025 16:44:03 +0100
Subject: [PATCH] avformat/isom_tags: fix fourcc for in24/in32 LE
Signed-off-by: Nicolas Gaullier <nicolas.gaullier@cji.paris>
---
libavformat/isom_tags.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/libavformat/isom_tags.c b/libavformat/isom_tags.c
index 151c42e9e6..b46e293ebf 100644
--- a/libavformat/isom_tags.c
+++ b/libavformat/isom_tags.c
@@ -347,9 +347,9 @@ const AVCodecTag ff_codec_movaudio_tags[] = {
{ AV_CODEC_ID_PCM_S16BE, MKTAG('l', 'p', 'c', 'm') },
{ AV_CODEC_ID_PCM_S16LE, MKTAG('l', 'p', 'c', 'm') },
{ AV_CODEC_ID_PCM_S24BE, MKTAG('i', 'n', '2', '4') },
- { AV_CODEC_ID_PCM_S24LE, MKTAG('i', 'n', '2', '4') },
+ { AV_CODEC_ID_PCM_S24LE, MKTAG('4', '2', 'n', 'i') },
{ AV_CODEC_ID_PCM_S32BE, MKTAG('i', 'n', '3', '2') },
- { AV_CODEC_ID_PCM_S32LE, MKTAG('i', 'n', '3', '2') },
+ { AV_CODEC_ID_PCM_S32LE, MKTAG('2', '3', 'n', 'i') },
{ AV_CODEC_ID_PCM_S8, MKTAG('s', 'o', 'w', 't') },
{ AV_CODEC_ID_PCM_U8, MKTAG('r', 'a', 'w', ' ') },
{ AV_CODEC_ID_PCM_U8, MKTAG('N', 'O', 'N', 'E') },
--
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:09 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=176495096647.39.9450858938903143903@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