Archive

Archive for September, 2011

x264 rev2085+616 patched build [ win, x86 & x64, tMod (& tMod+10bit/MixAQ/OreAQ), hacked bit depth conversion/dithering ]

30th September 2011, Friday Leave a comment

Latest updates:

– More audio formats accepted to be muxed in mkv using lsmash.
– Fix help information of AVC profiles, i.e., adding available “high422” and “high444” info, and hide unavailable “baseline”, “main” and “high” in 10 bit builds.

Other updates in rev2085’s patch version:

– Now in this version lavf/ffms demuxers can return color range flags of source clip, and send those flags to x264. You can still override the flags using –fullrange on/off.
– aq-mode 3 updated.
– 10bit version of OreAQ available.

Other minor changes won’t be mentioned. Download the patches below if details needed.

——– 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.

astrataro@gmail.com

——————–

Use win32thread and fprofiled:

plain-core/tMod/tMod-10bit/tMod+MixAQ/tMod+OreAQ/tMod+OreAQ-10bit:
x264_rev2085+616_tMod.7z

Other mirrors: MediaFireMegaUploadHotFileSkyDrive

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

Patches:
–—––—–Download(L-Smash not included): patches-rev2085-v2.7z
00-L-Smash(including qtaac in x86 build);
01-Fix help info of AVC profiles;(new!!)
02-Film Grain Optimization;
03-Fade Compensation;
04-Remove stats before renaming;
05-No opts;
06-Demuxer Thread;
07-Auto VBV Settings;
08-Avi output;
09-Filter: hqdn3d/pad/vflip/yadif;
10-Logger;
11-Encode Time;
12-Force level;
13-Cosmetic;
14-BugMaster’s new aq-mode 3;
15-Detect color range in lavf/ffms demuxer;(new!!)
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)

Compiler:
mingw-gcc 4.6.1

Libpack info:
libav: git-f5e717f/r30149
ffms2: svn-r572
lame 3.98.4
opencore-amr: git-08d6986/r178
vo-aacenc: git-075d122/r59
vo-amrwbenc: git-b7fcee9/r38
faac 1.28
qtsdk 7.3

Fix Help Info of Profile diff:
x264-Fix_help_info_of_profile.diff
MixAQ’s diff(AQDebug removed, also included in the patch package above):
MixAQ-core-Taro.diff
OreAQ’s diff(AQDebug removed, also included in the patch package above):
OreAQ-core-Taro.diff

Categories: encode, x264, x264-bin

avs4x264mod ( support non 8-bit avs input & customized x264_64 path )

29th September 2011, Thursday Leave a comment

Piping faked 16-bit avs output ( MSB and LSB field interleaved clip ) to x264_64.exe using original avs4x264 results in wrong resolution and video. So I modified it to behave in a correct way.

Download links ( source codes included) :

MediaFire: avs4x264mod.7z
Mirror: avs4x264mod.7z

Modifications:
— When x264’s parameter “input-depth” is set and is not equal to 8, divide “width” by 2. This make faked 16-bit avs output, i.e., MSB and LSB field interleaved clip, be treated correctly by x264. If “input-depth” is not defined or equals to 8, avs4x264mod acts in the same way as original avs4x264.
— Print full command-line piped to x264_64.exe to screen, prefixed by “avs4x264 [info]:”.
— Make x264_64.exe path changeable. The path of x264 binary can be set by –x264-binary “x264_path”. If custome path is not set, default path “x264_64.exe” will be used. Example: avs4x264mod.exe –x264-binary “C:\x264_64-abc.exe” -o out.264 in.avs

Categories: avs4x26x, encode, x264

x264 rev2085+607 patched build [ win, x86 & x64, tMod (& tMod+10bit/MixAQ/OreAQ), hacked bit depth conversion/dithering ]

23rd September 2011, Friday Leave a comment

Built last night but I was unable to upload the build. 😛

-Now in this version lavf/ffms demuxers can return color range flags of source clip, and send those flags to x264. You can still override the flags using –fullrange on/off.

-aq-mode 3 updated.

-10bit version of OreAQ available.

Other minor changes won’t be mentioned. Download the patches below if details needed.

——– 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.

astrataro@gmail.com

——————–

Use win32thread and fprofiled:

plain-core/tMod/tMod-10bit/tMod+MixAQ/tMod+OreAQ/tMod+OreAQ-10bit:
x264_rev2085+607_tMod.7z

Other mirrors: MediaFire, MegaUpload, HotFile, SkyDrive

My other tools list ( including some of the x264 builds ) : MediaFire, nmm-hd

Patches:
–—––—–Download(L-Smash not included): patches-rev2085.7z
01-L-Smash(including qtaac in x86 build);
02-Film Grain Optimization;
03-Fade Compensation;
04-Remove stats before renaming;
05-No opts;
06-Demuxer Thread;
07-Auto VBV Settings;
08-Avi output;
09-Filter: hqdn3d/pad/vflip/yadif;
10-Logger;
11-Encode Time;
12-Force level;
13-Cosmetic;
14-BugMaster’s new aq-mode 3;
15-Detect color range in lavf/ffms demuxer;(new!!)
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)

Compiler:
mingw-gcc 4.6.1

Libpack info:
libav: git-git-05fc9e4/r30030
ffms2: svn-r561
lame 3.98.4
opencore-amr: git-08d6986/r178
vo-aacenc: git-2b895f0/r58
vo-amrwbenc: git-b7fcee9/r38
faac 1.28
qtsdk 7.3

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

Categories: encode, x264, x264-bin