From: Helmuth Schmitz via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Helmuth Schmitz <helmuthschmitz@gmail.com>
Subject: [FFmpeg-devel] Re: [PATCH] avformat/mxfenc: fix SMPTE 436M UL for ANC
Date: Mon, 15 Sep 2025 14:44:04 -0300
Message-ID: <CAP47Nu9yQzaOF2nOYRNXuODMJoqd8ETqyvHKATg1CLWWBi7OQg@mail.gmail.com> (raw)
In-Reply-To: <c6f67415-4ea5-4295-8642-e1d7ccc89edd@cji.paris>
Hi Nicolas,
Thanks for the clarification about Omneon.
I agree that it makes sense to simply fix the UL as in this patch.
Best regards,
Helmuth
Em seg., 15 de set. de 2025 às 11:40, Nicolas Gaullier via ffmpeg-devel <
ffmpeg-devel@ffmpeg.org> escreveu:
> On 9/15/25 15:26, Helmuth Schmitz via ffmpeg-devel wrote:
> > 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".
>
> FYI, early Omneon mxf api (>10 years back) had this bad version number,
> it was fixed later and all other implementations I have met write the
> right 0x09 value.
>
> I don't think we care about so ancient rare broken files, so it should
> be no big deal to simply fix this.
>
> Nicolas
>
> _______________________________________________
> ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
> To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org
>
_______________________________________________
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org
next prev parent reply other threads:[~2025-09-15 17:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-15 13:26 [FFmpeg-devel] " Helmuth Schmitz via ffmpeg-devel
2025-09-15 14:40 ` Nicolas Gaullier via ffmpeg-devel
2025-09-15 17:44 ` Helmuth Schmitz via ffmpeg-devel [this message]
2025-09-18 20:36 ` [FFmpeg-devel] " 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=CAP47Nu9yQzaOF2nOYRNXuODMJoqd8ETqyvHKATg1CLWWBi7OQg@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