Home > encode, x264, x264-bin > x264 rev2106+629 tMod v2

x264 rev2106+629 tMod v2

3rd November 2011, Thursday Leave a comment Go to comments

Latest updates:
– Fix bugs in decoding lossless 4:2:2/4:4:4 AVC streams via lavf/ffms;
– Remove –no-opts and use –opts <integer> instead. –opts 2 (default) generates x264 info and options as the official builds; –opts 1 writes only x264 info as formal –no-opts; and –opts 0 writes nothing in SEI.

——– 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 of RGB and Y plane of YUV. Till now neither x264 nor swscale has a correct chroma upscaling algorithm for full range sources, and I didn’t make one. Anyway, the converting algorithm of x264 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, which is still not reliable for YUV sources, so it is recommanded to use your own reliable approaches to convert those sources by yourself before passing them to my x264 builds; if used without “–fullrange on”, the conversion will be done by shifting according to the standard, and the dithering algorithm is fixed as well, so that the result should be absolutely right.



Use win32thread and fprofiled:

x264_rev2106+629_tMod-v2.7zMediaFire Mirror

My other tools list ( including some of the x264 builds ) : MediaFirenmm-hd

–—––—–Download(L-Smash not included): patches-rev2106-v3.7z
00-L-Smash(including qtaac in x86 build);
01-Re-enable –tune “touhou” in fullhelp;
02-Film Grain Optimization;
03-Fade Compensation;
04-Remove stats before renaming;
05-Set level of writing options in SEI;(new!!)
06-Demuxer Thread;
07-Auto VBV Settings;
08-Avi output;
09-Filter: hqdn3d/pad/vflip/yadif;
11-Encode Time;
12-Force level;
14-BugMaster’s new aq-mode 3;
15-Detect color range in lavf/ffms demuxer;
16-Fix bit depth conversion and dithering;
17-Print video info lavf ffms;
18-Enable lto Ofast;
19-AviSynth 16bit hack;
20-Skip bit depth filter;
21-1-MixAQ-core(only in tMod+MixAQ version, remove AQDebug)
21-2-OreAQ-core(only in tMod+OreAQ version, remove AQDebug)

mingw-gcc 4.6.1

Libpack info:
libav r30764 git-594b54b
ffms svn-r582
lame 3.99
libvorbis-aotuv_b6.03 (libvorbis-1.3.2)
opencore-amr-0.1.2 r178 git-08d6986
vo-aacenc-0.1.1 r59 git-075d122
vo-amrwbenc-0.1.1 r38 git-b7fcee9
aacplus 2.0.2
faac 1.28
qtsdk 7.3

MixAQ’s diff(AQDebug removed, also included in the patch package above):
OreAQ’s diff(AQDebug removed, also included in the patch package above):

Categories: encode, x264, x264-bin
  1. Mark
    9th November 2011, Wednesday at 01,49am UTC


  2. Kouta84
    12th November 2011, Saturday at 03,07pm UTC

    I don’t know well, but there are some improvements to use mixaq or oreaq instead of aq3?

    • 12th November 2011, Saturday at 03,23pm UTC

      The algorithms are different and the quality depends on the source and the parameters you used. Also you can use aq-mode=3 and Haali’s AQ simultaneously with MixAQ builds.

  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: