[x265] [PATCH] cutree: identify the correct b-ref to estimate propagatecost

Steve Borho steve at borho.org
Thu May 22 18:04:04 CEST 2014


On Fri, May 16, 2014 at 4:41 AM, Steve Borho <steve at borho.org> wrote:
> On Thu, May 15, 2014 at 2:02 AM,  <gopu at multicorewareinc.com> wrote:
>> # HG changeset patch
>> # User Gopu Govindaswamy
>> # Date 1400137266 -19800
>> #      Thu May 15 12:31:06 2014 +0530
>> # Node ID 6ca880d7e68361e5b9e2353f05369d9e5c40a29f
>> # Parent  d5b42a9fe43ba877f90f73a11a071d9e449e9661
>> cutree: identify the correct b-ref to estimate propagatecost
>
> This patch is blocked until I get a response from the x264 developers
> about the same issue in their slicetype.c

I added printfs for the frame numbers being analyzed for BREF and
finally decided for BREF and figured that the current behavior is
better.  I'm dropping this patch from my backlog

-- 
Steve Borho


More information about the x265-devel mailing list