Any advice on --tune grain ?

[Emulgator]

Many thanks for that idea !

[benwaggoner]

Originally Posted by Emulgator

Many thanks for that idea !

Let us know if it helps!

[TB54]

Yes, sorry everyone, i have been pretty busy and not able to test serioulsy (with all the variations, differents settings...) the last suggestions, but I will come to it as soon as I have time!

[TB54]

Originally Posted by benwaggoner

Another grain tip: try --hme.

Just this code alone, or followed by a number? It makes handbrake crash if just put it alone in the advanced dialog boxed.

Thanks for all the suggestions, i tried everything, but still don't have a satisfying result (at least if i want to stay around 7Mb/s on the final 720p file).

If anyone wants to try his own solution, here is the very grainy test clip i use in ProResHQ (i know most of sources won't be as grainy as that, but with it I can see more clearly the problem I encounter in a milder way with every other sources): https://we.tl/t-Maamur6Wzm


TO SUM THIS UP (with comparison slides, which don't seem to display on chrome weirdly)...

- If i try h265 "grain", detail is preserved, but the grain is more present/harsher, which in movement makes the movie clip difficult to watch: https://cdn.knightlab.com/libs/juxta...8-ebb5d6f907df

- If i try h265 "none", detail disappear, and it makes a porridge-image on the face movements: https://cdn.knightlab.com/libs/juxta...8-ebb5d6f907df

- Weirdly, the closest to source image (the right amount of grain while preserving some detail) is obtained using h264 "grain": https://cdn.knightlab.com/libs/juxta...8-ebb5d6f907df

... but it doesn't do well on every shot (see the blocks around the guy on this large shot, or his face - you can see the problem more clearly in motion, on the little h264 excerpt I put in the wetansfer): https://cdn.knightlab.com/libs/juxta...8-ebb5d6f907df

If anyone wants to play with it, you're more than welcome, but anyway it is an occasion for newcomers to show the effect of each tune. Thanks again all for your help, and sorry to the long answer delay!

[excellentswordfight]

Originally Posted by TB54

Just this code alone, or followed by a number? It makes handbrake crash if just put it alone in the advanced dialog boxed.

Thanks for all the suggestions, i tried everything, but still don't have a satisfying result (at least if i want to stay around 7Mb/s on the final 720p file).

If anyone wants to try his own solution, here is the very grainy test clip i use in ProResHQ (i know most of sources won't be as grainy as that, but with it I can see more clearly the problem I encounter in a milder way with every other sources): https://we.tl/t-Maamur6Wzm


TO SUM THIS UP (with comparison slides, which don't seem to display on chrome weirdly)...

- If i try h265 "grain", detail is preserved, but the grain is more present/harsher, which in movement makes the movie clip difficult to watch: https://cdn.knightlab.com/libs/juxta...8-ebb5d6f907df

- If i try h265 "none", detail disappear, and it makes a porridge-image on the face movements: https://cdn.knightlab.com/libs/juxta...8-ebb5d6f907df

- Weirdly, the closest to source image (the right amount of grain while preserving some detail) is obtained using h264 "grain": https://cdn.knightlab.com/libs/juxta...8-ebb5d6f907df

... but it doesn't do well on every shot (see the blocks around the guy on this large shot, or his face - you can see the problem more clearly in motion, on the little h264 excerpt I put in the wetansfer): https://cdn.knightlab.com/libs/juxta...8-ebb5d6f907df


If anyone wants to play with it, you're more than welcome, but anyway it is an occasion for newcomers to show the effect of each tune. Thanks again all for your help, and sorry to the long answer delay!

https://we.tl/t-111C1r2CA0

Using the settings recommended previously, playing it back side by side to your source and I would say it looks fine. Way better then the attached h264 version that completely breaks apart in some areas of the image. But 7Mbps is streatching it a bit for this source, had to go to crf22.5 and still ended up a bit over 7Mbps (7,6Mbps).

[TB54]

Thanks a lot !

You mean this code ?

 --preset slow --profile main10 --level-idc 41 --crf 18
--keyint 240 --min-keyint 24 --rc-lookahead 48 --no-sao
--deblock -1:-1 --colorprim bt709 --transfer bt709 --colormatrix bt709 --range limited

Okaaay, i'm stupid; trying to replicate it with crf 22.5, and not achieving the same result as you (even if it's close: i end up on a 32,6 Mo file and 7 192 kb/s) I realize handbrake doesn't seem to take in consideration what i put in the advanced dialog box (don't know why)... That means that all i tried since day one (except the main things, like slow or using 10 bits) didn't have an effect! I'm sorry, that explains why your code didn't look to work for me at first...

I will definitely learn to use ffmpeg directly.

Your result is indeed very good! I still have a little weird feeling on the first close-up on him (this head movement...), but you're right, the bitrate limits us here for such a complex source.

Thanks again, and sorry for the bug :-/


EDIT : for handbrake if someone's interested, it seems to be a syntax problem. I can now achieve something very close to your result (34.8 MiB - 7 684 kb/s)

[benwaggoner]

That's a good chunk of grain in there. Maybe try --nr-intra 150 --nr-inter 500? That'll make it easier to encode and reduce the swirling moving noise. The underlying source isn't that detailed anyway. It'll let you save some bits or reduce QPs.