[FFmpeg-devel] [PATCH 001/281] Add a new channel layout API

[James Almer]

On 1/17/2022 10:51 AM, Nicolas George wrote:
> James Almer (12022-01-17):
>> And they can if they want to. It has a very specific purpose and it fulfills
>> it.
> 
> Just be clearer in the documentation.
> 
>> Please, stop asking for this. It's an incredibly niche usecase you want for
>> libavfilter, so you can and should implement it there. The API is there and
>> you can use it, you don't need to overdesign these general purpose helpers
>> to create these bizarre scenarios just to remove one or two filters from
>> your chain.
> 
> I will not stop asking for this, it is not specific to libavfilter: with
> a quick search, I spot -map_channel that requires exactly the same
> feature.

-map_channel works perfectly with the current bitmask API, and the new one.

> 
> There may be filters that require an option to distinguish one channel
> in particular; even if there are no now, there may be in the future. Can
> you guarantee it does not and will not happen?

Look at their IDs? Look at their names? Give them names if you need to?
And again, you keep talking about filtering scenarios. Lavfi can and 
should handle all this on its own internally, just like it was designed 
to, and not pollute an API meant to define the position a channel is 
supposed to be.

> 
> This use case happens at several places, therefore the parsing belongs
> in a common API.
> 
> Regards,
> 
> 
> _______________________________________________
> ffmpeg-devel mailing list
> ffmpeg-devel at ffmpeg.org
> https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
> 
> To unsubscribe, visit link above, or email
> ffmpeg-devel-request at ffmpeg.org with subject "unsubscribe".