Would love to beta test. I’m already a donator…
via Newton Mail
1 Like
You can try out the latest 2.4.8 BETA build with the new ffmpeg and let me know it goes for nvenc encoding (hevc and x264).
Also I don’t think nvenc supports the -crf parameter if I’m correct, but you can try it out and let me know. See your logs for what you get.
Try using -cq instead of -crf and let me know if that works. Our nvidia machine fried itself so until we get a replacement, looking for some testers 
(or if anyone’s willing to donate a NVIDIA pascal machine to us).
I’ll update and see. I did try cq in a previous iteration of my profile. The ffmpeg documentation is not exactly clear, but the NVidia documentation for their extension did mention crf vs cq for constant quality. Regardless, for most encodes, I can do an hour long show in about 10 minutes
1 Like
You can query ffmpeg for the list of available options for each encoder, here’s what shows for h264_nvenc
As you can see there are 2 options -cq (which is what we want, constant quality) and -qp (which is NOT what we want as that’s a constant quantizer which is pretty useless).
You may need to set -rc vbr also but it you can try it out with and without it and let me know how it goes.
-rc E…V… Override the preset rate-control (from -1 to INT_MAX) (default -1)
constqp E…V… Constant QP mode
vbr E…V… Variable bitrate mode
cbr E…V… Constant bitrate mode
vbr_minqp E…V… Variable bitrate mode with MinQP
ll_2pass_quality E…V… Multi-pass optimized for image quality (only for low-latency presets)
ll_2pass_size E…V… Multi-pass optimized for constant frame size (only for low-latency presets)
vbr_2pass E…V… Multi-pass variable bitrate mode
-rc-lookahead E…V… Number of frames to look ahead for rate-control (from -1 to INT_MAX) (default -1)
-surfaces E…V… Number of concurrent surfaces (from 0 to 64) (default 32)
-cbr E…V… Use cbr encoding mode (default false)
-2pass E…V… Use 2pass encoding mode (default auto)
-gpu E…V… Selects which NVENC capable GPU to use. First GPU is 0, second is 1, and so on. (from -2 to INT_MAX) (default any)
any E…V… Pick the first device available
list E…V… List the available devices
-delay E…V… Delay frame output by the given amount of frames (from 0 to INT_MAX) (default INT_MAX)
-no-scenecut E…V… When lookahead is enabled, set this to 1 to disable adaptive I-frame insertion at scene cuts (default false)
-forced-idr E…V… If forcing keyframes, force them as IDR frames. (default false)
-b_adapt E…V… When lookahead is enabled, set this to 0 to disable adaptive B-frame decision (default true)
-spatial-aq E…V… set to 1 to enable Spatial AQ (default false)
-temporal-aq E…V… set to 1 to enable Temporal AQ (default false)
-zerolatency E…V… Set 1 to indicate zero latency operation (no reordering delay) (default false)
-nonref_p E…V… Set this to 1 to enable automatic insertion of non-reference P-frames (default false)
-strict_gop E…V… Set 1 to minimize GOP-to-GOP rate fluctuations (default false)
-aq-strength E…V… When Spatial AQ is enabled, this field is used to specify AQ strength. AQ strength scale is from 1 (low) - 15 (aggressive) (from 1 to 15) (default 8)
-cq E…V… Set target quality level (0 to 51, 0 means automatic) for constant quality mode in VBR rate control (from 0 to 51) (default 0)
-aud E…V… Use access unit delimiters (default false)
-bluray-compat E…V… Bluray compatibility workarounds (default false)
-init_qpP E…V… Initial QP value for P frame (from -1 to 51) (default -1)
-init_qpB E…V… Initial QP value for B frame (from -1 to 51) (default -1)
-init_qpI E…V… Initial QP value for I frame (from -1 to 51) (default -1)
-qp E…V… Constant quantization parameter rate control method (from -1 to 51) (default -1)
Thanks for the above - I was pulling the commands from NVidia’s developer site - it seemed like it exposed a subset vs FFMPEG overall - I also noticed from some of the logs that hevc_nvenc is the new name for the encoder and that nvenc_hevc has been deprecated.
So I’ll try this modification to the encoding profile:
[----------------------]
[MKV HVEC Constant Quality]
Description=WARNING: Handbrake Constant Quality encoding (25) with Nvidia HVEC.
order=ffmpeg, handbrake
AllowH264CopyRemuxing=true
FixedResolution=true
AutoDeinterlace=true
ffmpeg-UsingHardwareEncoding=True
ffmpeg-general=-threads 0 -hwaccel auto
ffmpeg-video=-ss 9 -c:v hevc_nvenc -cq 25 -rc vbr -map 0:v
ffmpeg-audio=-acodec ac3 -ab 192k -map 0:a
ffmpeg-audioac3=-acodec ac3 -ab 384k -map 0:a
ffmpeg-ext=.mkv
ffmpeg-audiodelay=skip
handbrake-UsingHardwareEncoding=true
handbrake-general=--decomb --denoise="weak" --loose-anamorphic --verbose=2 -T -O
handbrake-video=--start-at duration:3 -e x265 -q 18
handbrake-audio=-E ffac3 -R auto -B 192 -D 0 -a 1,2,3,4,5
handbrake-audioac3=-E ffac3 -R auto -B 384 -D 0 -a 1,2,3,4,5
handbrake-ext=.mkv
handbrake-audiodelay=skip
PreConversionCommercialRemover=true
2 Likes
Vary the -cq numbers and see if the quality changes.
I did. I pushed it from 25 to 23. Marginally better. I think the vbr makes as much difference as the rest.
via Newton Mail
Try extremes like 5 or 40
I tried 18 and down - at that point there’s a very marginal savings in compression (300 megs on a 1.3gig file). 23 seems to be the right sweet spot for HEVC CQ.
If I understand the concepts here correctly with the last profile listed.
If I make -cq a larger integer, the compression is less efficient (i.e. larger file).
Does it make the encode any faster or degrade the video quality per se?
Yes. That’s right. It’s also a non-linear scale. The bigger the number, the bigger the file. If you know anything about handbrake or h264, cq20 is equivalent to cq23 in hevc. Thanks! Will.
The file is less complex, so it’s marginally easier to encode / decode. That said, you will notice a difference in video quality. If you record a lot of sports, or other fast motion content, you should skew lower. Good luck!
So first of all, great H265 profile, it performs very well with a Quadro card as the HW encoder source!
Second, I have been toying around with this profile and have been trying to create a H264 version of the dedicated encoder using ffmpeg, but have been having some syntax issues getting it to actually process, any chance you/anyone has been experimenting with this?
The reason behind the desire is to create a faster profile but with constant quality for shows that does not require long term storage like sports, jeopardy etc that will be watched once, perhaps twice and then will be gone for the most part, to save time on the nightly transcoding compared to longer term stored files like TV shows, movies etc.
Thanks - I totally understand the pain of trying to decode the ffmpeg commands - the documentation is… terse.
You want to replace HEVC_nvenc with h264_nvenc. Remember that the constant quality is different between 265 and 264. The “default” for 265 is 23, while the default for 264 is 20.
Hope this helps! WIll.
1 Like
Thanks mate, I tried that, but it seemed fall back to the handbrake Cli option no matter how I twisted the syntax. I read a ton on the, as you say terse, documentation, so true btw!, and found a ton of info concerning the options for the h264_nvenc encoder that appeared to be different than those of the HEVC one in the current version(s) of ffmpeg
I can post a copy some test profiles tomorrow when I get a chance if you are up for helping with some troubleshooting to get the profile to work. At the moment I am relying on alterations of the builtin h264 profiles based on the libx264 encoder which certainly can utilize the HW acceleration, but I would like to build one purely built on the HW encoder a la the one you made for HEVC
Happy to try to help. One thing to start with is to open a command line and run “FFMpeg.exe -codecs”. That will show which codecs are available to you in FFMpeg.
For the handbrake failback, I know recent versions of Handbrake support nvenc, but am not sure if handbrakecli.exe can just be replaced. Will do a little more digging.
Thanks! Will.
Thanks mate, appreciate it,
As for the Handbrake fall back, the newest version of the GUI version does support NVENC, with great performance I might add!, however the fallback refers to pure CPU based x264 encoding with no HW enhancement at all.
Will get more details tomorrow and test some command line options as well.
Thanks!
Updated: (not allowed to post more than three replies in the same thread as new user 
)
So I got the syntax to work, guess I was too tired to get it right initially, but this is how I got it to work by si,ply doing as you said and replace HEVC with h264 and keep the rest the same:
[MKV H264 NVENC Constant Quality]
Description=nVidia H264 NVENC Constant quality, varible bitrate
order=ffmpeg, handbrake
AllowH264CopyRemuxing=true
FixedResolution=true
AutoDeinterlace=true
ffmpeg-UsingHardwareEncoding=True
ffmpeg-general=-threads 0 -hwaccel auto
ffmpeg-video=-ss 9 -c:v h264_nvenc -cq 27 -rc vbr -map 0:v
ffmpeg-audio=-acodec libfdk_aac -ab 128k -map 0:a
ffmpeg-audioac3=-acodec libfdk_aac -ab 320k -map 0:a
ffmpeg-ext=.mkv
ffmpeg-audiodelay=skip
handbrake-UsingHardwareEncoding=true
handbrake-general=–decomb --denoise=“weak” --loose-anamorphic --verbose=2 -T -O
handbrake-video=–start-at duration:3 -e x265 -q 18
handbrake-audio=-E ffac3 -R auto -B 192 -D 0 -a 1,2,3,4,5
handbrake-audioac3=-E ffac3 -R auto -B 384 -D 0 -a 1,2,3,4,5
handbrake-ext=.mkv
handbrake-audiodelay=skip
PreConversionCommercialRemover=true
This runs with smooth the NVENC primary encoder,
One question though, do you know the syntax change for constant bitrates rather the vbr and quality based analysis, got a couple of scenarios where I would like to control the bitrate manually.
1 Like
You can download version 1.2 of handbrakecli from here: HandBrake
It integrates nvenc_h264 and nvenc_h265. Maybe try to get Handbrake to do the same…
So been testing the HandBrakeCli with the updated version and it works with NVENC, do you have any knowledge about options or if it is possible to point to a exported .json file for configuration through the MCEBuddy profiles?