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

[Steve Borho]

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?

-- 
Steve Borho