From: Jacob Lifshay <programmerjake-at-gmail.com@ffmpeg.org>
To: "ffmpeg-devel@ffmpeg.org" <ffmpeg-devel@ffmpeg.org>
Subject: [FFmpeg-devel] what AVCodecID to use for copying full vanc data between .mxf and .mcc
Date: Mon, 07 Jul 2025 21:12:17 -0700
Message-ID: <9029F661-A3AE-4C79-8C57-893D47EED528@gmail.com> (raw)
I'm currently writing a .mcc muxer, it currently translates from eia-608/708 to full vanc packets before outputting a .mcc file:
https://github.com/programmerjake/FFmpeg/tree/add-mcc-mux
I want to add the ability to the mxf and mcc muxers/demuxers to keep the full vanc data when doing stream copies, what do you think is the best way to do that?
* add a new AVCodecID for mxf vbi_vanc_smpte_436M
* change the muxers/demuxers to be able to use AV_CODEC_ID_SMPTE_KLV or AV_CODEC_ID_SMPTE_2038 (they hold the full vanc packets, right?)
* use the mxf vbi_vanc_smpte_436M stream as is -- AV_CODEC_ID_NONE and with vbi_vanc_smpte_436M in the metadata
additionally, it'd be nice to be able to output a eia-608/708 stream to mxf, so that would either need a codec/filter of some sort to translate to full vanc data in whatever format the mxf muxer ends up supporting, or to have that translation built-in to the mxf muxer, like it is built-in to the mxf demuxer (with eia608_extract).
What do you think?
Jacob
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
reply other threads:[~2025-07-08 4:12 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=9029F661-A3AE-4C79-8C57-893D47EED528@gmail.com \
--to=programmerjake-at-gmail.com@ffmpeg.org \
--cc=ffmpeg-devel@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