Re: [FFmpeg-devel] have some major changes for nvenc support

On 1/8/16, Andrey Turkin wrote: > In my opinion this proliferation of various filters which do the same thing > in different way is a configuration headache. There's CPU filters: one for > scaling/format conversion, one for padding, one for cropping, like 5 > different

Re: [FFmpeg-devel] have some major changes for nvenc support

On 11/5/15, wm4 wrote: > On Thu, 5 Nov 2015 16:23:04 +0800 > Agatha Hu wrote: > >> 2) We use AVFrame::opaque field to store a customized ffnvinfo struture >> to prevent expensive CPU<->GPU transferration. Without it, the workflow >> will be like CPU

Re: [FFmpeg-devel] have some major changes for nvenc support

2016-01-08 20:25 GMT+03:00 Michael Niedermayer : > Also slightly orthogonal but if you have 4 filters each written for a > different hwaccel you can write a generic filter that passes its > stuff to the appropriate one > If theres not much shareale code between hw specific

Re: [FFmpeg-devel] have some major changes for nvenc support

In my opinion this proliferation of various filters which do the same thing in different way is a configuration headache. There's CPU filters: one for scaling/format conversion, one for padding, one for cropping, like 5 different filters for deinterlacing. And now there would be nvresize for

Re: [FFmpeg-devel] have some major changes for nvenc support

On Fri, Jan 08, 2016 at 03:04:26PM +0300, Andrey Turkin wrote: > In my opinion this proliferation of various filters which do the same thing > in different way is a configuration headache. There's CPU filters: one for > scaling/format conversion, one for padding, one for cropping, like 5 >

[FFmpeg-devel] have some major changes for nvenc support

Hi, Recently Nvidia did some work on improving nvenc performance, it includes lots of change so I attach the patch instead of direct send. Here are the explanations: 1) The first main change is adding an nvresize filter (1:N, one input, multiple outputs) to do hardware resizing, because

Re: [FFmpeg-devel] have some major changes for nvenc support

On Thu, 5 Nov 2015 16:23:04 +0800 Agatha Hu wrote: > 2) We use AVFrame::opaque field to store a customized ffnvinfo struture > to prevent expensive CPU<->GPU transferration. Without it, the workflow > will be like CPU AVFrame input-->copy to GPU-->do CUDA resizing-->copy > to

Re: [FFmpeg-devel] have some major changes for nvenc support

在 2015/11/5 18:31, wm4 写道: On Thu, 5 Nov 2015 16:23:04 +0800 Agatha Hu wrote: 2) We use AVFrame::opaque field to store a customized ffnvinfo struture to prevent expensive CPU<->GPU transferration. Without it, the workflow will be like CPU AVFrame input-->copy to GPU-->do CUDA