[FFmpeg-devel] [PATCH] AVHWAccel infrastructure v2 (take 4) (ping)

Gwenole Beauchesne gbeauchesne
Tue Feb 16 14:23:06 CET 2010

On Mon, 4 Jan 2010, Gwenole Beauchesne wrote:

> On Mon, 4 Jan 2010, Michael Niedermayer wrote:
>>> In the new model I wanted to use, hwaccel_context was to be solely
>>> maintained by libavcodec. However, it still needed a way to get some
>>> hwaccel context initialized by the user-application. e.g. a VADisplay 
>>> (void
>>> I felt interesting to pass this information through hwaccel attrs along
>>> with other int attributes.
>> We have existing means to pass information, that is through AVCodecContext
>> and using AVOption where appropriate
>> As well as using AVFrame instead of AVCodecContext where its per frame
>> data
> OK, I nuked the hwaccel attrs and replaced it with 
> AVCodecContext.hwaccel_{id,flags}. hwaccel_flags is handled by AVOption. I 
> left hwaccel_id as is to match existing practise (pix_fmt et al.).
> I haven't tested with MPlayer yet but this new approach still works with my 
> modified ffplay.


More information about the ffmpeg-devel mailing list