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. |
25th February 2017, 22:45 | #4821 | Link |
Testeur de codecs
Join Date: May 2003
Location: France
Posts: 2,484
|
Rysen seem to have really good AVX/AVX2 implementation too ... Almost as good as Kaby lake
__________________
Le Sagittaire ... ;-) 1- Ateme AVC or x264 2- VP7 or RV10 only for anime 3- XviD, DivX or WMV9 |
25th February 2017, 22:46 | #4822 | Link |
Registered User
Join Date: Aug 2010
Location: Athens, Greece
Posts: 2,901
|
I certainly don't believe that.
__________________
Win 10 x64 (19042.572) - Core i5-2400 - Radeon RX 470 (20.10.1) HEVC decoding benchmarks H.264 DXVA Benchmarks for all |
26th February 2017, 00:02 | #4823 | Link | |
Registered Developer
Join Date: Mar 2010
Location: Hamburg/Germany
Posts: 10,346
|
Quote:
Anyway, we'll see actual believable results in a week or so, not "leaked" results or AMD marketing results.
__________________
LAV Filters - open source ffmpeg based media splitter and decoders |
|
26th February 2017, 00:08 | #4824 | Link |
Artem S. Tashkinov
Join Date: Dec 2006
Posts: 345
|
March the 2nd is really close, it's just four days from now. I guess we can all stop and wait for the official benchmarks. Also, there are rumors that AMD has already shipped a million Ryzen CPUs so we'll have a lot of data to chew on.
|
26th February 2017, 00:10 | #4825 | Link |
German doom9/Gleitz SuMo
Join Date: Oct 2001
Location: Germany, rural Altmark
Posts: 6,781
|
I'll be curious too. AMD used to be "notorious" for well optimized die designs vs. "brute force" preferred by intel. And even if RyZen is not as powerful as people may hope for, we still have to thank AMD for pushing intel (and Nvidia?) back to a solid ground, regarding price management ... — Thanks birdie for the link a page ago.
|
26th February 2017, 00:45 | #4826 | Link |
Registered User
Join Date: May 2015
Posts: 185
|
Anyone could take a quick peek at these settings and tell me if I'm missing a tweak here and there, thanks?
C:\x26x>x265.exe --crf 18 --aq-mode 1 --ctu 64 --qg-size 32 --deblock -1:-1 --me star --bframes 6 --rc-lookahead 60 --ref 5 --b-adapt 2 --tu-intra-depth 4 --tu-inter-depth 4 --merange 92 --weightp --weightb --scenecut 40 --rd 4 --limit-ref 0 --limit-modes --tskip --rect --amp --max-merge 5 --subme 7 --b-intra source.y4m -o out.hevc Thanks! Edit: Also what about --cutree ? Last edited by pingfr; 26th February 2017 at 02:50. |
26th February 2017, 03:08 | #4827 | Link | |
Registered User
Join Date: May 2015
Posts: 68
|
Quote:
|
|
26th February 2017, 07:18 | #4828 | Link | |
Registered User
Join Date: Mar 2015
Location: New Zealand
Posts: 45
|
Quote:
--rskip --no-sao --no-open-gop and I prefer --psy-rdoq 1.1 Cheers, Divxmaster |
|
26th February 2017, 08:11 | #4830 | Link |
Registered User
Join Date: Oct 2001
Location: Germany
Posts: 7,277
|
they both implement the same standard, but x265 has lot of optimizations.
HM = example on how it could be done for academic purposes x265 = real world implementation which is a lot faster and usable |
26th February 2017, 08:59 | #4831 | Link | |
Registered User
Join Date: Aug 2016
Posts: 60
|
Quote:
--tune grain, along with its built-in rc-grain algorithm, fundamentally changes the encoding decisions x265 makes by weighting towards quality over compression (aka high-frequency retention). The settings contained in these presets... ...retain more detail the slower you go. So much so that you can easily drop your non-grain CRF's BACK one or two notches at the slower presets. I suspect that most people who don't understand tunegrain have just left the rest of their options at "veryslow CRF18" when "slow CRF20" would probably produce comparable visual quality, faster encodes and smaller filesizes. This is my current command line, which replaced something 20+ parameters long: Code:
--profile main10 --tune grain --deblock=-6:-6 --no-strong-intra-smoothing Now, I'll admit that tunegrain could still undergo some tweaks for speed, and others have suggested the parameters to do that. Myself, I couldn't be happier about ditching the pursuit of endless quality experiments with this-command-line and that-command-line. |
|
26th February 2017, 09:54 | #4834 | Link |
Registered User
Join Date: Feb 2017
Posts: 14
|
Thanks. I wanted to do generate a log file using HM model that takes the difference in the SNR, quantization parameter etc per frame, ctu, and slice number. Is there such a thing, or should I code manually to do such thing?
|
26th February 2017, 11:12 | #4835 | Link |
Pig on the wing
Join Date: Mar 2002
Location: Finland
Posts: 5,733
|
This. What I've done is choose --preset slower --tune grain --CRF 21 as the baseline, then picked some recommended settings to tune performance (--limit-refs 3 --limit-tu 3 --rskip) and some quality-related ones from the bottom two presets (--tu-inter-depth 4 --tu-intra-depth 4 --max-merge 4). Produces 10-30% smaller files than x264 with my preferred settings at CRF 18, and seems to keep detail better.
__________________
And if the band you're in starts playing different tunes I'll see you on the dark side of the Moon... |
26th February 2017, 12:15 | #4837 | Link | |
Registered User
Join Date: May 2015
Posts: 185
|
Quote:
Also I would assume --no-sao disables SAO setting it to 0, whereas every preset excepted for ultrafast and superfast have the value set to 1, makes me to actually WANT the SAO. Now can some kind soul explain what is the rdoq-level? why is it set at 2 and how to make sure to keep it set at 2 from the command line args? Thanks. |
|
26th February 2017, 12:40 | #4840 | Link |
ffx264/ffhevc author
Join Date: May 2007
Location: /dev/video0
Posts: 1,844
|
The presets of x265 are optimized for (very) low bitrate where at those levels, blur is preferred over other compression artifacts. That's why most have SAO and intra smoothing enabled. Also the x265 presets haven't been optimized in a long time. If you want to squeeze out as much detail as possible, you'll need to tweak manually (IMHO)
|
Thread Tools | Search this Thread |
Display Modes | |
|
|