Welcome to Doom9's Forum, THE in-place to be for everyone interested in DVD conversion. Before you start posting please read the forum rules. By posting to this forum you agree to abide by the rules. |
12th November 2018, 23:16 | #1223 | Link | |
Registered User
Join Date: Jul 2018
Posts: 80
|
SSE3-optimised av1_nn_predict
https://aomedia.googlesource.com/aom...6f313f27b1c501 Quote:
|
|
12th November 2018, 23:23 | #1224 | Link |
Registered User
Join Date: Nov 2009
Location: Northeast Ohio
Posts: 447
|
...but this is exactly what I alluded to?
Athlon 64 CPUs are available on socket 754, 939, and AM2; 754 and 939 used DDR1 memory while AM2 used DDR2, and all AM2 CPUs support SSE3. (there are some socket 754 and 939 CPUs that support SSE3, though it's kind of hit and miss). Phenom for reference requires at least DDR2. |
13th November 2018, 19:26 | #1226 | Link |
Registered User
Join Date: Dec 2008
Posts: 1,970
|
Intel i5-3570k (SSE4.1, SSE4.2, AVX), Windows 7 Sp1 x64.
__________________
MPC-BE 1.7.0 and Nightly builds | VideoRenderer | ImageSource | ScriptSource | BassAudioSource |
15th November 2018, 00:29 | #1227 | Link |
I am maddo saientisto!
Join Date: Aug 2018
Posts: 95
|
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 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. Last edited by SmilingWolf; 15th November 2018 at 00:34. |
16th November 2018, 19:53 | #1228 | Link |
Moderator
Join Date: Jan 2006
Location: Portland, OR
Posts: 4,770
|
So, what's everyone's favorite AV1 decoder app on Windows? Chrome looks to be not converting from video to PC range correctly (blacks are washed out, contrast is low, etcetera). Is there a nightly of something that does AV! correctly for apples-apples?
|
16th November 2018, 22:45 | #1229 | Link | |
I am maddo saientisto!
Join Date: Aug 2018
Posts: 95
|
Quote:
In alternative, ffplay for quick stuff when I already have a bunch of command prompts open in the right path. Last edited by SmilingWolf; 17th November 2018 at 12:30. |
|
16th November 2018, 23:27 | #1230 | Link |
German doom9/Gleitz SuMo
Join Date: Oct 2001
Location: Germany, rural Altmark
Posts: 6,783
|
I use almost only MPC-HC. Which uses LAV Filters with a direct API. It was able to play AV1 clips from the YouTube beta playlist and some tiny own encodes (I don't have powerful CPU's available). So, only a limited experience, yet, but it appears to work.
|
18th November 2018, 12:40 | #1231 | Link |
I am maddo saientisto!
Join Date: Aug 2018
Posts: 95
|
32/64bits binaries (GCC 9.0):
av1-1.0.0-941-gd2a592e1c: https://mega.nz/#!F5Am2KyK!9aQ6_7mM2...6_OaZahvKCHPWQ |
19th November 2018, 10:51 | #1232 | Link |
Registered User
Join Date: Jan 2007
Posts: 729
|
You could get the same results by splitting manually into X parts end encode them separately at once. I'm not sure how much does libvpx/libaom count with that. It works great with x264 and x265 (using raw output at least).
|
19th November 2018, 10:58 | #1233 | Link | |
Registered User
Join Date: Jan 2007
Posts: 729
|
Quote:
You probably mean SSSE3 (SSS instead of SS) aka "Suplemental SSE3" which is a confusing and dumb name. Probably should have been SSE4 but got renamed for marketing reasons. Or SSE3 was not supposed to be SSE3 originally. SSSE3 is very useful for encoding and decoding, but only comes on Core 2 chips, and Bobcat/Bulldozer and later cores from AMD. K10 and K8 end at the not-so-important SSE3. (Note that x265 actually needs SSSE3 + SSE4 to be useful, you are barred from most of assembly optimization if you only have SSSE3, like with 65nm Core 2s or pre-Sandy Bridge Pentium/Celeron). Last edited by mandarinka; 19th November 2018 at 11:01. |
|
19th November 2018, 13:09 | #1234 | Link |
German doom9/Gleitz SuMo
Join Date: Oct 2001
Location: Germany, rural Altmark
Posts: 6,783
|
Thanks, mandarinka, that explains a bit. I meant SSE3 of 2004 (a.k.a. "Prescott New Instructions" PNI, according to Wikipedia), originally. SSSE3 of 2006 did not arrive in AMD CPUs before the "Cat" (Fusion APU) and "Heavy Equipment" series, so Athlon64/Phenom are clearly out of business.
|
20th November 2018, 01:08 | #1235 | Link | |
Moderator
Join Date: Jan 2006
Location: Portland, OR
Posts: 4,770
|
Quote:
Not that VBV is being used in any AV1 testing I've seen so far. |
|
20th November 2018, 04:13 | #1236 | Link |
Registered User
Join Date: Apr 2018
Posts: 63
|
So I am not entirely sure about what the stats file from first pass includes.
When using pure "q" mode for constant quality, is there a benefit to doing a first pass, or does the first pass only determine how to distribute bitrate when a target bitrate and vbr is specified? |
20th November 2018, 16:37 | #1237 | Link |
Registered User
Join Date: Jul 2018
Posts: 80
|
Building Modern Web Media Experiences: AV1 (Chrome Dev Summit 2018)
https://youtu.be/iTC3mfe0DwE?t=612
Last edited by marcomsousa; 20th November 2018 at 19:16. |
22nd November 2018, 00:09 | #1239 | Link |
Registered User
Join Date: Apr 2018
Posts: 63
|
dav1d is doing well
http://www.jbkempf.com/blog/post/201...-first-release |
22nd November 2018, 11:48 | #1240 | Link | |
Helenium(Easter)
Join Date: Aug 2017
Location: Hsinchu, Taiwan
Posts: 99
|
64-bit GCC 8.2.0 binaries: av1-1.0.0-962-1468e60d7
Quote:
__________________
Monochrome Anomaly |
|
|
|