Re: [FFmpeg-devel] [PATCH] frame: Simplify the video allocation

2018-09-03 Thread Maxym Dmytrychenko
On Mon, Sep 3, 2018 at 10:17 AM Michael Niedermayer wrote: > On Sun, Sep 02, 2018 at 09:34:23PM -0300, James Almer wrote: > > From: Luca Barbato > > > > Merged-by: James Almer > > --- > > This is the next merge in the queue. It's a critical part of the AVFrame > API, > > so even if FATE passes

Re: [FFmpeg-devel] [PATCH] frame: Simplify the video allocation

2018-09-11 Thread Maxym Dmytrychenko
On Tue, Sep 11, 2018 at 6:43 PM James Almer wrote: > On 9/3/2018 6:03 AM, Maxym Dmytrychenko wrote: > > On Mon, Sep 3, 2018 at 10:17 AM Michael Niedermayer > > > wrote: > > > >> On Sun, Sep 02, 2018 at 09:34:23PM -0300, James Almer wrote: > >>> Fro

Re: [FFmpeg-devel] [PATCH 1/2] lavu/qsv: fix a random hwupload failure regression

2018-10-01 Thread Maxym Dmytrychenko
On Sun, Sep 30, 2018 at 11:14 AM Zhong Li wrote: > Variable 'ret' hasn't been initialized,thus introducing a random > hwupload failure regression due to qsv session uninitialized. > > Signed-off-by: Zhong Li > --- > libavutil/hwcontext_qsv.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(

Re: [FFmpeg-devel] [PATCH 2/2] lavu/qsv: make a copy as libmfx alignment requirement for uploading

2018-10-01 Thread Maxym Dmytrychenko
On Sun, Sep 30, 2018 at 11:14 AM Zhong Li wrote: > Libmfx requires 16 bytes aligned input/output for uploading. > Currently only output is 16 byte aligned and assigning same width/height to > input with smaller buffer size actually, thus definitely will cause > segment fault. > > Can reproduce wi

Re: [FFmpeg-devel] [PATCH] libavcodec/qsvenc_hevc: correction for QSV HEVC default plugin selection on Windows

2018-10-12 Thread Maxym Dmytrychenko
On Tue, Oct 9, 2018 at 3:50 AM Landgraph wrote: > 1. Old logic meaned: everywhere, except Windows, ffmpeg has to use HW > acceleration, but on Windows ffmpeg has to use (unavailable) software > encode by default > 2. Software encode is available only if you provide corresponding > software MediaS

Re: [FFmpeg-devel] [PATCH] libavcodec/qsvenc_hevc: correction for QSV HEVC default plugin selection on Windows

2018-10-13 Thread Maxym Dmytrychenko
On Sat, Oct 13, 2018 at 6:43 PM Mark Thompson wrote: > On 06/10/18 07:21, Landgraph wrote: > > 1. Old logic meaned: everywhere, except Windows, ffmpeg has to use HW > acceleration, but on Windows ffmpeg has to use (unavailable) software > encode by default > > 2. Software encode is available only

Re: [FFmpeg-devel] [PATCH 2/2] lavf/qsvvpp: cope with MFX_ERR_MORE_DATA condition in VPP pipeline

2019-01-14 Thread Maxym Dmytrychenko
On Mon, Jan 14, 2019 at 5:53 PM Rostislav Pehlivanov wrote: > On Mon, 14 Jan 2019 at 12:40, Linjie Fu wrote: > > > Returning AVERROR(EAGAIN) when libmfx needs more data will cause the > > failure > > of requesting the next frame and lead to an infinite loop. > > > > Sleep for a while to release

Re: [FFmpeg-devel] [PATCH] lavf/qsv_scale: add scaling mode option

2019-01-16 Thread Maxym Dmytrychenko
On Wed, Jan 16, 2019 at 9:55 AM Zhong Li wrote: > Signed-off-by: Zhong Li > --- > libavfilter/vf_scale_qsv.c | 36 +++- > 1 file changed, 31 insertions(+), 5 deletions(-) > > diff --git a/libavfilter/vf_scale_qsv.c b/libavfilter/vf_scale_qsv.c > index 7d593b2..f9

Re: [FFmpeg-devel] [PATCH] avutil/hwcontext_qsv: fix log level for session initialization error

2018-07-05 Thread Maxym Dmytrychenko
do you really want to have warning log with the error statement inside? (root case of such MFXVideoVPP_Init behaviour is different topic and actually should be re-checked) just looking at the initial issue on Windows: >I thought I had the entire pipeline (decode/scale-resize/encode) being performe