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. |
22nd July 2019, 19:19 | #6941 | Link | |
Moderator
Join Date: Jan 2006
Location: Portland, OR
Posts: 4,770
|
Quote:
|
|
24th July 2019, 15:20 | #6945 | Link | |
ffx264/ffhevc author
Join Date: May 2007
Location: /dev/video0
Posts: 1,844
|
Quote:
I use umh because I find it preserves details better but is a bit slower than star |
|
24th July 2019, 22:41 | #6948 | Link | |
Registered User
Join Date: Jan 2007
Posts: 729
|
Quote:
To get higher speed, lower your merange. The value given is used as the distance of the first-stage search, so it is effectively quadrupled. |
|
25th July 2019, 06:28 | #6949 | Link |
Pig on the wing
Join Date: Mar 2002
Location: Finland
Posts: 5,733
|
I'm currently using merange 32 for my 720p encodes (max CTU and TU is 32 for better CPU utilization). Would it make sense to lower the value for example to 16-20 and enable HME (with umh,umh,umh), or is the first stage range so important that it will start to affect the final result too much?
__________________
And if the band you're in starts playing different tunes I'll see you on the dark side of the Moon... |
25th July 2019, 06:55 | #6950 | Link | |
ffx264/ffhevc author
Join Date: May 2007
Location: /dev/video0
Posts: 1,844
|
Quote:
ctu size - 4(luma) - 2(chroma) (- 1 if me=hex is used) You can lower it to 26 and enable HME like I do. Here the performance penalty is very minor, also considering that HME, as explained in the article I linked to a few posts earlier, has computationally low complexity I wonder what options the poster above uses to hit a 40% reduction in speed when HME is enabled |
|
25th July 2019, 10:17 | #6951 | Link | |
Pig on the wing
Join Date: Mar 2002
Location: Finland
Posts: 5,733
|
Quote:
__________________
And if the band you're in starts playing different tunes I'll see you on the dark side of the Moon... |
|
25th July 2019, 11:55 | #6952 | Link | |
ffx264/ffhevc author
Join Date: May 2007
Location: /dev/video0
Posts: 1,844
|
Quote:
Code:
X265PARAMS="ref=4:me=umh:hme=1:hme-search=umh,umh,umh:bframes=6:rd=4:subme=4:merange=26:strong-intra-smoothing=0:ctu=32:sao=0:cu-lossless=0:cutree=1:fades=1:tu-inter-depth=3:tu-intra-depth=3:rskip=1:max-merge=1:rc-lookahead=60:aq-mode=1:aq-strength=1.0:rdoq-level=1:psy-rdoq=1.5:psy-rd=2.3:limit-modes=1:limit-refs=3:limit-tu=1:rd-refine=0:deblock=-3,-3:weightb=1:weightp=1:rect=1:amp=0:wpp=1:pmode=0:pme=0:b-intra=1:b-adapt=2:b-pyramid=1:tskip-fast=0:fast-intra=0:early-skip=0:min-keyint=24:keyint=240" |
|
25th July 2019, 13:45 | #6953 | Link |
Pig on the wing
Join Date: Mar 2002
Location: Finland
Posts: 5,733
|
Biggest differences seem to be ref=5, me star, rd=6, rd-refine, strong-intra-smoothing, max-merge=4 and amp in my settings. I don't think those should affect the search for motion though. I really need to test to get some rough values.
__________________
And if the band you're in starts playing different tunes I'll see you on the dark side of the Moon... |
25th July 2019, 13:53 | #6954 | Link | |
Registered User
Join Date: Apr 2009
Posts: 478
|
Quote:
I can't wait to get a 3900X or a 16 core Threadripper! |
|
25th July 2019, 13:59 | #6955 | Link | |
ffx264/ffhevc author
Join Date: May 2007
Location: /dev/video0
Posts: 1,844
|
Quote:
Motion Estimation is where the encoder spends most of its time and takes the biggest penalty the higher you get. rd=6 is very expensive. I'm fine with rd=4 (which is really rd=3 as 4 maps to it) This is the best I can do on my i7 7700K when turning on HME. I don't want to wait days for an encode to finish and I won't see the difference when watching from afar on the TV With my settings above and HME turned on, I can shave ~100 MiB of an encode. Encoded Blade Runner once with and once without HME. The result was 100 MiB in size reduction with better subjective quality when HME is on Last edited by microchip8; 25th July 2019 at 14:12. |
|
25th July 2019, 17:15 | #6956 | Link |
Pig on the wing
Join Date: Mar 2002
Location: Finland
Posts: 5,733
|
Here are my results with my Black Sails testclip, 2748 frames @ CRF 18:
rd 6, no hme - 4333,39 kbps - 2.91 fps rd 6, hme umh - 4323,63 kbps - 2.16 fps rd 4, no hme - 4149,59 kbps - 3.95 fps rd 4, hme umh - 4154,60 kbps - 2.66 fps So the difference with rd=4 is even bigger than with rd=6 + rd-refine. I'm using a Ryzen 1800X @ 3.8 GHz.
__________________
And if the band you're in starts playing different tunes I'll see you on the dark side of the Moon... |
25th July 2019, 17:22 | #6957 | Link | |
ffx264/ffhevc author
Join Date: May 2007
Location: /dev/video0
Posts: 1,844
|
Quote:
|
|
25th July 2019, 18:18 | #6958 | Link |
Pig on the wing
Join Date: Mar 2002
Location: Finland
Posts: 5,733
|
Of course, it could be AVX2 which is making the difference here. On a first generation Zen CPU, it's more useful to disable it (as I've done). I'd expect an Intel CPU to benefit from AVX2.
__________________
And if the band you're in starts playing different tunes I'll see you on the dark side of the Moon... |
26th July 2019, 14:21 | #6959 | Link |
ffx264/ffhevc author
Join Date: May 2007
Location: /dev/video0
Posts: 1,844
|
I've reported the segfault when using star for hme-search Level 0 to the x265 devs. One of them came with a patch which I tested and seems to work. Patch is not committed yet but you can find it at https://mailman.videolan.org/piperma...ly/012601.html
|
|
|