From: "Tomas Härdin" <git@haerdin.se> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH] [RFC]avformat: introduce AVStreamGroup Date: Wed, 06 Sep 2023 19:53:15 +0200 Message-ID: <a005f4e1e273ed54bc6692b13a9c8aa7fcfc8e9e.camel@haerdin.se> (raw) In-Reply-To: <20230906143832.54604-1-jamrial@gmail.com> ons 2023-09-06 klockan 11:38 -0300 skrev James Almer: > Signed-off-by: James Almer <jamrial@gmail.com> > --- > This is an initial proof of concept for AVStream groups, something > that's > needed for quite a few existing and upcoming formats that lavf has no > way to > currently export. Said formats define a single video or audio stream > composed > by merging several individualy multiplexed streams within a media > file. > This is the case of HEIF, a format defining a tiled image where each > tile is a > separate image (either hevc, av1, etc) all of which need to be > decoded > individualy and then stitched together for presentation using > container level > information; I remember this blocking HEIF as a GSoC project. Honestly the way that format is designed is immensely horrible. > MPEG-TS programs, currently exported as > AVProgram, which this new general purpose API would replace. I can foresee this being a nuisance for users accustomed to AVProgram. Also this feature borders on NLE territory. Not necessarily a bad thing, but FFmpeg is overall poorly architectured for NLE stuff. I believe I raised this issue back when lavfi was proposed, it being wholly unsuitable for NLE work. > +typedef struct AVStreamGroup { > + /** > + * A class for @ref avoptions. Set on stream creation. > + */ > + const AVClass *av_class; > + > + /** > + * Group index in AVFormatContext. > + */ > + int index; > + > + /** > + * Format-specific group ID. > + * decoding: set by libavformat > + * encoding: set by the user, replaced by libavformat if left > unset > + */ > + int id; > + > + /** > + * Codec parameters associated with this stream group. Allocated > and freed > + * by libavformat in avformat_new_stream_group() and > avformat_free_context() > + * respectively. > + * > + * - demuxing: filled by libavformat on stream group creation or > in > + * avformat_find_stream_info() > + * - muxing: filled by the caller before avformat_write_header() > + */ > + AVCodecParameters *codecpar; > + > + void *priv_data; > + > + /** > + * Number of elements in AVStreamGroup.stream_index. > + * > + * Set by av_stream_group_add_stream() and > av_stream_group_new_stream(), must not > + * be modified by any other code. > + */ > + int nb_stream_indexes; > + > + /** > + * A list of indexes of streams in the group. New entries are > created with > + * av_stream_group_add_stream() and > av_stream_group_new_stream(). > + * > + * - demuxing: entries are created by libavformat in > avformat_open_input(). > + * If AVFMTCTX_NOHEADER is set in ctx_flags, then > new entries may also > + * appear in av_read_frame(). > + * - muxing: entries are created by the user before > avformat_write_header(). > + * > + * Freed by libavformat in avformat_free_context(). > + */ > + int *stream_index; > +} AVStreamGroup; I see no provisions for attaching metadata, for example HEIF stitching. Putting it in coderpar seems wrong, since it is container-level metadata. We could just have an HEIF specific struct as container metadata. /Tomas _______________________________________________ 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-09-06 17:53 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 [this message] 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 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=a005f4e1e273ed54bc6692b13a9c8aa7fcfc8e9e.camel@haerdin.se \ --to=git@haerdin.se \ --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