Home > encode, x264, x264-bin > x264 rev2192+664 tMod ( Auto VBV supports “auto_high422″/”auto_high444” )

x264 rev2192+664 tMod ( Auto VBV supports “auto_high422″/”auto_high444” )

8th April 2012, Sunday Leave a comment Go to comments

Sources on GitHub: https://github.com/astrataro/x264_tMod.

Use win32thread and fprofiled:

x264_rev2192+664_tMod.7z : NMMGitHubMediaFire
x264_rev2192+664_tMod-Special_offer.7z : NMMGitHubMediaFire

Special offer has only tMod+MixAQ-8bit and tMod-10bit with 4:2:0 chroma subsampling, no interlaced/audio/lavf/swscale/ffms support, smaller in size and might be faster in speed.

Latest updates:
– Updated to x264-devel for some bug fixes, such as “Fix disabling of mbtree when using 2pass encoding and zones”, which seems annoys many encoders, and now supports Level 5.2 according to latest superseded ITU standard.
– Updated “Auto VBV Settings” patch, it allows “auto_high422″/”auto_high444” now.

Also add support for “high10″/”high422″/”high444p” and Level 5.2 in TAEC.py / avc_refclac.py

—– How to load subtitles internally –—
These builds ported subtitles video-filter from direct264, and are able to render subtitles internally.
To render subtitles in this way, demuxer must be libav/ffms. Raw/avs demuxer is not supported for now. And VSFilter.dll(for 32-bit builds) or VSFilter64.dll(for 64-bit builds) must be placed together with the x264 binary or in the system path. Do NOT change filenames of them.
Rendering multiple subtitles is possible. Now you can render at most 16 subtitles simultaneously by calling –sub for each subtitles. Note that the later calling of –sub overlays the subtitles after previous calling of –sub, so if several subtitles are in the same position, the last one should overlays on all those rendered before.
The VSFilters are modified to add custom csri API. Patches can be found in svn of direct264 project. Therefore do NOT replace them with other builds. BT.709/BT.601 is auto detected according to video resolution. For HD videos BT.709 is used and for SD videos BT.601 is used.
Both 8-bit and 10-bit builds can use subtitles rendering, but rendering always takes place in 8-bit colorspaces.
The commandline example to render subtitles:
x264_32_tMod-8bit-420.exe --sub "subtitles-1.ass" --sub "subtitles-2.ass" --sub "subtitles-3.ass" --video-filter subtitles[/Other video filters] [Other x264 options] --output "output.mp4" "input.mp4"

–—––—– Download(L-Smash not included): patches-rev2192.7z: NMMMediaFire
00:L-Smash(including audio encoding);
01:More detailed version head
02:Add back “touhou” tune
03:Film Grain Optimization
04:Fade Compensation
05:Remove stats before renaming
06:Add a parameter to set level of writing options in User Data Unregistered SEI
07:Utilize internal threading in lavf/ffms
08:Auto VBV settings (Update!!)
09:AVI output
10:filters hqdn3d pad vflip yadif patch
11:Log file
12:Encoding time
13:Level force
14:Profile force
16:New experimental AQ mode (modification of Auto-variance AQ)
17:Print video info with lavf/ffms demuxer
18:lto & Ofast
19:AviSynth 16bit hack
20:Skip bit depth filter when possible
21:Video filter: subtitles
22:Detect color matrix with lavf/ffms demuxer
23:Fix AviSynth color space converting matrix
24:High-precision fps & estimated total size
25:More detailed “zones” help
26:Unofficial --device
27-1:MixAQ-core;(only in tMod+MixAQ version, remove AQDebug)
27-2:OreAQ-core.(only in tMod+OreAQ version, remove AQDebug)

mingw-gcc 4.7.0

Libpack info
ffms svn-r673
VSFilter svn-r3698 (MPC-HC)
lame 3.99-5
libvorbis-aotuv_b6.03 (libvorbis-1.3.3)
opencore-amr 0.1.3 git-r189(958395d)
vo-aacenc v0.1.2-6 git-r85(c6bad70)
vo-amrwbenc v0.1.2-3 git-r52(6ffcea9)
faac 1.28
qtsdk 7.3

My other tools list ( including some of the x264 builds ) : MediaFire

Categories: encode, x264, x264-bin
  1. Mark
    10th April 2012, Tuesday at 03,38pm UTC

    Thanks 🙂
    Is there any advantage of level 5.2?

    • 11th April 2012, Wednesday at 01,03am UTC

      No. L5.2 only increases maximum macroblock processing rate, which allows higher resolution or/and higher fps, such as 3840×2160@60fps.

  2. UI
    11th April 2012, Wednesday at 05,28am UTC

    off topic question here 🙂
    Does vp8 algorithm will merge into x264 later because I see dark shikari & other developer was working at that area in dark shikari github’s repo

    • 11th April 2012, Wednesday at 12,37pm UTC

      Not sure. Both xvp8 and x262 use x264’s framework and share some of x264’s mature features. But I haven’t looked into them to see if there’s anything from xvp8/x262 which may be useful for x264….

  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: