x264 rev2059+600 patched build [ win, x86 & x64, tMod & tMod+10bit/MixAQ/OreAQ), hacked bit depth conversion/dithering ]
Updating from 2057 to 2059 has nothing to do with performance or stability. They only fix wrong help info and add new configure parameters for compiling.
——– Attention on high bit depth usage ——–
Several days before madshi pointed out that x264’s internal low bit depth to high bit depth conversion and high bit depth to low bit depth dithering is incorrect. The present converting and dithering algorithms seem to work correctly on full range sources ( or not, I haven’t find any documents on the full range conversion ). But the converting algorithm is absolutely wrong on limited range sources, according to ITU-R 601/709’s standard, in which the conversion should be done by simply appending LSBs of zero to the source. The dithering algorithm may also causes overflow on limited range source. So I hacked on my tMod builds to solve this issue.
When the input and output bit depth are the same, no conversion or dithering will be apllied. Otherwise when used with “–fullrange on”, the conversion and dithering will be exactly the same with x264’s original algorithm; if used without “–fullrange on”, the conversion will be done by shifting according to the standard, and the dithering algorithm is fixed as well.
Use win32thread and fprofiled:
–—––—–Download（L-Smash not included）: patches-rev2059.7z
01-L-Smash（including qtaac in x86 build）;
02-Film Grain Optimization;
04-Remove stats before renaming;
07-Auto VBV Settings;
14-Print video info lavf ffms;
15-Enable lto Ofast;
16-AviSynth 16bit hack;
17-Skip bit depth filter;(!!new!!)
18-Fix bit depth conversion and dithering;(!!new!!)
19-BugMaster’s new aq-mode 3;
20-1-MixAQ-core（only in tMod+MixAQ version, remove AQDebug）
20-2-OreAQ-core（only in tMod+OreAQ version, remove AQDebug）