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. |
24th July 2021, 19:41 | #41 | Link |
Registered User
Join Date: May 2006
Posts: 3,997
|
--ctu32 in addition to --rskip 2 may bring some stars back, but other stars and details disappear. Artefacts are ugly in both cases. The compression of about 1/8 is simply too much IMO, but one could argue that the results are amazingly good for this high compression.
|
24th July 2021, 20:14 | #42 | Link | |
ffx264/ffhevc author
Join Date: May 2007
Location: /dev/video0
Posts: 1,843
|
Quote:
|
|
24th July 2021, 21:22 | #43 | Link | |
Moderator
Join Date: Jan 2006
Location: Portland, OR
Posts: 4,750
|
Quote:
To directly allow for the minimum size TU's: --tu-intra-depth 4 --tu-inter-depth 4 To reduce the perf hit --limit-tu 4 Stars can also be helped by --amp and --rect, which also have a speed penalty, which can be mitigated somewhat by --limit-modes. With minimum tu size and amp/rect being used, x265 can tweak things down to almost an individual pixel. Of course, by that point we're more finding something between slower and veryslow, not a middle ground between medium and slow. --tskip --tskip-fast may also help with stars. A dot in a flat block isn't well-suited to a frequency transform. |
|
25th July 2021, 06:58 | #44 | Link | ||
Registered User
Join Date: May 2014
Posts: 292
|
Quote:
Quote:
Code:
ffmpeg -i z:\space_6s.mkv -f yuv4mpegpipe - | x265 --y4m - --preset medium --output-depth 10 --profile main10 --crf 32.6 --rskip 0 --tskip --ctu 32 --hme --hme-search hex,hex,hex --tu-intra-depth 4 --tu-inter-depth 4 -o z:\R0.mkv Code:
ffmpeg -i z:\space_6s.mkv -f yuv4mpegpipe - | x265 --y4m - --preset medium --output-depth 10 --profile main10 --crf 31.3 --rskip 2 --rskip-edge-threshold 1 --tskip --ctu 32 --hme --hme-search hex,hex,hex --tu-intra-depth 4 --tu-inter-depth 4 -o z:\R2.mkv
__________________
Win10x64, Xeon E5450, GTX 750 2GB, DDR3 8GB. Last edited by Gravitator; 25th July 2021 at 07:01. |
||
25th July 2021, 11:33 | #45 | Link |
Pig on the wing
Join Date: Mar 2002
Location: Finland
Posts: 5,718
|
That should apply only to the CTU 64 & limit-tu 0 combination. I've not seen any issues at 1080p with CTU 64 and limit-tu 4. For lower resolutions I always set CTU to 32.
__________________
And if the band you're in starts playing different tunes I'll see you on the dark side of the Moon... |
25th July 2021, 16:44 | #46 | Link | |
Registered User
Join Date: May 2014
Posts: 292
|
Quote:
Code:
ffmpeg -i c:\space_6s.mkv -f yuv4mpegpipe - | x265 --y4m - --preset medium --output-depth 10 --profile main10 --crf 31.8 --rskip 2 --rskip-edge-threshold 1 --tskip --ctu 32 --hme --hme-search hex,hex,hex --tu-intra-depth 4 --tu-inter-depth 4 -o c:\r2_ctu32.mkv Code:
ffmpeg -i c:\space_6s.mkv -f yuv4mpegpipe - | x265 --y4m - --preset medium --output-depth 10 --profile main10 --crf 31.2 --rskip 2 --rskip-edge-threshold 1 --tskip --ctu 64 --hme --hme-search hex,hex,hex --tu-intra-depth 4 --tu-inter-depth 4 -o c:\r2_ctu64.mkv
__________________
Win10x64, Xeon E5450, GTX 750 2GB, DDR3 8GB. |
|
25th July 2021, 18:25 | #48 | Link | ||
Pig on the wing
Join Date: Mar 2002
Location: Finland
Posts: 5,718
|
Quote:
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 2021, 20:37 | #49 | Link | |
Registered User
Join Date: May 2014
Posts: 292
|
Quote:
------ I am looking for x265 maximum setting to get closer to the quality of AOM. Download the encoded sample > AOM
__________________
Win10x64, Xeon E5450, GTX 750 2GB, DDR3 8GB. |
|
26th July 2021, 19:44 | #51 | Link | |
Moderator
Join Date: Jan 2006
Location: Portland, OR
Posts: 4,750
|
Quote:
--hme --hme-range 16,32,32 --hme-search hex,umh,star The coarser ME passes should pick up on the stars, with the last stage really only for refinement. A smaller, more exhaustive search could help quite a bit to get the 1/8th pel optimal. I've not really tested this personally, however. |
|
28th July 2021, 17:42 | #53 | Link | |
Video Fanatic
Join Date: Jul 2021
Location: Surrey
Posts: 89
|
Quote:
-rskip-edge-threshold 4 --psy-rd 2.10 --psy-rdoq 1.1 --rskip 2 --me umh --rc-lookahead 30 (or 25) Based on testing on a slow CPU (Skylake-era Xeon 4C/4T), the penalty is ~6% increased time but retaining much more detail and better detail in moving scenes. |
|
28th July 2021, 20:46 | #54 | Link | |
Moderator
Join Date: Jan 2006
Location: Portland, OR
Posts: 4,750
|
Quote:
The x265 presets haven't bee refactored in several years now, and don't include a lot of features that would help. --selective-sao 2 is an essentially free speedup, for example, and should be default in every preset except maybe placebo. And even placebo could use --selective-sao 3. (SAO does very little for bidirectional prediction or non-reference frames). --dynamic-refine is a great quality/speed feature for VBV-limited encodes, as it cranks up complexity when quality is VBV-limited, and then lets it drop down where the CRF quality can be met. Encoding time will vary with source more, but it averages out to a good quality/speed win by spending more cycles just where it improves quality. |
|
29th July 2021, 12:35 | #55 | Link |
Pig on the wing
Join Date: Mar 2002
Location: Finland
Posts: 5,718
|
Which areas of the frame should be affected by --selective-sao 2 compared to --selective-sao 0? I just did a quick test regarding filesize and at the same CRF, the filesize for 0 was 2651 kbps / avg QP 18.23 while for 2 they were 2926.94 / 17.86 and based on the stats, the QPs for P-frames were substantially lower. I-frames pretty much the same for both versions.
EDIT: it's also odd that --selective-sao 2 is faster even though it produces a bigger file and should require more computation than no SAO at all.
__________________
And if the band you're in starts playing different tunes I'll see you on the dark side of the Moon... Last edited by Boulder; 29th July 2021 at 13:21. |
29th July 2021, 17:08 | #56 | Link | |
Moderator
Join Date: Jan 2006
Location: Portland, OR
Posts: 4,750
|
Quote:
|
|
16th August 2021, 23:54 | #59 | Link |
Moderator
Join Date: Jan 2006
Location: Portland, OR
Posts: 4,750
|
You can import a x264 encode as data to refine, but I've never tried it.
Tweaking a faster firstpass with x265 is probably going to give better speed/performance. x265 defaults to --no-slow-firstpass to avoid 1/2nd pass mismatches. But IIRC, as long as you use the same --ref and --bframes between passes, you can speed up --me, add a bunch of early-exit options, etcetera. It's been years since I've tried it, but with some testing I'm sure compatible yet faster 1st pass settings can be determined. |
Thread Tools | Search this Thread |
Display Modes | |
|
|