On 27.10.19 02:14, hydra at gmail.com wrote:
> > I see the attachment (attached by outlook) was scrubbed.
> > Sorry, I'd hoped it would work.
> > So, patch just pasted below to see if that works.
> >
> Please use git send-email. It's the easiest way to properly send patches
to the list
OK,
On 27.10.19 02:14, hydra3...@gmail.com wrote:
> I see the attachment (attached by outlook) was scrubbed.
> Sorry, I'd hoped it would work.
> So, patch just pasted below to see if that works.
>
Please use git send-email. It's the easiest way to properly send patches to the
list.
> On 14.10.2019 18:56 Timo Rothenpieler wrote:
> > On 14.10.2019 17:43, Hendrik Leppkes wrote:
> > > Since some users seem to have blindly passed -refs to their
> > > commandline which now fails without really telling them why, any
> > > thoughts on moving the capability check error messages onto a
On 14.10.2019 18:56 Timo Rothenpieler wrote:
> On 14.10.2019 17:43, Hendrik Leppkes wrote:
> > Since some users seem to have blindly passed -refs to their
> > commandline which now fails without really telling them why, any
> > thoughts on moving the capability check error messages onto a high log
On 14.10.2019 17:43, Hendrik Leppkes wrote:
Since some users seem to have blindly passed -refs to their
commandline which now fails without really telling them why, any
thoughts on moving the capability check error messages onto a high log
level so that they are shown by default, since they are t
On Fri, Sep 27, 2019 at 8:07 PM Timo Rothenpieler wrote:
>
> applied, but after some discussion on IRC, I opted to rename the current
> -refs option to -dpb_size, and use -refs for this one.
>
> -refs now matches what libx264 uses it for and what probably the
> majority of users expect.
Since som
applied, but after some discussion on IRC, I opted to rename the current
-refs option to -dpb_size, and use -refs for this one.
-refs now matches what libx264 uses it for and what probably the
majority of users expect.
___
ffmpeg-devel mailing list
f
Am Fr., 27. Sept. 2019 um 14:15 Uhr schrieb Timo Rothenpieler
:
>
> On 27/09/2019 12:28, Roman Arzumanyan wrote:
> >> First, this needs SDK Version Guards
> > Thanks, I've missed that. Added to patch.
>
> >> Second, in what way is this different from the existing global
> >> option(avctx->refs), w
On 27/09/2019 12:28, Roman Arzumanyan wrote:
First, this needs SDK Version Guards
Thanks, I've missed that. Added to patch.
Second, in what way is this different from the existing global
option(avctx->refs), which nvenc.c already uses to set
It's slightly different from existing global opti
eler
Sent: Friday, September 27, 2019 12:56 PM
To: FFmpeg development discussions and patches ; Roman
Arzumanyan
Cc: Yogender Gupta
Subject: Re: [FFmpeg-devel] [PATCH] avcodec/nvenc: multiple reference frames
support
On 27/09/2019 11:04, Roman Arzumanyan wrote:
> Hello,
>
> This patch a
On 27/09/2019 11:04, Roman Arzumanyan wrote:
Hello,
This patch adds multiple reference frames support (part of Video Codec SDK 9.1).
It adds "nb_ref_frames" CLI option to set number of reference frames. Possible
values:
* auto - let encoder decide (default value).
* [0;7] - set value
Hello,
This patch adds multiple reference frames support (part of Video Codec SDK 9.1).
It adds "nb_ref_frames" CLI option to set number of reference frames. Possible
values:
* auto - let encoder decide (default value).
* [0;7] - set value by hand. 0 is equal to auto.
Usage example:
ffm
12 matches
Mail list logo
