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. 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? This use case happens at several places, therefore the parsing belongs in a common API. Regards, -- Nicolas George
signature.asc
Description: PGP signature
_______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
