x265 HEVC Encoder

[LigH]

*sigh* How much energy for development is wasted in ego wars instead.

[troica]

Hello guys can anyone help me? I'm trying to code in visual studios wherein I want to produce a text file that reports the changes after encoding a YUV video. The text file consists of the frame #, slice #, CTU# etc. Thank you for any help.

[LigH]

What kind of changes do you mean? Differences according to metrics like PSNR or SSIM? Absolute differences per YUV channel?

x265 can already produce a CSV log file per frame.

   --csv <filename>              Comma separated log file, if csv-log-level > 0 frame level statistics, else one line per run
   --csv-log-level <integer>     Level of csv logging, if csv-log-level > 0 frame level statistics, else one line per run: 0-2

[birdie]

Ryzen supports AVX2, so let's hope for the best and expect the worst. :-)

[LigH]

You probably mean it similar to the support of SSE3 by Phenom-II, which is considered too slow by x264/x265 to be enabled?

[NikosD]

The developers of x265 can tell us for sure if and how FMA3 is used.

Because nobody here disagrees that integer AVX2 is used a lot by x265.

Usually a floating point division or some other single floating point instruction could be used in projects like x264 or x265 but nothing more than that regarding floating point support.

SSEx is very fast in RyZen, it's as fast as Kabylake.

AVX/AVX2 is supported, but it's about half speed.

[Ma]

Originally Posted by NikosD

The developers of x265 can tell us for sure if and how FMA3 is used.

FMA3 (nor FMA4) is not used in x265. It could be used for example in
https://bitbucket.org/multicoreware/...mc-a2.asm-1120
but the speed up is only a few CPU cycles in function that is not important for whole encoding time. It is OK to use MUL and ADD instead of one FMA.

[troica]

Originally Posted by LigH

What kind of changes do you mean? Differences according to metrics like PSNR or SSIM? Absolute differences per YUV channel?

x265 can already produce a CSV log file per frame.

   --csv <filename>              Comma separated log file, if csv-log-level > 0 frame level statistics, else one line per run
   --csv-log-level <integer>     Level of csv logging, if csv-log-level > 0 frame level statistics, else one line per run: 0-2

I mean like what kind of config you have before and after encoding..

If I encoded using 10 frames it will show 10 frames etc and record the quantization parameters per CTU etc

[LigH]

So you are looking for an API that will trigger even more detailed reports than the CSV log with level 2, even a per-CTU log... I believe there is none yet, only per-file and per-frame logs (see: x265-extras.h).

[troica]

Originally Posted by LigH

So you are looking for an API that will trigger even more detailed reports than the CSV log with level 2, even a per-CTU log... I believe there is none yet, only per-file and per-frame logs (see: x265-extras.h).

If so, how do access thex265-extras? Sorry for being a noob at encoders.

And is there anything I can code in visual studios to report the per CTU log?

[LigH]

I assume you already used Mercurial to clone the whole x265 source repository? Apart from that, you can look at the source here:

https://bitbucket.org/multicoreware/x265/src / source / x265-extras.h (as well as x265-extras.cpp)

[troica]

How do you access the source files?

[birdie]

Intel got scared: http://wccftech.com/intel-amd-price-...en-processors/

Hopefully you haven't bought any Intel CPUs lately 'cause it's time to kick yourself in the balls.

Lovely!

[LigH]

@ troica:

Always read the documentation first...

[troica]

Okay sorry. I really don't know how to start using HEVC and how to simulate a wireless video transmission between visual studios and the ns3 program. It's where my thesis will start so sorry if I got a lt oof questions. Btw, is this x265 the HM model?

[Barough]

x265 v2.3+9-820f4327ddac (MSYS/MinGW, GCC 6.3.0, 32 & 64bit 8/10/12bit multilib EXEs)

x265 [info]: HEVC encoder version 2.3+9-820f4327ddac
x265 [info]: build info [Windows][GCC 6.3.0][32 bit/64 bit] 8bit+10bit+12bit
x265 [info]: using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX AVX2 FMA3 LZCNT BMI2

https://bitbucket.org/multicoreware/x265/commits/branch/default

[Sagittaire]

Originally Posted by NikosD

I was told by an Intel fanboy and RyZen 7 reviewer that you need a Core i7 7700K@4.8GHz to catch the performance of RyZen 7@4.0GHz at x265 2nd pass or you could see the same thing reversed.

Will see...

No, Rysen 7 1800X 8C/16T at 500$ will be certainely on par with i7 6900K 8C/16T at 1000$ for x264/x265 encoding. You must use certainely something like O/C at 6 Ghz (nitrogen!!!) with i7 7700K (400$) or even more to have the same performance than R7 1700 (350$) at stock frequency.

[NikosD]

x264 is a lot different than x265 due to AVX2 optimizations.

Yes, I agree that using x264 RyZen is going to have a party.

But x265 has a lot of AVX2 optimizations and it's not possible for RyZen 7 to catch the performance of an Intel 8C/16T.

[Motenai Yoda]

Originally Posted by Sagittaire

No, Rysen 7 1800X 8C/16T at 500$ will be certainely on par with i7 6900K 8C/16T at 1000$ for x264/x265 encoding. You must use certainely something like O/C at 6 Ghz (nitrogen!!!) with i7 7700K (400$) or even more to have the same performance than R7 1700 (350$) at stock frequency.

I'd not be so enthusiast about Ryzen, as the only public comparison is still the amd charts one, and as bulldozer and its derivates are nothing better than intel's ones.

Also 7700k cost now about 340€ (maybe 320/300€ with the 10/15$ prices cut), sure not 400$, and 1700x is (yep) an esacore, but with castrated avx2 and few/no compiler optimizations.

6900k is the actual not plus ultra for a consumer pc so it's baldly overvalued.

[Sagittaire]

Originally Posted by Motenai Yoda

I'd not be so enthusiast about Ryzen, as the only public comparison is still the amd charts one, and as bulldozer and its derivates are nothing better than intel's ones.

Also 7700k cost now about 340€ (maybe 320/300€ with the 10/15$ prices cut), sure not 400$, and 1700x is (yep) an esacore, but with castrated avx2 and few/no compiler optimizations.

6900k is the actual not plus ultra for a consumer pc so it's baldly overvalued.

There are here in France exclusive test on "CPC hardware magazine" since one month. The test CPU model is 3.15/3.3/3.5 Ghz 8C/16T sample (will be like R7 1700).

Overall benchmark for x264 HB encodaging 2K, x265 HB encodaging 4K, WPrime, PovRay, Blender, 3DMax 2015/Mental Ray, Coronna Benchmark

i7 6900K: 193.4
R7 3.15/3.3/3.5 Ghz: 168.7
i7 6800K: 152.5
i7 6700K: 137.3
i7 4790K: 127.7
FX-8370: 105.2
i5 6600K: 100.0

Make scaling for R7 1800X at 3.6/3.8/4.0 Ghz by yourself ... ;-)