> -----Original Message----- > From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On Behalf > Of Paul B Mahol > Sent: November 29, 2017 10:16 AM > To: FFmpeg development discussions and patches <ffmpeg- > de...@ffmpeg.org> > Subject: Re: [FFmpeg-devel] AMD external header > > On 11/29/17, Carl Eugen Hoyos <ceffm...@gmail.com> wrote: > > 2017-11-29 15:58 GMT+01:00 wm4 <nfx...@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@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? Thanks, Mikhail _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
