[x265] Another performance issue on ARM code

I found some issues in ARM code, I don't point out on time, that's my failure. Such as these garbage code in x265_pixel_add_ps_4x4_neon: vmov.u16q10, #255 veor.u16q11, q11 veor.u16d3, d3 veor.u16d5, d5 btw: the ARM build was broken after

Re: [x265] [PATCH] Add vbv-end tolerance check

This may still break HRD compliance -- imagine you have a large amount of chunks (hundreds or thousands per movie) which you encode in parallel. Under VBV-based (VBV or VBV+CRF) rate control you try running as close to the buffer capacity as you can. If uncoordinated overshoot of e.g. 4% in buffer

Re: [x265] [PATCH x265] Add support for chunked encoding

On Fri, Jun 8, 2018 at 2:53 PM, wrote: > # HG changeset patch > # User Aruna Matheswaran > # Date 1521010828 -19800 > # Wed Mar 14 12:30:28 2018 +0530 > # Node ID 182914e1d201395d152e310db7f5cf29ab3c787e > # Parent 03dcb3457b7eafc6a13fd317286d70921a5b7dfe > Add support for chunked

Re: [x265] [PATCH x265] Use the data structure of analysis-save/load for multi-pass-opt-analysis/multi-pass-opt-distortion

On Fri, Jun 8, 2018 at 5:44 PM, wrote: > # HG changeset patch > # User Aruna Matheswaran > # Date 1526883919 -19800 > # Mon May 21 11:55:19 2018 +0530 > # Node ID 00eec4796d233e72d6344c7f4c9d5c69a9c55501 > # Parent ed853c4af6710a991d0cdf4bf68e00fe32edaacb > Use the data structure of

Re: [x265] [PATCH] Add vbv-end tolerance check

On Mon, Jun 11, 2018 at 10:54 AM, Aruna Matheswaran < ar...@multicorewareinc.com> wrote: > > > On Mon, Jun 11, 2018 at 3:34 AM, Alex Giladi > wrote: > >> Does this "5% tolerance" imply that CPB fullness as defined by vbv-end >> can be exceeded by 5%? >> > > yes, the CPB fullness can vary by +/-