x265 HEVC Encoder

[filler56789]

x265.exe v. 2.1+66

http://forum.videohelp.com/threads/3...=1#post2469269

[Barough]

x265 v2.1+66-b2d360143d96 (MSYS/MinGW, GCC 6.2.0, 32 & 64bit 8/10/12bit multilib EXEs)

[filler56789]

x265 v. 2.1+69

http://forum.videohelp.com/threads/3...=1#post2469617

[LigH]

x265 2.1+69-c97c64ab8b8e

As mentioned above: SEA motion search implemented, several fixes and optimizations in addition.

[Majorlag]

x265 is coming together rather well. I have finally decided to switch over from x264,

Only one thing is still bothering me, and it only started recently. x265_2.1+59 seemed to be a great improvement over previous builds in my encodes, but in +59 and +69, the encoding settings show stats-file= location. x265_2.1+36 and below did not seem to show as much detail. I know about the --no-info, but was wondering if there is an option to turn off only stats-file= information from the encodes.

Keep up the Great work.

[LoRd_MuldeR]

Originally Posted by Majorlag

I know about the --no-info, but was wondering if there is an option to turn off only stats-file= information from the encodes.

Judging from the code, doesn't look so:

char *x265_param2string(x265_param* p, int padx, int pady)
{
    [...]
    if (p->rc.rateControlMode == X265_RC_ABR || p->rc.rateControlMode == X265_RC_CRF)
    {
        [...]
        if (p->rc.bStatRead || p->rc.bStatWrite)
            s += sprintf(s, " stats-file=%s", p->rc.statFileName);

(If RC mode is either ABR or CRF and if a stats file is read or written, then the stats file location will be logged)

[aymanalz]

What is the general opinion on SAO now? Does it still blur too much, or cause much loss of detail? Is it generally recommended to be used in most cases?

[gnol009]

Hello guys. Here my cmd line settings:

D:\Encode\x264\avs4x26x --x26x-binary x265.exe 2.avs --bitrate 9000 --pass 1 --stats ".stats" --bframes 8 --aq-strength 0.9 --b-intra --no-amp --no-strong-intra-smoothing --no-sao -o NUL 2> pass12.log

D:\Encode\x264\avs4x26x --x26x-binary x265.exe 2.avs --bitrate 9000 --pass 2 --stats ".stats" --preset slower --ctu 32 --no-amp --aq-mode 3 --deblock -3:-3 --cbqpoffs -3 --crqpoffs -3 --aq-strength 0.9 --rd 4 --psy-rd 4.0 --psy-rdoq 10.0 --rc-lookahead 80 --qcomp 0.65 --no-strong-intra-smoothing --no-sao --ipratio 1.3 --pbratio 1.2 -o "T3.hevc" 2> pass22.log

And here media info encode setting:

x265 2.1+69-c97c64ab8b8e:[Windows][GCC 6.2.0][64 bit] 8bit
Encoding settings : cpuid=1050111 / frame-threads=3 / numa-pools=8 / wpp / no-pmode / no-pme / no-psnr / no-ssim / log-level=2 / input-csp=1 / input-res=1920x800 / interlace=0 / total-frames=2129 / level-idc=0 / high-tier=1 / uhd-bd=0 / ref=4 / no-allow-non-conformance / no-repeat-headers / annexb / no-aud / no-hrd / info / hash=0 / no-temporal-layers / open-gop / min-keyint=23 / keyint=250 / bframes=8 / b-adapt=2 / b-pyramid / bframe-bias=35 / rc-lookahead=20 / lookahead-slices=4 / scenecut=40 / no-intra-refresh / ctu=64 / min-cu-size=8 / rect / no-amp / max-tu-size=32 / tu-inter-depth=1 / tu-intra-depth=1 / limit-tu=0 / rdoq-level=2 / signhide / no-tskip / nr-intra=0 / nr-inter=0 / no-constrained-intra / no-strong-intra-smoothing / max-merge=3 / limit-refs=3 / limit-modes / me=2 / subme=3 / merange=57 / temporal-mvp / weightp / weightb / no-analyze-src-pics / deblock=-3:-3 / no-sao / no-sao-non-deblock / rd=5 / no-early-skip / rskip / no-fast-intra / no-tskip-fast / no-cu-lossless / no-b-intra / rdpenalty=0 / psy-rd=3.00 / psy-rdoq=10.00 / no-rd-refine / analysis-mode=0 / no-lossless / cbqpoffs=-3 / crqpoffs=-3 / rc=abr / bitrate=9000 / qcomp=0.65 / qpstep=4 / stats-write=0 / stats-read=2 / stats-file=.stats / cplxblur=20.0 / qblur=0.5 / ipratio=1.35 / pbratio=1.25 / aq-mode=3 / aq-strength=0.90 / cutree / zone-count=0 / no-strict-cbr / qg-size=32 / no-rc-grain / qpmax=69 / qpmin=0 / sar=0 / overscan=0 / videoformat=5 / range=0 / colorprim=2 / transfer=2 / colormatrix=2 / chromaloc=0 / display-window=0 / max-cll=0,0 / min-luma=0 / max-luma=255 / log2-max-poc-lsb=8 / vui-timing-info / vui-hrd-info / slices=1 / opt-qp-pps / opt-ref-list-length-pps / no-multi-pass-opt-rps / scenecut-bias=0.05

Does anyone know why media info show rc=abr?

[Boulder]

Because you are doing a 2-pass encode which means ABR.

[Ma]

Originally Posted by Majorlag

[...] if there is an option to turn off only stats-file= information from the encodes.

Like LoRd_MuldeR wrote, there isn't, but all OpenSource projects have one super option -- you can change what you want.

If you don't want to modify source code by yourself, you can download modified and compiled version: http://www.msystem.waw.pl/x265/x265-...34-no-stats.7z

Inside the archive there is diff file from original sources and Windows binaries compiled by VS 2017 (and GCC 5/6/7 with names x265gccN.exe).

[sneaker_ger]

I don't think it is a good idea. It has the potential to leak personal information, e.g. if your Windows user name equals your real name and the stats file is somewhere in your user directory. Some GUIs might have their working directory there so you wouldn't even notice. I also wonder if it could lead to problems with long path names. I vaguely remember a program crashing when the custom SEI became too long.

Question:
Why stats-read=2? Is there a "1"?

[Ma]

Originally Posted by sneaker_ger

Why stats-read=2? Is there a "1"?

No, it is 0 or 2, see source:

OPT("pass")
{
    int pass = x265_clip3(0, 3, atoi(value));
    p->rc.bStatWrite = pass & 1;
    p->rc.bStatRead = pass & 2;
}

For pass 2 and pass 3 it is '2', for pass 1 and no pass it is '0'.

Originally Posted by Majorlag

x265 is coming together rather well. I have finally decided to switch over from x264,

Only one thing is still bothering me, and it only started recently. x265_2.1+59 seemed to be a great improvement over previous builds in my encodes, but in +59 and +69, the encoding settings show stats-file= location. x265_2.1+36 and below did not seem to show as much detail. I know about the --no-info, but was wondering if there is an option to turn off only stats-file= information from the encodes.

Keep up the Great work.

Thanks for your feedback. I agree that we shouldn't write the stats file info... it's a potential privacy issue, and it isn't really useful a part of the info. I'll ask the developer who made the last patch to revert this.

Tom

Originally Posted by gnol009

Hello guys. Here my cmd line settings:

D:\Encode\x264\avs4x26x --x26x-binary x265.exe 2.avs --bitrate 9000 --pass 1 --stats ".stats" --bframes 8 --aq-strength 0.9 --b-intra --no-amp --no-strong-intra-smoothing --no-sao -o NUL 2> pass12.log

D:\Encode\x264\avs4x26x --x26x-binary x265.exe 2.avs --bitrate 9000 --pass 2 --stats ".stats" --preset slower --ctu 32 --no-amp --aq-mode 3 --deblock -3:-3 --cbqpoffs -3 --crqpoffs -3 --aq-strength 0.9 --rd 4 --psy-rd 4.0 --psy-rdoq 10.0 --rc-lookahead 80 --qcomp 0.65 --no-strong-intra-smoothing --no-sao --ipratio 1.3 --pbratio 1.2 -o "T3.hevc" 2> pass22.log

And here media info encode setting:

x265 2.1+69-c97c64ab8b8e:[Windows][GCC 6.2.0][64 bit] 8bit
Encoding settings : cpuid=1050111 / frame-threads=3 / numa-pools=8 / wpp / no-pmode / no-pme / no-psnr / no-ssim / log-level=2 / input-csp=1 / input-res=1920x800 / interlace=0 / total-frames=2129 / level-idc=0 / high-tier=1 / uhd-bd=0 / ref=4 / no-allow-non-conformance / no-repeat-headers / annexb / no-aud / no-hrd / info / hash=0 / no-temporal-layers / open-gop / min-keyint=23 / keyint=250 / bframes=8 / b-adapt=2 / b-pyramid / bframe-bias=35 / rc-lookahead=20 / lookahead-slices=4 / scenecut=40 / no-intra-refresh / ctu=64 / min-cu-size=8 / rect / no-amp / max-tu-size=32 / tu-inter-depth=1 / tu-intra-depth=1 / limit-tu=0 / rdoq-level=2 / signhide / no-tskip / nr-intra=0 / nr-inter=0 / no-constrained-intra / no-strong-intra-smoothing / max-merge=3 / limit-refs=3 / limit-modes / me=2 / subme=3 / merange=57 / temporal-mvp / weightp / weightb / no-analyze-src-pics / deblock=-3:-3 / no-sao / no-sao-non-deblock / rd=5 / no-early-skip / rskip / no-fast-intra / no-tskip-fast / no-cu-lossless / no-b-intra / rdpenalty=0 / psy-rd=3.00 / psy-rdoq=10.00 / no-rd-refine / analysis-mode=0 / no-lossless / cbqpoffs=-3 / crqpoffs=-3 / rc=abr / bitrate=9000 / qcomp=0.65 / qpstep=4 / stats-write=0 / stats-read=2 / stats-file=.stats / cplxblur=20.0 / qblur=0.5 / ipratio=1.35 / pbratio=1.25 / aq-mode=3 / aq-strength=0.90 / cutree / zone-count=0 / no-strict-cbr / qg-size=32 / no-rc-grain / qpmax=69 / qpmin=0 / sar=0 / overscan=0 / videoformat=5 / range=0 / colorprim=2 / transfer=2 / colormatrix=2 / chromaloc=0 / display-window=0 / max-cll=0,0 / min-luma=0 / max-luma=255 / log2-max-poc-lsb=8 / vui-timing-info / vui-hrd-info / slices=1 / opt-qp-pps / opt-ref-list-length-pps / no-multi-pass-opt-rps / scenecut-bias=0.05

Does anyone know why media info show rc=abr?

When you use the --bitrate command, you're engaging x265's ABR (Average Bit Rate) rate control mode, as opposed to constant QP or CRF rate control, which are fundamentally different.

[Selur]

Btw. is it just me or are other users also experiencing problems when trying to multiplex x265 encoded content with mp4box ? (see: https://bitbucket.org/multicoreware/...ncompatibility)

[Jamaika]

Originally Posted by Selur

Btw. is it just me or are other users also experiencing problems when trying to multiplex x265 encoded content with mp4box ? (see: https://bitbucket.org/multicoreware/...ncompatibility)

Maybe high time to give yourself a peace of MP4Box.

[Ajvar]

Originally Posted by LigH

Knowing that SEA means "Successive Elimination Algorithm", I found some links to scientific papers. It appears to be parallelizable rather easily, having a tree structure.

Possible display: eSilicon Labs HEVC slide, images 79 and 93 of 159? Links to single images (with descriptions) are below the slide.

SEA is "lossless" searching method with "compression".
Exhaustive = 8x8 square = 64 searching points and 196 sp for 14x14.
SEA = 8+9+9 = 26 sp (27 if analize starting pixel in center) while fully covering same 14x14 square. Pretty easy to get once you look at page 79. 3 steps search: 4 pixel long, then 2, then 1.

[LigH]

So it is indeed quite similar to UMH: Progressive precision, narrowing down to the optimum in several passes.
__

P.S.:

I hope I understood them all good enough to display them correctly and comprehensibly... added to the thread Motion Search Method (sorry for necro, but there is the optimal place).

[NikosD]

Just a quick bench using latest StaxRip x64 v1.4.0.0 which has x265 v2.1+69 inside, this time in 10bit HEVC.

So, using the default settings of Medium preset on the same source I got these results:

Core i3-4170
494.20s (1.01 fps)

Core i5-2400
524.81s (0.95 fps)

A Haswell Core i3 at 3.7GHz with 8GB DDR3-1600MHz-CL9 which is a 2C/4T CPU (~2C + ~40%) is a little faster than a Sandybridge Core i5 at 3.2GHz (using Turbo) with 12GB DDR3-1333MHz-CL9 which is a 4C/4T CPU, both under the same OS (Win 10 x64 latest) using significantly less power consumption (35W vs 54W measured consuption).

Impressive.

Of course in a few months a new star will be born - AMD RyZen 8C/16T CPU - which according to the yesterday's Live Show using Handbrake, is a tad faster than Broadwell-E Core i7-6900K.

This is even more impressive when you see that RyZen has 95W TDP and the Core i7-6900K has 140W TDP.

[Magik Mark]

Does anyone knows which version of x265 is being used by adobe media encoder 2017?


Sent from my iPhone using Tapatalk