On Mon, Oct 24, 2016 at 11:24 PM, qw wrote:
> Hi,
>
>
> I have one question about some rare usage for avfilter graph:
>
>
> Sometimes, I want to change the setting in avfilter graph. For example,
> fps filter is used to set output frame rate, and it's expected that fps can
> be changed in accorda
Ivan Uskov nablet.com> writes:
>
> Hello All,
>
> After commit d30cf57a7b2097b565db02ecfffbdc9c16423d0e qsv-based
decoding
> aborts with crash, there are many incorrect places appeared. The
attached
> patch fixes the issues but keeps new method of the 'sync' variable
allocation
> in
Hi,
(Ivan, I am sending this mail to you directly because you said you are the
maintainer of QSV related code in a recent mail. Apologize if this is
inappropriate.. )
I am trying to use h264_qsv to transcode a MP4 file. This is my command:
ffmpeg -c:v h264_qsv -i input.mp4 -look_ahead 0 -c:v h264
On Mon, Jul 25, 2016 at 11:04 PM, Chao Liu wrote:
> Hi,
>
> (Ivan, I am sending this mail to you directly because you said you are the
> maintainer of QSV related code in a recent mail. Apologize if this is
> inappropriate.. )
>
> I am trying to use h264_qsv to transcode a
On Mon, Jul 25, 2016 at 11:08 PM, Chao Liu wrote:
>
>
> On Mon, Jul 25, 2016 at 11:04 PM, Chao Liu wrote:
>
>> Hi,
>>
>> (Ivan, I am sending this mail to you directly because you said you are
>> the maintainer of QSV related code in a recent mail. A
On Tue, Jul 26, 2016 at 2:08 AM, Ivan Uskov wrote:
>
> Hello Chao,
>
> Tuesday, July 26, 2016, 9:04:49 AM, you wrote:
>
> > I tried to debug it a bit by comparing ffmpeg code with intel media SDK.
> > There is sth. I don't understand. Not sure whether it's related..
> > In ffmpeg, we decode the f
Hi,
Looks like h264_qsv doesn't respect AVFrame.pict_type now.
It always encodes to non-key frames except for the first frame.
Is this a bug of ffmpeg or QSV doesn't support key frames?
Command I use:
ffmpeg -debug_ts -i orig.mp4 -force_key_frames 'expr:gte(t,n_forced)'
-look_ahead 0 -c:v h264_qsv
Need to add some code like following here
<https://github.com/FFmpeg/FFmpeg/blob/master/libavcodec/qsvenc.c#L941>
if (frame->pict_type == AV_PICTURE_TYPE_I) {
enc_ctrl->FrameType = MFX_FRAMETYPE_I | MFX_FRAMETYPE_IDR |
MFX_FRAMETYPE_REF;
}
On Mon, Aug 1, 2016 at 1:20
On Mon, Aug 15, 2016 at 6:00 PM, Jun Zhao wrote:
>
>
> On 2016/8/16 1:48, Jean-Baptiste Kempf wrote:
> > On 15 Aug, Hendrik Leppkes wrote :
> >> > On Mon, Aug 15, 2016 at 10:22 AM, Jun Zhao
> wrote:
> >>> > > add libyami decoder/encoder/vpp in ffmpeg, about build step,
> >>> > > please refer to
On Mon, Aug 15, 2016 at 7:44 PM, Jun Zhao wrote:
>
>
> On 2016/8/16 10:14, Chao Liu wrote:
> > On Mon, Aug 15, 2016 at 6:00 PM, Jun Zhao wrote:
> >
> >>
> >>
> >> On 2016/8/16 1:48, Jean-Baptiste Kempf wrote:
> >>> On 15 Aug, Hendrik L
On Mon, Aug 15, 2016 at 10:22 PM, Jun Zhao wrote:
>
>
> On 2016/8/16 11:07, Timothy Gu wrote:
> > Hi
> >
> > On Mon, Aug 15, 2016 at 7:44 PM Jun Zhao wrote:
> >
> >>
> >>
> >> On 2016/8/16 10:14, Chao Liu wrote:
> >>> Sor
On Tue, Aug 16, 2016 at 1:06 AM, Jun Zhao wrote:
>
>
> On 2016/8/16 15:37, Chao Liu wrote:
> > On Mon, Aug 15, 2016 at 7:44 PM, Jun Zhao wrote:
> >
> >>
> >>
> >> On 2016/8/16 10:14, Chao Liu wrote:
> >>> On Mon, Aug 15, 2016 at 6:00
On Tue, Aug 16, 2016 at 11:27 AM, Mark Thompson wrote:
> On 16/08/16 03:44, Jun Zhao wrote:
> >
> >
> > On 2016/8/16 10:14, Chao Liu wrote:
> >> On Mon, Aug 15, 2016 at 6:00 PM, Jun Zhao wrote:
> >>
> >>>
> >>>
> >>&
Hi there,
I compared h264_qsv decoder from ffmpeg to intel media sdk sample_decode.
There is pretty big speed gap. I wonder whether I did sth. wrong or there
are really some problems with ffmpeg's implementation..
The test video was captured from a 3MP(2048x1536) camera. The commands I
used:
- ff
On Wed, Aug 17, 2016 at 3:13 PM, Mark Thompson wrote:
> On 17/08/16 20:47, Chao Liu wrote:
> > Hi there,
> > I compared h264_qsv decoder from ffmpeg to intel media sdk sample_decode.
> > There is pretty big speed gap. I wonder whether I did sth. wrong or there
> > ar
On Wed, Aug 17, 2016 at 4:41 PM, Andy Furniss wrote:
> Mark Thompson wrote:
>
>> On 17/08/16 20:47, Chao Liu wrote:
>>
>>> Hi there,
>>> I compared h264_qsv decoder from ffmpeg to intel media sdk sample_decode.
>>> There is pretty big speed gap. I won
On Thu, Aug 18, 2016 at 7:50 AM, Moritz Barsnick wrote:
> On Wed, Aug 17, 2016 at 23:13:13 +0100, Mark Thompson wrote:
> > > The test video was captured from a 3MP(2048x1536) camera. The commands
> I
> > > used:
> > > - ffmpeg -c:v h264_qsv -async_depth 10 -i test.h264 -c:v rawvideo -f
> null
>
On Sat, Sep 24, 2016 at 6:18 AM, wm4 wrote:
> On Sat, 24 Sep 2016 02:34:56 +0200
> Michael Niedermayer wrote:
>
> > On Mon, Aug 15, 2016 at 04:22:33PM +0800, Jun Zhao wrote:
> > > add libyami decoder/encoder/vpp in ffmpeg, about build step,
> > > please refer to the link: https://github.com/01or
On Wed, Sep 28, 2016 at 2:45 PM, wm4 wrote:
> On Wed, 28 Sep 2016 12:18:38 -0700
> Chao Liu wrote:
>
> > On Sat, Sep 24, 2016 at 6:18 AM, wm4 wrote:
> >
> > > On Sat, 24 Sep 2016 02:34:56 +0200
> > > Michael Niedermayer wrote:
> > >
> >
On Wed, Sep 28, 2016 at 3:23 PM, Mark Thompson wrote:
> On 28/09/16 22:57, Chao Liu wrote:
> > BTW, is there any plan to support VP8 with vaapi hwaccel?
>
> No plan; already done: <https://git.libav.org/?p=libav.git;a=commit;h=
> a9fb134730da1f9642eb5a2baa50943b8a4aa245&g
Have you ever used valgrind? Please just run the command below:
valgrind --leak-check=full --log-file=out.log ffmpeg -hwaccel qsv
-qsv_device /dev/dri/renderD128 -c:v h264_qsv -i a.h264 -c:v h264_qsv -b:v
2M -y out.h264
See line 3323 of ffmpeg.c,
ret = avcodec_copy_context(ost->st->codec,
On Sun, Jan 22, 2017 at 9:03 PM, Mark Thompson wrote:
> On 20/01/17 02:06, Huang, Zhengxu wrote:
> > From 9ceb2ac6a89246f2e686eb3ad3448fbaff5328f7 Mon Sep 17 00:00:00 2001
> > From: Zhengxu
> > Date: Fri, 13 Jan 2017 10:33:05 +0800
> > Subject: [PATCH] lavformat/utils: Fix a memleak that
> st->c
22 matches
Mail list logo
