On 01.12.2017 00:32, Marton Balint wrote:

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

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.

Still some decision about these external headers should be made but the outcome would have less impact on user experience.

What is the current policy for adding a library on the HWACCEL_AUTODETECT_LIBRARY_LIST versus putting it on HWACCEL_LIBRARY_LIST? Is it different from EXTERNAL_AUTODETECT_LIBRARY_LIST / EXTERNAL_LIBRARY_LIST?


ffmpeg-devel mailing list

Reply via email to