Quoting Vittorio Giovara (2017-06-29 00:10:45)
> +
> +enum AVChannelOrder {
> + /**
> + * The native channel order, i.e. the channels are in the same order in
> + * which they are defined in the AVChannel enum. This supports up to 63
> + * different channels.
> + */
> + AV_CHANNEL_ORDER_NATIVE,
> + /**
> + * The channel order does not correspond to any other predefined order
> and
> + * is stored as an explicit map. For example, this could be used to
> support
> + * layouts with 64 or more channels, or with channels that could be
> skipped.
> + */
> + AV_CHANNEL_ORDER_CUSTOM,
> + /**
> + * Only the channel count is specified, without any further information
> + * about the channel order.
This used to be just 'about the channels', and I think that was more
correct -- here we lack any informations about what the channels are,
not just their ordering. Alternatively 'about the channel order or
semantics'.
> +
> +/**
> + * Initialize a channel layout from a given string description.
> + * The input string can be represented by:
> + * - the formal channel layout name (returned by
> av_channel_layout_describe())
> + * - single or multiple channel names (returned by av_channel_name()
> + * or concatenated with "|")
Shouldn't this be
- single or multiple channel names (returned by av_channel_name())
concatenated with "|"
--
Anton Khirnov
_______________________________________________
libav-devel mailing list
libav-devel@libav.org
https://lists.libav.org/mailman/listinfo/libav-devel
