[FFmpeg-devel] [PATCH] avdevice/avdevice: Deprecate AVDevice Capabilities API
James Almer
jamrial at gmail.com
Mon Jan 25 19:11:19 EET 2021
On 1/25/2021 1:46 PM, Nicolas George wrote:
> James Almer (12021-01-25):
>> Solving the hacky state of lavd <-> lavf *is* useful.
>
> The only "hacky state" comes from the useless split of the libraries.
And that's why we're trying to merge them. So again, a subdirectory is
not obligatory for this purpose, and alternative suggestions are welcome.
Even just saying to keep them in the root folder would be more useful
than saying "Work on something else".
>
>> And it would help the
>> project a lot if you could be a tiny bit less aggressive and dismissive of
>> other people's personal opinions.
>
> Anton is dismissive of other people's efforts — not just opinions — yet
> you said him nothing. Double standards.
Saying and thinking that lavd devices with their current capabilities
and API are not very useful is not being "dismissive of other people's
efforts", it's giving his opinion. He did it in fact as a reply to
Mark's comment that the KMS/DRM output device patch didn't seem like a
good idea.
Mark then suggested to directly replace/extend the API with one that's
more useful in the long run, instead of removing them as Anton suggested
since you and some other devs stated they in fact do have users, and you
agreed to that. So how about we try to move in that direction? The first
step is merging the libraries, and not trying to stop any relevant effort.
And for that matter, unlike you, Anton did not resort to ad hominem
attacks to back his argument.
>
> 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".
>
More information about the ffmpeg-devel
mailing list