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. |
27th August 2018, 13:06 | #861 | Link |
*****
Join Date: Feb 2005
Posts: 5,647
|
I previously used this for mingw build of decoder lib:
Code:
rm -rf CmakeCache.txt CMakeFiles cmake.exe ..\aom -G "MSYS Makefiles" -DCMAKE_AR="C:\msys64\mingw64\bin\x86_64-w64-mingw32-gcc-ar.exe" -DCMAKE_TOOLCHAIN_FILE="..\aom\build\cmake\toolchains\x86_64-mingw-gcc.cmake" -DCONFIG_LOWBITDEPTH=1 -DCONFIG_AV1_ENCODER=0 -DCONFIG_LIBYUV=0 -DCONFIG_WEBM_IO=0 -DENABLE_DOCS=0 -DENABLE_EXAMPLES=0 -DENABLE_TOOLS=0 -DENABLE_TESTS=0 -DENABLE_TESTDATA=0 make |
27th August 2018, 13:43 | #862 | Link |
Registered User
Join Date: Apr 2008
Location: Russia, Vladivostok
Posts: 2,788
|
I try - but cmake show me error about avx2 and exit. Maybe it's because my CPU don't support AVX2.
__________________
AMD Ryzen 5 3600 /GIGABYTE B450 Gaming X /Patriot 32Gb@3200 /Kingston 500Gb M.2 /RTX 4060 /Samsung U28R550UQI /OLED Philips 55OLED707 /Yamaha RX-V471 + NS-555 + NS-C444 + NS-333 + YST-SW215 |
27th August 2018, 15:55 | #864 | Link | |
Registered User
Join Date: Jun 2013
Posts: 95
|
Quote:
Edit: this is outdated info.
__________________
https://github.com/MoSal Last edited by MoSal; 27th August 2018 at 18:12. |
|
27th August 2018, 16:30 | #865 | Link |
Registered User
Join Date: Dec 2008
Posts: 1,971
|
This is unexpected for me. I spent a lot of time using it.
__________________
MPC-BE 1.7.0 and Nightly builds | VideoRenderer | ImageSource | ScriptSource | BassAudioSource |
27th August 2018, 16:40 | #866 | Link | |
Registered User
Join Date: Aug 2014
Posts: 4
|
Quote:
|
|
27th August 2018, 18:13 | #867 | Link | |
Registered User
Join Date: Jun 2013
Posts: 95
|
Quote:
__________________
https://github.com/MoSal |
|
27th August 2018, 20:08 | #868 | Link |
Registered User
Join Date: Apr 2004
Posts: 1,315
|
|
28th August 2018, 18:57 | #870 | Link | |
Moderator
Join Date: Jan 2006
Location: Portland, OR
Posts: 4,771
|
Quote:
--preset placebo --subme 7 --cu-lossless --tskip --bframes 16 --no-wpp Which would still be faster than libaom, and would make more exhaustive use of HEVC's features. At very low bitrates, maybe another 10-15% reduction in bits @ quality versus slower. Quality @ Speed is the name of the game here, and comparisons at orders of magnitude different speed aren't that applicable to estimating real-world advantages of different bitstream formats. (not a diss at the OP; that data might have been useful for an internal comparison for just posting to Twitter. I just want to warn against premature optimism based on Excel RD plots). |
|
1st September 2018, 15:17 | #872 | Link | ||
Registered User
Join Date: Mar 2002
Posts: 863
|
Quote:
Quote:
|
||
5th September 2018, 02:26 | #873 | Link |
Registered User
Join Date: Mar 2004
Posts: 1,126
|
chrome 69 was supposed to add av1 decoding support (which could be enabled using about:flags) however they removed it a week or so ago. If you were wondering why the newly released v69 didn't have it now you know why. I'm pretty sure it will be in v70, though probably disabled by default.
Last edited by hajj_3; 5th September 2018 at 23:19. |
5th September 2018, 05:01 | #874 | Link | |
Registered User
Join Date: Jul 2018
Posts: 80
|
Quote:
Chrome 69 adds an AV1 decoder to Chrome Desktop stable (Windows, Mac, Linux, ChromeOS) based on the official bitstream specification. At this time, support is limited to "Main" profile 0 and does not include encoding capabilities. The supported container is ISO-BMFF (MP4). To enable this feature use the chrome://flags/#enable-av1-decoder flag. source At this moment it's planing be enabled by default in Chrome v70. Last edited by marcomsousa; 5th September 2018 at 16:51. |
|
5th September 2018, 10:53 | #876 | Link | ||
Registered User
Join Date: Oct 2009
Posts: 930
|
Quote:
Quote:
|
||
5th September 2018, 14:49 | #877 | Link | |
Registered User
Join Date: Jan 2007
Posts: 729
|
[Rav1e tune Psychovisual vs PSNR]
Quote:
I did not get those "super weird lines" shown in the github issue thread, but I think some similar stripe artifacts do appear in smaller degree too (some transform basis function showing?). Here are some example images: http://imgbox.com/g/l1gKciGNMk I tested it on a bluray sample I had for other purposes, 1985 animation (remaster with some noise reduction. Chroma noise has been temporally filtered by me earlier). I don't normally deal with live action footage so I have to leave that to others. The sample is a mashup of dunno, 15 scenes, 910 frames total. Lossless encode is about 500 megabytes in case anybody wants to take a look. I noticed that rav1e at the default speed setting had about the same performance/thread as x265 settings I used for testing before (though that was at much higher bitrate than what I received now), so I decided to use the exact same CLI except for 2-pass to make a comparison clip. So these are not x265 default settings, note. x265_2.6+2.exe - --input-depth 8 --input-res 1440x1080 --fps 24000/1001 --preset slower --output-depth 10 --ctu 32 --max-tu-size 16 --bitrate 4200 --pass 1 --tu-intra-depth 2 --tu-inter-depth 2 --rdpenalty 2 --me 3 --subme 5 --merange 92 --amp --rect --ref 6 --weightb --weightp --keyint 300 --min-keyint 1 --bframes 8 --aq-mode 1 --aq-strength 1.0 --rd 5 --psy-rd 1.6 --psy-rdoq 8.0 --rdoq-level 1 --no-sao --no-open-gop --rc-lookahead 80 --max-merge 5 --qcomp 0.70 --no-strong-intra-smoothing --no-limit-modes --limit-refs 0 --limit-tu 0 --frame-threads 1 --no-wpp --deblock -2:-2 --qg-size 8 --pbratio 1.2 --no-cutree --cu-lossless --lookahead-slices 1 --sar 1:1 --range limited --chromaloc 0 --colormatrix bt709 --no-rskip --rd-refine --cbqpoffs -2 --crqpoffs -2 -o hevc-test.hevc (this got 4146 kbps on second pass) Rav1e commandlines: rav1e.exe --speed 3 --quantizer 70 --tune Psnr dump.y4m -o psnr.ivf (got ~4200 kbps) rav1e.exe --speed 3 --quantizer 75 --tune Psychovisual dump.y4m -o psy.ivf (got ~4270 kbps) binary used: https://ci.appveyor.com/project/tdae....195/artifacts |
|
5th September 2018, 14:50 | #878 | Link |
Registered User
Join Date: Jan 2007
Posts: 729
|
Also, may I have some suggestions? I realize that Rav1e is very early in development (I guess no more can be expected from encoders under the age of 2 years and/or supporting adaptive quantization and such important features).
However, there are some changes that I think could be useful to do even at this early stage. 1) there is a general lack of configurable settings and I heard some rumor that this might actually be somewhat a policy (like the nonexistent user-facing configurabiltiy in Theora?) and not just effect of being early in development. This is an unfortunate position IMHO. x264/x265 have shown that configurability actually adds to both performance and quality because people can tweak settings. No defaults can be good for everybody. In addition, the it's the configurability that allows testers to actually test the encoder. You can't even get feedback about your default internal tuning if random people can't test it against different set of parameters. For example, with things like the psychovisual tuning you requested testing off, it would be useful to be able to test what changing the strength does (whether more is better or less is better, where's an apparent sweetspot, whether it is different depending on content etc...) Things like aq-strenth, psychovisual bias settings, ratecontrol parameters like qcompress, these things absolutely have to be user-configurable in a serious encoder. Anything that has some quality-compression balance effect too, or just about any compression tool that is a bonus for compression but not always - or when there are cases where it hurts and people will want to disable it. All encoders/formats have tools like that (hello there SAO) and I don't think there are reasons for AV1 (rav1e) to be completely different. If you bar access to these parameters, you handicap the encoder by leaving compression performance potential locked away. You should strive to sell what you got, like x264/x265 does, not keep it in the vault. Even if you disagree with all of the above, you should think about it form the PR point of view. I'm not the only person feeling like this, so exposing the parameters to users will make your encoder more attractive to users even if you think it's useless... 2) a smaller thing: there is very little feedback given by the commandline encoder. A FPS counter probably isn't completely important, but there is one thing that really would help with testing, and that is a achieved bitrate being reported at the end. I was rather suprised Rav1e didn't report this, because I wanted to encode a comparison clip with 2pass with another encoder and this is rather complicating. I have to figure it out based on filesize but the output's already in a container that has some unknown overhead... I used bitrate calculator like in 2006 but note that those generally only have 1 second precision, which is not very exact for short testing samples. |
5th September 2018, 16:11 | #879 | Link |
Registered User
Join Date: Jun 2013
Posts: 95
|
Is it Chrome? or a Chromium distribution package?
__________________
https://github.com/MoSal |
5th September 2018, 16:44 | #880 | Link |
Registered User
Join Date: Jul 2018
Posts: 80
|
It seems that AV1 has disable in M69 by Google in last minute
But in official docs it's still there Source |
|
|