From: Jacob Lifshay <programmerjake@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] what AVCodecID to use for copying full vanc data between .mxf and .mcc
Date: Wed, 23 Jul 2025 14:00:03 -0700
Message-ID: <4188E516-8830-4C46-A703-1B04585E646C@gmail.com> (raw)
In-Reply-To: <fc785db1d19dfcb029ed26c9732db5189cdcd40b.camel@haerdin.se>
On July 23, 2025 1:01:32 PM PDT, "Tomas Härdin" <git@haerdin.se> wrote:
> Perhaps I should have made it clear that I'm just spitballing what kind
> of workflows we should keep in mind with this stuff. I'm not suggesting
> we need to add support for everything right away. Just that we should
> take steps toward a sane architecture for all this stuff. I'm not sure
> what that would be though
sounds good! I've tried to aim for a sane architecture, but some of those later steps I'll definitely be leaving for others to implement.
I created a draft PR (comments appreciated):
https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20024
I still need to add fate tests and docs, I'm hoping to get it merged before 8.0 branches since I'll need some of that functionality in casparcg.
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".
prev parent reply other threads:[~2025-07-23 21:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-08 4:12 Jacob Lifshay
2025-07-09 0:08 ` Devin Heitmueller
2025-07-09 2:37 ` Jacob Lifshay
2025-07-09 13:42 ` Devin Heitmueller
2025-07-22 12:21 ` Tomas Härdin
2025-07-22 20:56 ` Jacob Lifshay
2025-07-23 20:01 ` Tomas Härdin
2025-07-23 21:00 ` Jacob Lifshay [this message]
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=4188E516-8830-4C46-A703-1B04585E646C@gmail.com \
--to=programmerjake@gmail.com \
--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