From: Helmuth Schmitz via ffmpeg-devel <ffmpeg-devel@ffmpeg.org> To: ffmpeg-devel@ffmpeg.org Cc: Helmuth Schmitz <helmuthschmitz@gmail.com> Subject: [FFmpeg-devel] [PATCH] avformat/mxfenc: fix SMPTE 436M UL for ANC Date: Mon, 15 Sep 2025 10:26:20 -0300 Message-ID: <CAP47Nu_qDhFXzO9o=pFzFk_JCW9rdGdVWyht-9vgWgK+sD0vCg@mail.gmail.com> (raw) The first UL of the SMPTE 436M descriptor triple in mxfenc.c used 0x0a instead of 0x09. This caused generated MXF files without "MXF-GC Generic ANC Data Mapping" essence container descriptor. This patch corrects the UL to align with SMPTE RP224, so that the ANC descriptor is properly recognized. Tested with MXFInspect and Adobe Premiere: - Without the patch, the stream is not identified as ANC. - With the patch, the ANC data is correctly detected as "Generic ANC Data". Signed-off-by: Helmuth Schmitz <helmuthschmitz@gmail.com> --- diff --git a/libavformat/mxfenc.c b/libavformat/mxfenc.c index b14a480ba3..245c0853af 100644 --- a/libavformat/mxfenc.c +++ b/libavformat/mxfenc.c @@ -224,7 +224,7 @@ static const MXFContainerEssenceEntry mxf_essence_container_uls[] = { { 0x06,0x0E,0x2B,0x34,0x04,0x01,0x01,0x0a,0x04,0x01,0x02,0x02,0x01,0x00,0x00,0x00 }, mxf_write_h264_desc }, // S436M ANC - { { 0x06,0x0E,0x2B,0x34,0x04,0x01,0x01,0x0a,0x0D,0x01,0x03,0x01,0x02,0x0e,0x00,0x00 }, + { { 0x06,0x0E,0x2B,0x34,0x04,0x01,0x01,0x09,0x0D,0x01,0x03,0x01,0x02,0x0E,0x00,0x00 }, { 0x06,0x0E,0x2B,0x34,0x01,0x02,0x01,0x01,0x0D,0x01,0x03,0x01,0x17,0x01,0x02,0x00 }, { 0x06,0x0E,0x2B,0x34,0x04,0x01,0x01,0x0a,0x04,0x01,0x02,0x02,0x01,0x01,0x5C,0x00 }, mxf_write_s436m_anc_desc }, _______________________________________________ ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org
next reply other threads:[~2025-09-15 13:26 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2025-09-15 13:26 Helmuth Schmitz via ffmpeg-devel [this message] 2025-09-15 14:40 ` Nicolas Gaullier via ffmpeg-devel 2025-09-15 17:44 ` [FFmpeg-devel] " Helmuth Schmitz via ffmpeg-devel 2025-09-18 20:36 ` Tomas Härdin via ffmpeg-devel
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='CAP47Nu_qDhFXzO9o=pFzFk_JCW9rdGdVWyht-9vgWgK+sD0vCg@mail.gmail.com' \ --to=ffmpeg-devel@ffmpeg.org \ --cc=helmuthschmitz@gmail.com \ /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