On 16/02/2018 18:28, Diego Biurrun wrote:
On Fri, Feb 16, 2018 at 06:02:05PM +0100, Luca Barbato wrote:
Unbreaks the rate-control behaviour.
How does this unbreak what?
Locally amended adding:
The API expects an average framerate, the timebase is often
1/1000 while the reported average fram
On Fri, Feb 16, 2018 at 9:15 PM, Luca Barbato wrote:
> On 17/02/2018 00:57, wm4 wrote:
>
>> On Fri, 16 Feb 2018 18:02:05 +0100
>> Luca Barbato wrote:
>>
>> Unbreaks the rate-control behaviour.
>>>
>>
Would be nice that the commit message is expanded, explaining what is
currently broken and how t
On 17/02/2018 00:57, wm4 wrote:
On Fri, 16 Feb 2018 18:02:05 +0100
Luca Barbato wrote:
Unbreaks the rate-control behaviour.
---
libavcodec/libx265.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/libavcodec/libx265.c b/libavcodec/libx265.c
index fd5452193b..73aff2ca
On Fri, 16 Feb 2018 18:02:05 +0100
Luca Barbato wrote:
> Unbreaks the rate-control behaviour.
> ---
> libavcodec/libx265.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/libavcodec/libx265.c b/libavcodec/libx265.c
> index fd5452193b..73aff2caef 100644
> --- a/libav
On 16/02/2018 18:28, Diego Biurrun wrote:
On Fri, Feb 16, 2018 at 06:02:05PM +0100, Luca Barbato wrote:
Unbreaks the rate-control behaviour.
How does this unbreak what?
If your timebase is 1/1000 and your actual frame rate is 30, it gets
extra creative in deciding how many bits allocate pe
On Fri, Feb 16, 2018 at 06:02:05PM +0100, Luca Barbato wrote:
> Unbreaks the rate-control behaviour.
How does this unbreak what?
Diego
___
libav-devel mailing list
libav-devel@libav.org
https://lists.libav.org/mailman/listinfo/libav-devel