benwaggoner
6th May 2016, 19:02
I haven't seen a mention of the new r2692 release of x264 from a couple weeks ago.
http://git.videolan.org/?p=x264.git;a=shortlog;h=refs/heads/stable
There are a variety of bug fixes and minor-sounding performance tweaks. However, the below sounds like a potentially meaningful quality improvement:
Revise the 2-pass algorithm
author Anton Mitrofanov <BugMaster@narod.ru>Tue, 13 Oct 2015
committer Henrik Gramner <henrik@gramner.com>Sat, 16 Jan 2016
Use the correct default B-ref placement with B-pyramid
Cost analyse functions expects the placement of the B-ref in a sequence of an even number of B-frames to be located towards the beginning while the actual placement was towards the end.
Change the placement to be consistent with the analyse expectations, e.g. PbbBbP -> PbBbbP.
And the below which sound potentially promising, but have rather..."terse " documentation.
Revise the row VBV algorithm (part 2)
author Anton Mitrofanov <BugMaster@narod.ru>Mon, 4 Jan 2016
committer Henrik Gramner <henrik@gramner.com>Sat, 16 Jan 2016
Should fix rare cases of VBV emergency mode activation caused by too much trust to the row predictors.
2-pass: Take into account possible frame reordering
author Anton Mitrofanov <BugMaster@narod.ru>Tue, 13 Oct 2015
committer Henrik Gramner <henrik@gramner.com>Sat, 16 Jan 2016
Can anyone shed some light on these changes and their potential impact?
http://git.videolan.org/?p=x264.git;a=shortlog;h=refs/heads/stable
There are a variety of bug fixes and minor-sounding performance tweaks. However, the below sounds like a potentially meaningful quality improvement:
Revise the 2-pass algorithm
author Anton Mitrofanov <BugMaster@narod.ru>Tue, 13 Oct 2015
committer Henrik Gramner <henrik@gramner.com>Sat, 16 Jan 2016
Use the correct default B-ref placement with B-pyramid
Cost analyse functions expects the placement of the B-ref in a sequence of an even number of B-frames to be located towards the beginning while the actual placement was towards the end.
Change the placement to be consistent with the analyse expectations, e.g. PbbBbP -> PbBbbP.
And the below which sound potentially promising, but have rather..."terse " documentation.
Revise the row VBV algorithm (part 2)
author Anton Mitrofanov <BugMaster@narod.ru>Mon, 4 Jan 2016
committer Henrik Gramner <henrik@gramner.com>Sat, 16 Jan 2016
Should fix rare cases of VBV emergency mode activation caused by too much trust to the row predictors.
2-pass: Take into account possible frame reordering
author Anton Mitrofanov <BugMaster@narod.ru>Tue, 13 Oct 2015
committer Henrik Gramner <henrik@gramner.com>Sat, 16 Jan 2016
Can anyone shed some light on these changes and their potential impact?