From: James Almer <jamrial@gmail.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] [RFC]avformat: introduce AVStreamGroup
Date: Mon, 2 Oct 2023 16:48:31 -0300
Message-ID: <25251dc5-ade2-4206-893e-8ee135ec9286@gmail.com> (raw)
In-Reply-To: <169623871010.6638.6939823444947670953@lain.khirnov.net>
On 10/2/2023 6:25 AM, Anton Khirnov wrote:
> Quoting Tomas Härdin (2023-09-28 13:27:53)
>> Yes, a typed union like this should work nicely. This way we keep
>> things related to each type of stream group separate.
>
> I agree that this seems like a better solution than repurposing
> AVCodecParameters, but the union members probably need to be pointers to
> keep both the stream group and the type-specific structs extensible.
Good idea, will do that and re-send.
_______________________________________________
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".
next prev parent reply other threads:[~2023-10-02 19:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-06 14:38 James Almer
2023-09-06 17:53 ` Tomas Härdin
2023-09-06 19:16 ` James Almer
2023-09-13 9:34 ` Tomas Härdin
2023-09-13 14:33 ` [FFmpeg-devel] J2K in HEIF was: " Pierre-Anthony Lemieux
2023-09-13 20:41 ` Tomas Härdin
2023-09-15 18:10 ` [FFmpeg-devel] [PATCH] " James Almer
2023-09-28 11:27 ` Tomas Härdin
2023-10-02 9:25 ` Anton Khirnov
2023-10-02 19:48 ` James Almer [this message]
2023-10-02 9:37 ` Anton Khirnov
2023-10-02 12:10 ` James Almer
2023-10-03 15:43 ` Anton Khirnov
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=25251dc5-ade2-4206-893e-8ee135ec9286@gmail.com \
--to=jamrial@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