HandBrake

Quicksync test encode with h265 results in a freeze. There are no extra options in use. HandBrake 1.0.0 (2016122400) - 64bit OS: Microsoft Windows NT 10.0.14393.0 - 64bit CPU: Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz Ram: 16250 MB, GPU Information: Intel(R) HD Graphics 630 - 21.20.16.4551 NVIDIA GeF...

vbv-maxrate doesn't work either, ref-dist higher than 3 as well. So basically all advanced settings are broken/not working for QSV H265. Nothing new actually, it never worked. Which makes H265 QSV only useful for noobs that won't touch any settings except for bitrate and encoder preset. HandBrake Ni...

Unfortunately Handbrake is still bugged when using advanced options with h265 QS, it just freezes. HandBrake Nightly 20161217232237-77bdefe-master (2016121801) - 64bit Version OS: Microsoft Windows NT 10.0.14393.0 - 64bit CPU: Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz Ram: 16250 MB, GPU Information: ...

This is Handbrake out of the box. The only things I changed are the codec, preset and bitrate.

Sure. HandBrake 0.10.5.0 - 64bit Version OS: Microsoft Windows NT 6.2.9200.0 - 64bit CPU: Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz Ram: 16250 MB, GPU Information: Intel(R) HD Graphics 630 - 21.20.16.4551 NVIDIA GeForce GTX 1080 - 21.21.13.7595 Screen: 1920x1080 Temp Dir: C:\Users\Michael\AppData\Loc...

There is something broken. Look at the difference. Latest nightly CPU Load= 80-85% Speed= 109 fps Latest official CPU Load= 3% Speed= 250 fps Same settings and video sample. Latest official works as expected. This is a video sample I'm using for several years, I know exactly how it should behave wit...

During encode. It isn't normal, it is abnormal. Here is a scan of a QSV H264 encode process. Hardware decoding doesn't seem to work in last nightly which results in a 80% CPU load and encoding speed is very slow. Same for h265. Latest official works fine, although there is no h265. HandBrake Nightly...

HandBrake supports QuickSync H.265 and 4. But it is useless with Handbrake, there are too many issues with Handbrake using H265. One big issue is the broken decoding, CPU load close to 100% while using a hardware decoder is useless. H265 with Quicksync on Handbrake never was a usable option. I was ...

Numerous tests from my side based on a GTX 970. The same applies to Quicksync. From a performance/quality perspective x264 is inefficient on a fast Intel Quadcore. I meant ultra fast by the way. Slower than the hardware solution from Nvidia and even more Intel. X264 ultra fast is just crap in qualit...

It's not that simple. On a i7-6700k x264 very fast is slower than NVENC and looks much much worse.

Hardware SDK as well?

I didn't ask for encode, scan log don't need this. HD 530 is detected, for some reason API version isn't (as expected). I would try to install Intels Media 2016 SDK to see if it can find at least the software version and also check if libmfxhw dll exists in the Media SDK folder (the one from the gra...

Your scan log is useless, you have to load a video. I have almost the same system with an i7-6700k, GTX 970 and Windows 10 and Handbrake detects Quicksync perfectly fine. This is a proper log. HandBrake 0.10.5.0 - 64bit Version OS: Microsoft Windows NT 6.2.9200.0 - 64bit CPU: Intel(R) Core(TM) i7-67...

Where can I find the advanced query field? I don't see it anymore.

The freeze issue with HEVC doesn't seem to appear with Quicksync decoding enabled, and runs faster. Speed is on par with QSVEnc. There is still no ICQ support, only CQP and seeking of HEVC QS converted videos remains slow, 10 seconds mostly. Obviously they are not interested anymore. Wasted effort f...

NVENC Encoding spectrum is more limited than Quicksync, for example there are no Target level options or something similar. To answer your question, no it can't match x264 encoding spectrum. Encoding speed of my GTX 970 with NVENC 5.x isn't much different to my SKL GT2 @6700k h264, although I think ...

Also note, x264 has a wide range on the encoding speed spectrum. At two extremes on my Intel 4770K, I've had it running at <1fps all the way up to just over 2000fps. (yes, two thousand but obviously massive penalties for doing that.). On very fast x264 presets quality is worse than Quicksync.

Woodstock wrote:If you're referring to the GPU on the nVidia card, it is not significantly faster than using the CPU.

It is much faster if you are using a Maxwell GPU and encoding software with NVENC support.

Because gop-pic-size=0 and gop-pic-size=256 is the same, both do use Intels default 256. If you don't use one of them Handbrake uses fps=gop....results in a much worse video quality usually.

For better quality use gop-pic-size=0 or gop-pic-size=256

I've tried tried this all, this is not the reason for the huge difference. There is a big performance (and stability) issue on Handbrake side. I would check if Handbrake really uses TU7 on Skylake HEVC when it is used and log confirms it, TU7 isn't faster than TU4. 90 fps is the limit not matter wha...

As Intel says:

HW Accelerated HEVC Encode supports only CQP, CBR, VBR and ICQ rate control methods.

ICQ works fine as long as the app support it like QSVEnc.

I noticed Handbrake is limited to CQP for HEVC unlike AVC where it uses the better ICQ bitrate mode.

QSVEncC does the job with 150 fps and instant seeking.

Same with TU4. Another anomaly: TU4 runs faster than TU7 in Handbrake. Seeking of these videos are very slow, I have to wait 10 seconds. http://fs5.directupload.net/images/151121/9bitimjy.png HandBrake Nightly 20151110232157-6b713ad-master (2015111201) - 64bit Version OS: Microsoft Windows NT 6.2.92...