Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Marton Balint <cus@passwd.hu>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH v2 4/5] avutil/channel_layout: add av_channel_layout_retype()
Date: Sun, 11 Feb 2024 23:38:29 +0100 (CET)
Message-ID: <0b996495-fa12-c244-186a-821c183f247b@passwd.hu> (raw)
In-Reply-To: <170749145587.8914.1907905647574802862@lain.khirnov.net>



On Fri, 9 Feb 2024, Anton Khirnov wrote:

> Quoting Marton Balint (2024-02-04 20:28:11)
>> +/**
>> + * Change the AVChannelOrder of a channel layout.
>> + *
>> + * Change of AVChannelOrder can be either lossless or lossy. In case of a
>> + * lossless conversion all the channel designations and the associated channel
>> + * names (if any) are kept. On a lossy conversion the channel names and channel
>> + * designations might be lost depending on the capabilities of the desired
>> + * AVChannelOrder. Note that some conversions are simply not possible in which
>> + * case this function returns AVERROR(ENOSYS).
>> + *
>> + * The following conversions are supported:
>> + *
>> + * Any       -> Custom     : Always possible, always lossless.
>> + * Any       -> Unspecified: Always possible, lossless if channel designations
>> + *   are all unknown and channel names are not used, lossy otherwise.
>> + * Custom    -> Ambisonic  : Possible if it contains ambisonic channels with
>> + *   optional non-diegetic channels in the end. Lossy if the channels have
>> + *   custom names, lossless otherwise.
>> + * Custom    -> Native     : Possible if it contains native channels in native
>> + *     order. Lossy if the channels have custom names, lossless otherwise.
>> + *
>> + * On error this function keeps the original channel layout untouched.
>> + *
>> + * @param channel_layout channel layout which will be changed
>> + * @param order the desired channel layout order
>> + * @param flags a combination of AV_CHANNEL_LAYOUT_RETYPE_FLAG_* constants
>> + * @return 0 if the conversion was successful and lossless or if the channel
>> + *           layout was already in the desired order
>> + *         1 if the conversion was successful but lossy
>
> You could say 'positive number' instead of 1, which leaves us wiggle
> room to use other numbers in the future in a backwards compatible way.
>
> Looks ok otherwise.

Ok, thanks, will apply the series with that change.

Regards,
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".

  reply	other threads:[~2024-02-11 22:38 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
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 [this message]
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=0b996495-fa12-c244-186a-821c183f247b@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