From: Anton Khirnov <anton@khirnov.net> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Cc: Marton Balint <cus@passwd.hu> Subject: Re: [FFmpeg-devel] [PATCH 3/5] avutil/channel_layout: add av_channel_layout_from_custom() Date: Thu, 01 Feb 2024 09:56:54 +0100 Message-ID: <170677781445.8914.8380277934131001805@lain.khirnov.net> (raw) In-Reply-To: <20240129232755.9622-3-cus@passwd.hu> Quoting Marton Balint (2024-01-30 00:27:53) > Signed-off-by: Marton Balint <cus@passwd.hu> > --- > doc/APIchanges | 3 +++ > libavutil/channel_layout.c | 20 ++++++++++++++++++++ > libavutil/channel_layout.h | 13 +++++++++++++ > libavutil/version.h | 4 ++-- > 4 files changed, 38 insertions(+), 2 deletions(-) > > diff --git a/doc/APIchanges b/doc/APIchanges > index e477ed78e0..8e8498f803 100644 > --- a/doc/APIchanges > +++ b/doc/APIchanges > @@ -2,6 +2,9 @@ The last version increases of all libraries were on 2023-02-09 > > API changes, most recent first: > > +2024-02-xx - xxxxxxxxxx - lavu 58.37.100 - channel_layout.h > + Add av_channel_layout_from_custom(). The name seems misleading to me, there is no 'custom' from which a channel layout is derived. It should be something like av_channel_layout_custom_init() instead. > +/** > + * Initialize a custom channel layout with the specified number of channels. > + * The designation of all channels will be unknown. > + * > + * @param channel_layout the layout structure to be initialized > + * @param nb_channels the number of channels > + * > + * @return 0 on success > + * AVERROR(EINVAL) if the number of channels <= 0 > + * AVERROR(ENOMEM) if the channel map could not be allocated > + */ It should say that this is a convenience helper, so people don't think this is the only way to build custom layouts. It should also explicitly say it allocates the channel map array. -- Anton Khirnov _______________________________________________ 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:[~2024-02-01 8:57 UTC|newest] Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-29 23:27 [FFmpeg-devel] [PATCH 1/5] avformat/mov_chan: do not assume channels are in native order Marton Balint 2024-01-29 23:27 ` [FFmpeg-devel] [PATCH 2/5] avformat/mov_chan: never override number of channels based on chan atom Marton Balint 2024-01-29 23:27 ` [FFmpeg-devel] [PATCH 3/5] avutil/channel_layout: add av_channel_layout_from_custom() Marton Balint 2024-02-01 8:56 ` Anton Khirnov [this message] 2024-02-01 20:01 ` Marton Balint 2024-02-02 4:42 ` Anton Khirnov 2024-01-29 23:27 ` [FFmpeg-devel] [PATCH 4/5] avutil/channel_layout: add av_channel_layout_retype() Marton Balint 2024-01-31 23:01 ` [FFmpeg-devel] [PATCH v2 " Marton Balint 2024-02-01 9:02 ` Anton Khirnov 2024-02-01 20:36 ` Marton Balint 2024-02-03 16:19 ` Anton Khirnov 2024-02-02 12:56 ` [FFmpeg-devel] [PATCH " James Almer 2024-02-03 10:38 ` Anton Khirnov 2024-02-03 13:24 ` James Almer 2024-02-04 19:28 ` [FFmpeg-devel] [PATCH v2 3/5] avutil/channel_layout: add av_channel_layout_custom_init() Marton Balint 2024-02-04 19:28 ` [FFmpeg-devel] [PATCH v2 4/5] avutil/channel_layout: add av_channel_layout_retype() Marton Balint 2024-02-09 15:10 ` Anton Khirnov 2024-02-11 22:38 ` Marton Balint 2024-02-11 22:51 ` James Almer 2024-02-11 23:03 ` Marton Balint 2024-02-04 19:28 ` [FFmpeg-devel] [PATCH v2 5/5] avformat/mov_chan: add support for reading custom channel layouts when layout_tag == 0 Marton Balint 2024-02-08 20:16 ` [FFmpeg-devel] [PATCH v3 " Marton Balint 2024-01-29 23:27 ` [FFmpeg-devel] [PATCH " Marton Balint 2024-02-08 19:25 ` [FFmpeg-devel] [PATCH 1/5] avformat/mov_chan: do not assume channels are in native order Marton Balint
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=170677781445.8914.8380277934131001805@lain.khirnov.net \ --to=anton@khirnov.net \ --cc=cus@passwd.hu \ --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