From: Marton Balint <cus@passwd.hu> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH 001/293 v8] avutil/channel_layout: Add a new channel layout API Date: Mon, 24 Jan 2022 22:08:51 +0100 (CET) Message-ID: <8a44dca2-4c46-4fcc-5e4f-b2c536a6a28c@passwd.hu> (raw) In-Reply-To: <20220124204656.48625-1-jamrial@gmail.com> On Mon, 24 Jan 2022, James Almer wrote: > From: Anton Khirnov <anton@khirnov.net> > > The new API is more extensible and allows for custom layouts. > More accurate information is exported, eg for decoders that do not > set a channel layout, lavc will not make one up for them. > > Deprecate the old API working with just uint64_t bitmasks. > > Expanded and completed by Vittorio Giovara <vittorio.giovara@gmail.com> > and James Almer <jamrial@gmail.com>. > Signed-off-by: Vittorio Giovara <vittorio.giovara@gmail.com> > Signed-off-by: James Almer <jamrial@gmail.com> > --- > Changes since last version: > > *Both av_channel_layout_describe() and av_channel_layout_from_string() now > support a "2 channels (FL+LFE)" syntax, to signal native (usually > non-standard) or custom order layouts. > *a single decimal value is now interpreted as a mask by > av_channel_layout_from_string(), same as a single hexadecimal value. > *De-duplicated code by simplifying av_channel_layout_channel_from_string(). AV_CHAN_UNKWNOWN is fixed in the Amibsonic patch, but it should be fixed in this patch. > +/** > + * Check whether a channel layout is valid, i.e. can possibly describe audio > + * data. > + * > + * @param channel_layout input channel layout > + * @return 1 if channel_layout is valid, 0 otherwise. > + */ > +int av_channel_layout_check(const AVChannelLayout *channel_layout); I still find the name av_channel_layout_valid() more readable, but feel free to keep it as is if you disagree. Thanks, Marton _______________________________________________ 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:[~2022-01-24 21:09 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-24 20:46 James Almer 2022-01-24 21:08 ` Marton Balint [this message] 2022-01-24 21:21 ` James Almer 2022-01-27 15:08 ` Nicolas George 2022-01-31 13:27 ` Anton Khirnov 2022-03-16 0:41 ` Michael Niedermayer 2022-03-16 2:00 ` James Almer 2022-03-17 19:39 ` Michael Niedermayer 2022-03-17 19:46 ` James Almer 2022-03-17 19:51 ` James Almer
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=8a44dca2-4c46-4fcc-5e4f-b2c536a6a28c@passwd.hu \ --to=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