[x265] [PATCH] ratecontrol: improve visual quality and bitrate savings in ABR

Aarthi Priya Thirumalai aarthi at multicorewareinc.com
Thu May 29 20:57:58 CEST 2014


On May 30, 2014 12:20 AM, "Steve Borho" <steve at borho.org> wrote:
>
> On Thu, May 29, 2014 at 1:43 PM, Aarthi Priya Thirumalai
> <aarthi at multicorewareinc.com> wrote:
> > initially both frameNumThreads and m_totalFrameThreads are set to same
value
> > specificed by user. So, we are always  creating frameEncoder objects,
> > frameNumThreads holds actual frame thread count.
> > Only when we begin to encode, we change the value n within that second
we
> > reset it to orig num of frame threads. So , the destroy func called at
very
> > end can use frameNumThreads safely. Logically, There shouldn't be memory
> > leaks here..
>
> If the clip is less than half a second long?

:) ok.
>
> --
> Steve Borho
> _______________________________________________
> x265-devel mailing list
> x265-devel at videolan.org
> https://mailman.videolan.org/listinfo/x265-devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.videolan.org/pipermail/x265-devel/attachments/20140530/cac22653/attachment.html>


More information about the x265-devel mailing list