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. |
![]() |
#6781 | Link | |
SuperVirus
Join Date: Jun 2012
Location: Antarctic Japan
Posts: 1,115
|
Quote:
![]() It is somewhat bloated because of the additional stuff, but I compressed it with upx and now it has a healthy weight. Last edited by filler56789; 21st April 2019 at 16:58. Reason: damn typos :-/ |
|
![]() |
![]() |
![]() |
#6782 | Link |
Pig on the wing
Join Date: Mar 2002
Location: Hollola, Finland
Posts: 4,972
|
How does one get rid of the "onion gradient" artifacts of x265? In the sample images, they are apparent in the character's forehead and also in the purplish stripe near his hair (zoom a bit to see both better). The bitrate of the encodes is ~6900 kbps.
x264 ![]() x265, aq-mode 1 ![]() x265, aq-mode 2 ![]() Some base settings of the x265 encode: Code:
--deblock -2:-1 --no-strong-intra-smoothing --cbqpoffs -3 --crqpoffs -3 --subme 3 --merange 24 --no-sao --no-rect --qcomp 0.7 --rd 6 --rd-refine --aq-mode 1/aq-mode 2 --aq-strength 0.9 --ctu 16 --max-tu-size 8 --qg-size 16 --tu-inter-depth 2 --tu-intra-depth 2 --limit-tu 1 --limit-refs 3 --max-merge 2 --ref 5 --bframes 10
__________________
And if the band you're in starts playing different tunes I'll see you on the dark side of the Moon... |
![]() |
![]() |
![]() |
#6784 | Link | |
Moderator
![]() Join Date: Jan 2006
Location: Portland, OR
Posts: 3,470
|
Quote:
A 8x8 max tu is pretty unusual, and those are also big chroma offsets which can suck bits away from luma. What are the goals of these settings, and how tdid you come to them? |
|
![]() |
![]() |
![]() |
#6785 | Link |
Pig on the wing
Join Date: Mar 2002
Location: Hollola, Finland
Posts: 4,972
|
I got you the original clip here. I basically did a very slight MDegrain and then downscaled to 1280x720 using a very sharp Bicubic and fed to the encoders.
https://drive.google.com/open?id=1Qm...9NZavzXFTSkGIr My x265 settings are based on frame-by-frame comparisons that I made several times. A small CTU and TU size look better (least distortion compared to the original image) with 720p encodes. For 1080p, I would use one notch higher values (also based on my tests). The chroma offsets don't change the bitrate much in CRF mode so the difference in 2-pass shouldn't also be big. Besides, x264 already does a similar thing by default. EDIT: does anyone else have problems with topic notifications? I don't get any emails at all from any thread I've subscribed to.
__________________
And if the band you're in starts playing different tunes I'll see you on the dark side of the Moon... |
![]() |
![]() |
![]() |
#6786 | Link | |
Lost my old account :(
Join Date: Jul 2017
Posts: 163
|
Quote:
x264 2pass @ 5Mbps, veryslow tune film ![]() x265 2pass @ 5Mbps, slow, --no-sao --no-strong-intra-smoothing --deblock -1:-1 ![]() Last edited by excellentswordfight; 27th April 2019 at 11:00. |
|
![]() |
![]() |
![]() |
#6787 | Link | |
Pig on the wing
Join Date: Mar 2002
Location: Hollola, Finland
Posts: 4,972
|
Quote:
I did some more testing now that I found those troublesome frames (it seems they evaded me when I pinpointed my go-to settings a long time ago), and using CTU 32 makes the onionize effect go away. I also left max-tu-size and qg-size at their defaults since things looked good.
__________________
And if the band you're in starts playing different tunes I'll see you on the dark side of the Moon... |
|
![]() |
![]() |
![]() |
#6788 | Link | |
Registered User
Join Date: Mar 2006
Posts: 101
|
Quote:
x265 CRF 28, veryslow, --no-sao --no-strong-intra-smoothing --deblock -1:-1 ![]() ![]() ![]() More bitrate removes the artifacting. |
|
![]() |
![]() |
![]() |
#6789 | Link |
Pig on the wing
Join Date: Mar 2002
Location: Hollola, Finland
Posts: 4,972
|
In those cases, I had thrown quite a lot of bitrate there. Using CRF18 produced a smaller file than 6900 kbps, which was x264@CRF18. CRF28 is something I'd never use
![]()
__________________
And if the band you're in starts playing different tunes I'll see you on the dark side of the Moon... |
![]() |
![]() |
![]() |
#6790 | Link |
Derek Prestegard IRL
![]() Join Date: Nov 2003
Location: Los Angeles
Posts: 5,790
|
I'd caution against doing too much settings tuning using still frame comparisons, especially when evaluating max CU size (--ctu).
I've spent a lot of time doing this. Using --ctu 32 can indeed produce a sharper / more detailed / less blurred image when looking at single frames - relative to keeping the default (--ctu 64) in some cases. However, the trade-off is typically more blocking, which you're more likely to notice in motion. In other words, an inferior user experience unless you're using very high bitrates. You're kind of performing a brute force non-adaptive psy tuning. x265 will use smaller CUs when it sees fit, you're just forcing it to never consider 64x64, even when coding giant uniform areas. In my opinion, you're typically best off trusting the extensive tuning and testing that MulticoreWare has done, and just using a preset. They set --ctu to 64 starting with --preset veryfast, and keep it that way all the way through placebo. In fact, in looking at the documentation for this parameter: https://x265.readthedocs.io/en/defau...#cmdoption-ctu it appears the only reason they set this to 32 for superfast and lower is that this increases parallelism and can therefore be faster. Do what's right for you, of course ![]() Last edited by Blue_MiSfit; 28th April 2019 at 22:02. |
![]() |
![]() |
![]() |
#6791 | Link |
Registered User
Join Date: Oct 2016
Posts: 104
|
I got crash when using zone in x265_12bit.
So I tried to use VSEdit to test it and here is result. Here is x265 file: http://msystem.waw.pl/x265/x265-3.0_..._gcc83-AVX2.7z Here is everything else: https://i.imgur.com/FFlFylW.png |
![]() |
![]() |
![]() |
#6792 | Link | |
Pig on the wing
Join Date: Mar 2002
Location: Hollola, Finland
Posts: 4,972
|
Quote:
As you apparently have been testing things quite a lot, do you have any opinion regarding AQ-mode? I'm still quite unsure if the new default of mode 2 is the best general option for film.
__________________
And if the band you're in starts playing different tunes I'll see you on the dark side of the Moon... |
|
![]() |
![]() |
![]() |
#6793 | Link | |
Lost my old account :(
Join Date: Jul 2017
Posts: 163
|
Quote:
Last edited by excellentswordfight; 29th April 2019 at 17:42. |
|
![]() |
![]() |
![]() |
#6794 | Link |
Registered User
Join Date: Feb 2007
Location: Sweden
Posts: 361
|
x265 v3.0_Au+22-feec4bdf9866 (32 & 64-bit 8/10/12bit Multilib Windows Binaries) (32bit-GCC v7.4.0 / 64bit-GCC v8.3.0)
Code:
https://bitbucket.org/multicoreware/x265/commits/branch/default |
![]() |
![]() |
![]() |
#6796 | Link |
The cult of personality
Join Date: May 2013
Location: Planet Vegeta
Posts: 121
|
I wanted to encode a 10-bit H.264 MKV video (lossless, 30 gb) to HEVC 10-bit... I piped it via ffmpeg but I put this "-pix_fmt yuv420p" instead of this "yuv420p10le"... I suspect this is wrong, but it is the only way it worked. Can you kindly guide me here?
I encoded .vpy file to lossless 10-bit H.264 since my device is slow with the filters I used... so now how to encode the 10-bit .mkv using x265? << I assumed using -pix_fmt yuv420p is wrong. Plus, next time when I want to encode like this (lossless 10-bit H.264 then 10-bit HEVC), should I encode to .yuv/.h264 in x264 (--muxer yuv\raw)? So I can input it directly to x265 without piping?? Here is my command line: Code:
"C:\.....\ffmpeg.exe" -i "C:\....\lossless_H264_video.mkv" -pix_fmt yuv420p -f yuv4mpegpipe - | C:\....\x265_64bit_10bit.exe --y4m --preset slower --crf 17 --ref 6 --rd 6 --psy-rd 1 --ctu 64 --aq-strength 0.8 --output-depth 10 --input-res 1920x1080 - --output "C:\....\ep07_1080p_video_HEVC.hevc" Last edited by ~ VEGETA ~; 1st May 2019 at 21:05. |
![]() |
![]() |
![]() |
#6798 | Link | |
The cult of personality
Join Date: May 2013
Location: Planet Vegeta
Posts: 121
|
Quote:
Where can I find such ffmpeg build for windows? I thought -pix_fmt is to get the input as 10-bit... |
|
![]() |
![]() |
![]() |
#6800 | Link | |
Lost my old account :(
Join Date: Jul 2017
Posts: 163
|
Quote:
Code:
"ffmpeg.exe" -i "input.mkv" -pix_fmt yuv420p10le -f yuv4mpegpipe -strict -1 - | "x265.exe" --y4m |
|
![]() |
![]() |
![]() |
Thread Tools | Search this Thread |
Display Modes | |
|
|