SmilingWolf I am maddo saientisto!



Join Date: Aug 2018 Posts: 103



Previous edition:

Whatever paragraph I don't repeat here can be assumed to be the same as in the aforementioned post



First of all: graphs! Click to enlarge

Y axis: chosen metric

X axis: bits per pixel



720p:





1080p:





BD rates for 720p:

Code: x264 -> rav1e (yeah you read that right!) RATE (%) DSNR (dB) MSSSIM -0.736889 0.0375593 PSNRHVS -5.5274 0.375081 rav1e -> x265 RATE (%) DSNR (dB) MSSSIM -26.5291 1.29942 PSNRHVS -27.1134 1.70509 x265 -> libaom RATE (%) DSNR (dB) MSSSIM -18.9088 0.7852 PSNRHVS -15.3123 0.761791

Code: x264 -> rav1e (yeah you read that right again!) RATE (%) DSNR (dB) MSSSIM -4.92009 0.235151 PSNRHVS -7.23088 0.473125 rav1e -> x265 RATE (%) DSNR (dB) MSSSIM -26.7063 1.16103 PSNRHVS -28.0007 1.53902 x265 -> libaom RATE (%) DSNR (dB) MSSSIM -26.486 0.938124 PSNRHVS -21.7431 0.905916

x264 157-2935-545de2f

x265 2.9-4-471726d3a046

rav1e 0.1.0-702-ab4d23e2

libaom 1.0.0-908-g3a607f7b0



Cmdlines:

x264 --preset veryslow --tune ssim --crf 16 -o test.x264.crf16.264 orig.i420.y4m

x265 --preset veryslow --tune ssim --crf 16 -o test.x265.crf16.hevc orig.i420.y4m

rav1e --low_latency false -o test.rav1e.cq80.ivf --quantizer 80 -s 2 --tune psnr orig.i420.y4m

aomenc --frame-parallel=0 --tile-columns=3 --auto-alt-ref=1 --cpu-used=4 --tune=psnr --passes=2 --threads=2 --end-usage=q --cq-level=20 --test-decode=fatal -o test.av1.cq20.webm orig.i420.y4m



Notes:

So as you can see, the rav1e and aomenc cmdlines have been slightly adjusted to take advantage of the bugfixes and updates from the last months.

In particular, rav1e has been gifted by Frank Bossen the ability to create a B-pyramid, which almost single handedly decreed rav1e's advantage over x264.

A word of warning on this last point: it's still kind of a mixed bag. In very flat, static scenes like PresageFlowerWalk x264 still rules by quite a margin, while rav1e takes the crown in clips like F.Y.C and PresageFlowerFight

Code: F.Y.C, x264 -> rav1e: RATE (%) DSNR (dB) MSSSIM -18.451 1.01281 PSNRHVS -25.7463 2.03419 PresageFlowerFight, x264 -> rav1e: RATE (%) DSNR (dB) MSSSIM -31.4953 1.80761 PSNRHVS -31.0827 2.27546 PresageFlowerWalk, x264 -> rav1e: RATE (%) DSNR (dB) MSSSIM 66.2264 -1.70084 PSNRHVS 70.8208 -2.28853



Considerations about times with libaom:

I'm using my desktop PC to run all the encodes. It is also my main study/work PC, so the times can come quite off. Plus, I run multiple encodes in parallel, which further messes up timings.

HOWEVER, between annoying bugs and a lot of stuff, the first report did cost me nearly a week of time (this includes having to re-run some encodes because sh*t happened) ONLY to encode with libaom.

Taking advantage of the recent bugfixes and improvements I have been able to rework my workflow and bring down that time to a couple days only, WITHOUT having to touch the --cpu-used parameter and no night time encoding.

All in all, I am pretty satisfied.



This concludes my (bi-monthly?) report.

As always, I'm open to any kind of feedback to improve my comparisons and my encodes. Status report!Previous edition: http://forum.doom9.org/showthread.ph...49#post1852449 Whatever paragraph I don't repeat here can be assumed to be the same as in the aforementioned postFirst of all: graphs! Click to enlargeY axis: chosen metricX axis: bits per pixel720p:1080p:BD rates for 720p:BD rates for 1080p:Encoders:x264 157-2935-545de2fx265 2.9-4-471726d3a046rav1e 0.1.0-702-ab4d23e2libaom 1.0.0-908-g3a607f7b0Cmdlines:x264 --preset veryslow --tune ssim --crf 16 -o test.x264.crf16.264 orig.i420.y4mx265 --preset veryslow --tune ssim --crf 16 -o test.x265.crf16.hevc orig.i420.y4mrav1e --low_latency false -o test.rav1e.cq80.ivf --quantizer 80 -s 2 --tune psnr orig.i420.y4maomenc --frame-parallel=0 --tile-columns=3 --auto-alt-ref=1 --cpu-used=4 --tune=psnr --passes=2 --threads=2 --end-usage=q --cq-level=20 --test-decode=fatal -o test.av1.cq20.webm orig.i420.y4mNotes:So as you can see, the rav1e and aomenc cmdlines have been slightly adjusted to take advantage of the bugfixes and updates from the last months.In particular, rav1e has been gifted by Frank Bossen the ability to create a B-pyramid, which almost single handedly decreed rav1e's advantage over x264.A word of warning on this last point: it's still kind of a mixed bag. In very flat, static scenes like PresageFlowerWalk x264 still rules by quite a margin, while rav1e takes the crown in clips like F.Y.C and PresageFlowerFight(as always, a negative BD rate means improvement, positive means regression)Considerations about times with libaom:I'm using my desktop PC to run all the encodes. It is also my main study/work PC, so the times can come quite off. Plus, I run multiple encodes in parallel, which further messes up timings.HOWEVER, between annoying bugs and a lot of stuff, the first report did cost me nearly a week of time (this includes having to re-run some encodes because sh*t happened) ONLY to encode with libaom.Taking advantage of the recent bugfixes and improvements I have been able to rework my workflow and bring down that time to a couple days only, WITHOUT having to touch the --cpu-used parameter and no night time encoding.All in all, I am pretty satisfied.This concludes my (bi-monthly?) report.As always, I'm open to any kind of feedback to improve my comparisons and my encodes. Last edited by SmilingWolf; 15th November 2018 at 00:34 .