Re: [FFmpeg-devel] [PATCH 6/7] avcodec: allow multiple hwaccels for the same codec/pixfmt

2017-10-03 Thread wm4
On Tue, 3 Oct 2017 15:58:32 +0200 Timo Rothenpieler wrote: > > -static AVHWAccel *find_hwaccel(enum AVCodecID codec_id, > > +static AVHWAccel *find_hwaccel(AVCodecContext *avctx, > > enum AVPixelFormat pix_fmt) > > { > > AVHWAccel

Re: [FFmpeg-devel] [PATCH 6/7] avcodec: allow multiple hwaccels for the same codec/pixfmt

2017-10-03 Thread Philip Langdale
On Tue, 3 Oct 2017 15:15:17 +0200 wm4 wrote: > Currently, AVHWAccels are looked up using a (codec_id, pixfmt) tuple. > This means it's impossible to have 2 decoders for the same codec and > using the same opaque hardware pixel format. > > This breaks merging Libav's

Re: [FFmpeg-devel] [PATCH 6/7] avcodec: allow multiple hwaccels for the same codec/pixfmt

2017-10-03 Thread wm4
On Tue, 3 Oct 2017 15:58:32 +0200 Timo Rothenpieler wrote: > Am 03.10.2017 um 15:15 schrieb wm4: > > Currently, AVHWAccels are looked up using a (codec_id, pixfmt) tuple. > > This means it's impossible to have 2 decoders for the same codec and > > using the same opaque

Re: [FFmpeg-devel] [PATCH 6/7] avcodec: allow multiple hwaccels for the same codec/pixfmt

2017-10-03 Thread Timo Rothenpieler
Am 03.10.2017 um 15:15 schrieb wm4: Currently, AVHWAccels are looked up using a (codec_id, pixfmt) tuple. This means it's impossible to have 2 decoders for the same codec and using the same opaque hardware pixel format. This breaks merging Libav's CUVID hwaccel. FFmpeg has its own CUVID

[FFmpeg-devel] [PATCH 6/7] avcodec: allow multiple hwaccels for the same codec/pixfmt

2017-10-03 Thread wm4
Currently, AVHWAccels are looked up using a (codec_id, pixfmt) tuple. This means it's impossible to have 2 decoders for the same codec and using the same opaque hardware pixel format. This breaks merging Libav's CUVID hwaccel. FFmpeg has its own CUVID support, but it's a full stream decoder,