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. |
26th September 2018, 16:36 | #6381 | Link | |
Moderator
Join Date: Jan 2006
Location: Portland, OR
Posts: 4,770
|
Quote:
Yes, the -cp?offs ARE the chroma offsets. I don’t recall the exact math; it was based on an IEEE paper a couple years back. But it is adaptive based on luma, and so is going to be better than just fixed offsets. |
|
26th September 2018, 16:44 | #6382 | Link | |
Moderator
Join Date: Jan 2006
Location: Portland, OR
Posts: 4,770
|
Quote:
Those are what I know about. When using —no-slow-firstpass you probably want to make sure to set the number of ref and b-frames to match the second pass. The first pass is less useful as a reference without those, which will hurt quality a bit, and might slow encoding. That said, the multi-pass options and no-slow-firstpass might be incompatible in practice, since x265 can’t refine stuff that the first pass didn’t do. Or at least, some parameter fine-tuning might be required to make sure the 1st pass is a good reference. |
|
26th September 2018, 17:04 | #6383 | Link | |
Registered User
Join Date: Aug 2010
Location: Athens, Greece
Posts: 2,901
|
Quote:
I just got my budget Chinese tablet with MediaTek MT6797 (Xelio X20) inside - a 2016 SoC It supports in hardware MPEG2, VC-1/ WMV3, VP8, VP9 (8bit/10bit), H.264 (8bit/10bit), H.265 (8bit/10bit) Also, my Sony is an ATV2 with MediaTek MT5891 SoC inside and supports H.264 10bit too. End of OT.
__________________
Win 10 x64 (19042.572) - Core i5-2400 - Radeon RX 470 (20.10.1) HEVC decoding benchmarks H.264 DXVA Benchmarks for all |
|
26th September 2018, 18:06 | #6384 | Link | |
Registered User
Join Date: Jul 2016
Posts: 19
|
Quote:
I would keep options 2 and 3, and add --no-strong-intra-smoothing --no-sao --multi-pass-opt-rps for some speedups as well. |
|
26th September 2018, 18:47 | #6385 | Link | |
Registered User
Join Date: May 2009
Posts: 184
|
Quote:
I'll leave --c*qpoffs at default for HDR ecndoes then and set --hdr-opt instead. |
|
27th September 2018, 16:35 | #6386 | Link |
Registered User
Join Date: Feb 2007
Location: Sweden
Posts: 483
|
x265 v2.8+74-fd517ae68f93 (32 & 64-bit 8/10/12bit Multilib Windows Binaries)
Code:
https://bitbucket.org/multicoreware/x265/commits/branch/default |
6th October 2018, 13:50 | #6388 | Link |
Pig on the wing
Join Date: Mar 2002
Location: Finland
Posts: 5,733
|
Apart from the required bitrate to encode a frame, is the only real difference between --rd 4 and --rd 6 just the amount of effort required by the encoder? So I could switch to using --rd 4 if I'm ready to accept that it will probably produce a bigger file but take much less time? The presets don't seem to change the setting at all from the default 3, but 4 is the one where the other settings related to RDO kick in.
__________________
And if the band you're in starts playing different tunes I'll see you on the dark side of the Moon... |
6th October 2018, 15:48 | #6389 | Link |
Registered User
Join Date: Feb 2007
Location: Sweden
Posts: 483
|
x265 v2.9+1-169e76b6bbcc (32 & 64-bit 8/10/12bit Multilib Windows Binaries)
Code:
https://bitbucket.org/multicoreware/x265/commits/all |
8th October 2018, 17:17 | #6393 | Link | |
Moderator
Join Date: Jan 2006
Location: Portland, OR
Posts: 4,770
|
Quote:
I don’t know if it’d be THAT much less time, but it’ll help. |
|
10th October 2018, 15:12 | #6394 | Link |
Registered User
Join Date: Feb 2007
Posts: 128
|
Thanks for providing builds for v2.9, guys!
I just always wonder - how to tell which cpu capabilities a build is using (AVX? AVX2? None?). As far as I can tell x265.exe -V is misleadingly saying "using CPU capabilities X Y Z" but in fact it is actually just listing MY CPU's capabilities. Is that right? |
10th October 2018, 15:22 | #6395 | Link | ||
Herr
Join Date: Apr 2009
Location: North Europe
Posts: 556
|
Quote:
Quote:
|
||
10th October 2018, 15:25 | #6396 | Link | |
Registered Developer
Join Date: Mar 2010
Location: Hamburg/Germany
Posts: 10,346
|
Quote:
Some people try to get a tiny bit of extra performance by allowing the C/C++ compiler to use those instructions sets to optimize the code, however one should know that compilers are limited in what they can do, and the majority of the "hot" (ie. important) code is manually optimized and unaffected by the compilers choices. In my experience, the differences between a generic build with just the ASM enabled that the x265 developers wrote, and a build that allows the compiler to additionally use AVX/AVX2 to optimize the remaining code is relatively small, probably low single digits percentages.
__________________
LAV Filters - open source ffmpeg based media splitter and decoders |
|
10th October 2018, 20:05 | #6398 | Link |
Artem S. Tashkinov
Join Date: Dec 2006
Posts: 345
|
Version 2.9
Release date - 05/10/2018 New features
Last edited by birdie; 10th October 2018 at 20:10. |
10th October 2018, 20:14 | #6399 | Link |
Registered User
Join Date: Feb 2007
Posts: 128
|
@Forteen88:
Thanks, man. That's where I'm usually grabbing my builds from. But no 2.9 yet. But there are cool guys here too, providing builds. @nevcairiel: Moin nevcairiel, thanks for the insights! Huh. The x265.exe --V output made me think that there are some AVX2 optimizations in the project's code itself. That's why I'm asking. But you're saying it's just about compiler optimizations. Hm. |
Thread Tools | Search this Thread |
Display Modes | |
|
|