[x265] [PATCH] analysis: fix output change in --cu-lossless and analysis-load mode for Intra slice

# HG changeset patch # User Kavitha Sampath # Date 1445238772 -19800 # Mon Oct 19 12:42:52 2015 +0530 # Node ID 8c6e6165dcb4e93f61f253028a2bec6080a174dd # Parent 04575a459a160162391fcf1a12e8e6f2e81e95b4 analysis: fix output change in --cu-lossless and

[x265] [PATCH] cmake: correct order of linking

# HG changeset patch # User Deepthi Nandakumar # Date 1445247748 -19800 # Mon Oct 19 15:12:28 2015 +0530 # Node ID 8589ea49854604d35bd0e84cd06ac82e6dbdc016 # Parent 1bcfea4372d90ceca3db6c262eaaf19147537c27 cmake: correct order of linking First, the library

[x265] [PATCH] asm: fix intrapred_planar16x16 sse4 code for main12

# HG changeset patch # User Dnyaneshwar G # Date 1445245458 -19800 # Mon Oct 19 14:34:18 2015 +0530 # Node ID 76d4fc7264a0d22218db30f65bb58095c294db1b # Parent 04575a459a160162391fcf1a12e8e6f2e81e95b4 asm: fix intrapred_planar16x16 sse4 code for main12

Re: [x265] [PATCH] asm: fix intrapred_planar16x16 sse4 code for main12

At 2015-10-19 18:43:57,dnyanesh...@multicorewareinc.com wrote: ># HG changeset patch ># User Dnyaneshwar G ># Date 1445245458 -19800 ># Mon Oct 19 14:34:18 2015 +0530 ># Node ID 76d4fc7264a0d22218db30f65bb58095c294db1b ># Parent

[x265] [PATCH] asm: extend constant 0x3FFF to 256-bits (fix issue #204)

# HG changeset patch # User Min Chen # Date 1445294421 18000 # Node ID 11c81b81da37e9251d6d6ec36f666f5ac6d57bed # Parent 1bcfea4372d90ceca3db6c262eaaf19147537c27 asm: extend constant 0x3FFF to 256-bits (fix issue #204) --- source/common/x86/const-a.asm |2 +-

[x265] Under VBV rc mode , increasing the vbv-maxrate or vbv-bufsize has no or very little effect on the final result

Recently, I am testing the x265 codes and mostly on VBV rc mode.\ But, I find an strange problem. For instance, I set up the following test circumstance: resolution: 1920x1080 bitrate=1000kbps, vbv-bufsize=3000kbit when I set vbv-maxbitrate>1250kbps, I get almost the same result, like the same