A good config for StaxRip 2019?

[ZeroCool22]

I just found this awesome converter and i was looking for a good guide/settings for h265 Nvenc, i searched trough all places and i only found outdated configs, someone could do/share a updated config please?

Thx in advance!

My GPU: MSI 1080 TI Gaming X
Nvidia Drivers: 436.48

These are the settings i usually use (for 1080p encodes):

--cqp 21 --codec h265 --preset quality --profile main10 --output-depth 10 --aq --ref 16 --gop-len 600 --lookahead 32 --strict-gop --cuda-schedule auto --vpp-edgelevel strength=10,threshold=15,black=5,white=1 --vpp-deband --mv-precision q-pel --cabac

[videoh]

What do you mean by outdated and how would we know if an "updated config" is good enough for you?

[Forteen88]

I don't know much about NVENC, but I know that for quality with H.265, you should be sure to set "Depth" to 10-Bit (and Profile "Main 10", I think), because most GPU:s can decode H.265-video at 10-bit.
16 B-Frames and 6 "Ref frames" should be set too (maybe only 5 "Ref frames" for 4K resolution or higher, to keep GPU-decoding compatibility).

[Blue_MiSfit]

If you must use NVENC then you should have a Turing generation GPU. This generation has pretty good encoding quality (for a hardware encoder, anyway).

[benwaggoner]

Originally Posted by Forteen88

I don't know much about NVENC, but I know that for quality with H.265, you should be sure to set "Depth" to 10-Bit (and Profile "Main 10", I think), because most GPU:s can decode H.265-video at 10-bit.
16 B-Frames and 6 "Ref frames" should be set too (maybe only 5 "Ref frames" for 4K resolution or higher, to keep GPU-decoding compatibility).

Do you have any data showing 16 b-frames as being helpful? In past HW encoders, too many could actually make things worse if the I/P/B frame type decision logic wasn't great.

[Forteen88]

Originally Posted by benwaggoner

Do you have any data showing 16 b-frames as being helpful? In past HW encoders, too many could actually make things worse if the I/P/B frame type decision logic wasn't great.

No, I don't have actual data, it's just that in theory it should be better to allow for more b-frames.
OK, it's better to test that.

[ZeroCool22]

Originally Posted by Forteen88

I don't know much about NVENC, but I know that for quality with H.265, you should be sure to set "Depth" to 10-Bit (and Profile "Main 10", I think), because most GPU:s can decode H.265-video at 10-bit.
16 B-Frames and 6 "Ref frames" should be set too (maybe only 5 "Ref frames" for 4K resolution or higher, to keep GPU-decoding compatibility).

Hey thx for the answer, yes, infact i always use Main 10 & 10 Bits for the encodes. I would like to try 12 Bits but seems like Staxrip can't do it yet for H265.

[ZeroCool22]

Originally Posted by videoh

What do you mean by outdated and how would we know if an "updated config" is good enough for you?

By outdated, i mean there are settings guides that are old and don't have all the new options of the lasts Staxrip versions:

For ex. searching for guides, i found:

https://www.youtube.com/watch?v=2OselaN9v9k

https://forum.videohelp.com/threads/...-%28Staxrip%29

https://www.google.com.ar/search?sxs...10.bKn_F5ZFw8c

But no one guide for Staxrip for H265 on 2019.

[ZeroCool22]

BTW, someone know if there is some command to be able to endoce with H265 at 12 Bits with Staxrip?

[RanmaCanada]

Originally Posted by ZeroCool22

BTW, someone know if there is some command to be able to endoce with H265 at 12 Bits with Staxrip?

Pick x265 as you encoder. In the encoder window, go into options, Basic, and bit depth.

You need to use x265 as nvenc does not support 12 bit. There is no hardware support for 12 bit outside of PC, so any other devices you attempt to play your encodes on will use software rendering, which will typically bring them to their knees.

[ZeroCool22]

Originally Posted by RanmaCanada

Pick x265 as you encoder. In the encoder window, go into options, Basic, and bit depth.

You need to use x265 as nvenc does not support 12 bit. There is no hardware support for 12 bit outside of PC, so any other devices you attempt to play your encodes on will use software rendering, which will typically bring them to their knees.

x265 will take hours to encode, i will stick with H265 at 10 Bits, using the GPU, but thx.

[RanmaCanada]

Originally Posted by ZeroCool22

x265 will take hours to encode, i will stick with H265 at 10 Bits, using the GPU, but thx.

Ok, so you want garbage/bloated encodes. Gotcha!

[Santojob]

Using H265 with Nvenc is a quick way to code at a fairly acceptable quality. New possibilities for improvement are being implemented with the new versions of NVENC. Is there an expert who can tell us what new parameters to include to improve?

My parameters:

--vbrhq 6000 --codec h265 --preset quality --profile main10 --tier high --level 5.1 --output-depth 10 --aq --lookahead 32 --nonrefp --cuda-schedule auto --vpp-edgelevel --vpp-deband

[Forteen88]

Originally Posted by RanmaCanada

Ok, so you want garbage/bloated encodes. Gotcha!

Not being able to GPU-decode 12bits-encodes is crappy too though, so I'd stick with 10bit x265-encodes.
EDIT: Oh, I assumed that "using the GPU" meant GPU-decoding, not GPU-encoding.

[craigpro]

from following the suggested settings at http://aerobytepc.com/index-html/nvi...ware-encoding/ , my command line output looks like this:

--cqp 18:20:22 --codec h265 --preset quality --output-depth 10 --qp-init 20 --qp-max 22 --qp-min 18 --aq --aq-temporal --gop-len 240 --lookahead 16 --slices 2 --multiref-l0 4 --multiref-l1 4 --strict-gop --nonrefp --weightp

[benwaggoner]

Originally Posted by Forteen88

Not being able to GPU-decode 12bits-encodes is crappy too though, so I'd stick with 10bit x265-encodes.

12-bit decode is supported in the last generation or two of NVidia GPUs, IIRC.

A full "Native" version of Dolby Vision would be 12-bit, although I'm not sure how much materially better that would be over Profile 5 with its dynamic coding ranges.

Sent from my SM-T837V using Tapatalk