[x265] [PATCH] Use maximum frame size calculation of access unit 0 for all the key frames

[Ashok Kumar Mishra]

On Mon, Mar 26, 2018 at 10:35 AM, <aruna at multicorewareinc.com> wrote:

> # HG changeset patch
> # User Aruna Matheswaran <aruna at multicorewareinc.com>
> # Date 1521806936 -19800
> #      Fri Mar 23 17:38:56 2018 +0530
> # Node ID cda71a3fbc5f5d66944028f17c3e3eb7579adb38
> # Parent  2e370d98c806ea6ca4c9395bcd23f79cec22f2fb
> Use maximum frame size calculation of access unit 0 for all the key frames
>
> diff -r 2e370d98c806 -r cda71a3fbc5f source/encoder/ratecontrol.cpp
> --- a/source/encoder/ratecontrol.cpp    Fri Mar 23 15:51:41 2018 +0530
> +++ b/source/encoder/ratecontrol.cpp    Fri Mar 23 17:38:56 2018 +0530
> @@ -1290,7 +1290,7 @@
>          else
>          {
>              /* The spec has a special case for the first frame. */
> -            if (rce->encodeOrder == 0)
> +            if (curFrame->m_lowres.bKeyframe)
>              {
>                  /* 1.5 * (Max( PicSizeInSamplesY, fR * MaxLumaSr) +
> MaxLumaSr * (AuCpbRemovalTime[ 0 ] -AuNominalRemovalTime[ 0 ])) ? MinCr */
>                  double fr = 1. / 300;
>
> _______________________________________________
> x265-devel mailing list
> x265-devel at videolan.org
> https://mailman.videolan.org/listinfo/x265-devel
>
>
Pushed.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.videolan.org/pipermail/x265-devel/attachments/20180327/37e35c1e/attachment.html>