[FFmpeg-devel] AMD external header

[Marton Balint]

On Wed, 29 Nov 2017, Mironov, Mikhail wrote:

>> -----Original Message-----
>> From: ffmpeg-devel [mailto:ffmpeg-devel-bounces at ffmpeg.org] On Behalf
>> Of Paul B Mahol
>> Sent: November 29, 2017 10:16 AM
>> To: FFmpeg development discussions and patches <ffmpeg-
>> devel at ffmpeg.org>
>> Subject: Re: [FFmpeg-devel] AMD external header
>>
>> On 11/29/17, Carl Eugen Hoyos <ceffmpeg at gmail.com> wrote:
>>> 2017-11-29 15:58 GMT+01:00 wm4 <nfxjfg at googlemail.com>:
>>>
>>>> Well, don't worry too much. People like him are, as some would say,
>>>> toxic members of the community. Frequent drama and flame wars
>> happen.
>>>> (And here's where I wished ffmpeg were a properly managed project.)
>>>
>>> Look who's talking!
>>>
>>> Given that you started a fork of FFmpeg repeating ancient lies and
>>> stating you don't support FFmpeg anymore:
>>> Why do you post here?
>>
>> Because he like to argue with toxic people like you.
>> _______________________________________________
>> ffmpeg-devel mailing list
>> ffmpeg-devel at ffmpeg.org
>> http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
>
> Hi,
> This conversation is very entertaining but leads us nowhere.
> May I suggest to go down to business of enabling HW encoders by default?
> Yesterday Mark submitted the initial implementation and I really want
> to thank him for his mentoring and participation - it was very useful.
> The submission doesn't have AMD header so AMD encoder is off in any default build.
> I counted responses to my posts and found six people are for the default enabling
> of HW blocks one way or another: by including headers or pulling them out
> automatically using git (I guess via submodules?).
> Two people want to remove external headers and disable default HW acceleration.
> Question is: how to move forward on practical terms? I really don’t know how this team makes such decisions.
> Or maybe it is impasse case and  all want to keep things the way they are today?

The project has a voting system which was used in the past for issues 
where no consensus was reached. A voting however is a tedious process 
which usually leaves a few frustrated people on the losing side, so I'd 
say that is a last resort.

An alternative solution to adding AMD or removing Nvidia headers might be 
to simply disable the Nvidia hwaccel autodetection, and require the user 
to explicitly enable it. That seems mostly fair to me, and keeps the 
current status of the headers.

Regards,
Marton