VideoHelp Forum

Try DVDFab and download streaming video, copy, convert or make Blu-rays,DVDs! Download free trial !
+ Reply to Thread
Results 1 to 16 of 16
Thread
  1. My current settings are (HandBrake): 1080p / H.265 10-bit / 23 or 24 CRF / Preset Slow.

    I used to use H.265 8bit with medium preset and this code which I don't know what it does "strong-intra-smoothing=0:rect=0" it was on a preset that I tweaked so I just left it alone.. I saw a lot of people recommending to use --no-sao which I guess removes blurriness? would it help me with preserving skin textures?.

    Thanks.
    Last edited by Felow; 4th Jan 2020 at 21:19.
    Quote Quote  
  2. nowadays using sao should be fine with x265 so I would not disable it (assuming that Handbrake uses x265 for H.265 encoding)
    users currently on my ignore list: deadrats, Stears555
    Quote Quote  
  3. Originally Posted by Selur View Post
    nowadays using sao should be fine with x265 so I would not disable it (assuming that Handbrake uses x265 for H.265 encoding)
    So it doesn't affect skin textures right?.
    Quote Quote  
  4. It should not unless the bitrate is to low to show the textures properly.
    users currently on my ignore list: deadrats, Stears555
    Quote Quote  
  5. Originally Posted by Selur View Post
    It should not unless the bitrate is to low to show the textures properly.
    ok what about "strong-intra-smoothing=0:rect=0" what does it do? it was activated on the default preset.
    Quote Quote  
  6. see: https://x265.readthedocs.io/en/latest/cli.html
    strong-intra-smoothing=0:rect=0 means both options are disabled
    users currently on my ignore list: deadrats, Stears555
    Quote Quote  
  7. Originally Posted by Selur View Post
    nowadays using sao should be fine with x265 so I would not disable it (assuming that Handbrake uses x265 for H.265 encoding)
    In my testing around 2019, it failed with high bit rate applications... (unnecessary blurriness)
    Quote Quote  
  8. @gdgsdg123:
    If a features caused 'unnecessary blurriness' on an old version it does not really say much, especially since:
    a. it's totally unclear what qualifies as 'high bit rate applications' (resolution, settings, content are all unknown)
    b. not knowing what version this was (a lot happened during 2019, including the introduction of sliced based sao; different settings might change things)
    users currently on my ignore list: deadrats, Stears555
    Quote Quote  
  9. Yes it still blurs in 2020. But not as bad as before. Personally I still don't like it

    To disable all , it's --selective-sao 0 --no-sao now.

    SAO tends to blur smaller higher frequency details like fine hairs, skin pores, even at typical bitrate ranges. The trade off is slightly more artifacts. But I prefer details > smooth . Some people prefer smooth, that's ok too . You will typically see the blurring for 10bit x265 CRF 23-24 slow as per the OP's scenario , at least on still frames for typical live action sources. In motion, depends on the person.

    But for low to very low bitrates, or "smooth" content like simple cartoons it can be beneficial (but so can a denoiser)

    Those are just generalizations; it's always better to do some tests and check for yourself for your specific sources


    (Handbrake still does not have a 10bit pipeline in 2020. Don't use it if you have a true 10bit source.)
    Quote Quote  
  10. Originally Posted by poisondeathray View Post
    Yes it still blurs in 2020. But not as bad as before. Personally I still don't like it

    To disable all , it's --selective-sao 0 --no-sao now.

    SAO tends to blur smaller higher frequency details like fine hairs, skin pores, even at typical bitrate ranges. The trade off is slightly more artifacts. But I prefer details > smooth . Some people prefer smooth, that's ok too . You will typically see the blurring for 10bit x265 CRF 23-24 slow as per the OP's scenario , at least on still frames for typical live action sources. In motion, depends on the person.

    But for low to very low bitrates, or "smooth" content like simple cartoons it can be beneficial (but so can a denoiser)

    Those are just generalizations; it's always better to do some tests and check for yourself for your specific sources


    (Handbrake still does not have a 10bit pipeline in 2020. Don't use it if you have a true 10bit source.)
    I switched to Vidcoder since handbrake doesn't allow up scaling I tried no Sao vs Sao on one video and I couldn't see any difference (crf 23 slow) to be honest.. I'll have to do more test.
    Thanks.
    Quote Quote  
  11. Originally Posted by Felow View Post
    I switched to Vidcoder since handbrake doesn't allow up scaling I tried no Sao vs Sao on one video and I couldn't see any difference (crf 23 slow) to be honest.. I'll have to do more test.
    Thanks.

    Did your source have fine details to begin with ? The difference will be more noticable on higher quality sources with higher frequency, fine details
    Quote Quote  
  12. Originally Posted by Selur View Post
    it's totally unclear what qualifies as 'high bit rate applications' (resolution, settings, content are all unknown)
    For sample previews, check my YouTube channel. (I keep higher quality versions locally)

    After various testing I choose to stick with x264 as x265 actually yielded worse result (both efficiency and quality wise) for my usage. (maybe because I don't know how to use x265... more likely because x264 works too good for me)
    Quote Quote  
  13. Looked channel, no details about resolution and settings.
    -> it's probably best Felow tries with his content and decides for himself.
    users currently on my ignore list: deadrats, Stears555
    Quote Quote  
  14. Originally Posted by Selur View Post
    ...no details about resolution and settings.
    What I was using (for quality export):
    Code:
    ffmpeg -i "%INPUT%" -c:a aac -b:a 320k -c:v libx264 -r 30 -preset placebo -tune film -crf 19 -x264-params "level=5.1:keyint=150:qcomp=0.75" -pix_fmt yuv420p -sws_flags spline+accurate_rnd+full_chroma_int -vsync vfr -color_range 1 -colorspace 5 -color_primaries 5 -color_trc 6 "out.mp4"
    %INPUT%: RGB24, 30 FPS VFR

    Input resolution: 5120x1440, 2560x1440, 1920x1080



    Note: I use different commands for YouTube uploading and quality export.
    Quote Quote  
  15. I have made a more meticulous test and the difference is negligible so I'll just stick with SAO enabled here is the comparison: https://imgur.com/a/sajWHXh
    Quote Quote  
  16. Originally Posted by Felow View Post
    I have made a more meticulous test and the difference is negligible so I'll just stick with SAO enabled here is the comparison: https://imgur.com/a/sajWHXh

    That would be acceptable for me too.

    But it's a lower quality 5Mb/s 1920x1080 source. There are already compression and banding artifacts; high frequency details are already missing in the source (essentially it's already been pre blurred or lowpassed, so there is not much to lose)

    When people complain, it's usually a higher quality source that loses significant fine details after encoding
    Quote Quote  



Similar Threads