Hello, I have severl pc’s I have been trying to get hardware encoding to work, 1 nuc 1 beelink same chipset and a older dell laptop.
None of them will seem to work.
I think at this point I need to concentrate on the nuc,
I tried the drives listed but they will not install as nuc has the iris plus 655 and its not installing the drivers.
I tried 3 of the 27 drivers from intel, and none will use qsv they fall back to ffmpeg, and seem to be cpu.
Here are my intel HEVC MKV profiles I use on my NUC. One uses ffmpeg and the other Handbrake. Personally I feel like I get better results with the Handbrake one.
[HEVC MKV Intel handbrake]
Description=HEVC in MKV to use Intel hardware encoding in Handbrake.
order=handbrake
DisableEncoderReordering=true
AllowAllCopyRemuxing=true
handbrake-UsingHardwareEncoding=true
handbrake-DisableSoftwareEncoderFallback=true
handbrake-general=-v=2
handbrake-video=--comb-detect=Default --decomb=Default --auto-anamorphic -e qsv_h265 --encoder-preset quality -q 26 --cfr
handbrake-audio=-E copy --audio-copy-mask ac3,eac3,truehd,dts,dtshd,mp3,flac --audio-fallback ffac3 -R auto
handbrake-audioac3=-E copy -R auto
handbrake-ext=.mkv
handbrake-audiodelay=skip
[HEVC MKV Intel ffmpeg]
Description=HEVC in MKV to use Intel hardware encoding in ffmpeg.
order=ffmpeg
DisableEncoderReordering=true
AllowAllCopyRemuxing=true
ffmpeg-UsingHardwareEncoding=true
ffmpeg-DisableSoftwareEncoderFallback=true
ffmpeg-general=-threads 0 -v verbose -hwaccel qsv
ffmpeg-video=-vf yadif=0:-1:1,hqdn3d -pix_fmt qsv -c:v hevc_qsv -preset slow -global_quality 26 -look_ahead 32 -vsync 2 -map 0:v -sn
ffmpeg-audio=-c:a copy -map 0:a
ffmpeg-audioac3=-c:a copy -map 0:a
ffmpeg-ext=.mkv
ffmpeg-audiodelay=skip
Thank you, so I copy these to my profiles config?
Thanks, Eric
OK, so it is using handbrake, and I am watching the gpu so it is using that, I am getting about 30-35 fps, how can I increase the speed. I really appreciate your help, it is already better than It was.
Should I only do 1 concurent? currently I have it set to 2 but for my testing I am running 1.
Yes, i see that now, lol but its so slow. and it falls back to ffmpeg?
If I use the handbreak application it is much much faster, I guess thats why I thought it was not working.
I am trying to understand how to speed it up. and why Handbreak fails
Thanks, Eric
I recommend only running 1. I get about 30-35 fps on mine also. With all the testing I did it’s the best I was able to get. You can try the ffmpeg profile and see if it is faster. Ensure that in the BIOS you’ve allocated as much memory as you can to the video. Mine only allowed max of 1GB. The only other thing you can adjust is the --encoder-preset parameter in the Handbrake config. Your options are quality, balanced or speed. Test these out, find your acceptable quality threshold and go with that preset. The other thing to play with is the -q parameter, you can try a higher number for lower quality. This affects speed a little but more affects file size output.
So I have seen why the handbrake is failing it is the quality setting in the hevc profile, if i remove the medium it works, however it still runs at 30-35 fps.
when it fails over to ffmpeg im getting 77 fps, better.
I set the ffmpeg to be first in the profile for now so it runs better, am i leaving something out? I see other nucs older than mine getting 120 or more.
is anything in the settings holding back the speed?
I still have to check the memory for the video, I am not home right now to physically check the bios.
Thanks, Eric
Correct, in Handbrake for Intel the quality settings are speed, balanced and quality for the HEVC encoder. Since medium (equivalent of balanced) doesn’t match a quality setting it will fail and move on to ffmpeg which does support medium as the quality setting. Since each application has it’s own settings for how it encodes, filters and processes video and audio I can’t tell you why in your case ffmpeg is faster or if it is even doing the equivalent of what Handbrake is attempting to do.
I can’t tell you why some NUCs are getting such good processing without knowing what parameters they are passing or which application they are using for processing. All I can tell you is that there are a lot of parameters to play with for both applications and you have to spend time finding which ones work best for you. Both applications have decent documentation and there is a lot of online content related to tweaking the parameters for the best result. It’s really an endless pursuit because you can have great results and feel like you finally have it locked in and a driver update can completely destroy it.