HandBrake

I have a sneaking suspicion that it won't work without the ARC gpu being the primary card in the system. (In the first PCI-E slot) Are you able to test that theory?

Please include the log header as it contains GPU / driver information that's relevant.

It looks like your CPU is currently the limiting factor here. I'm not entirely sure why it's not using fullpath encoding for you. That would reduce CPU utilisation down. There is no obvious reason for that. Might have something to do with it being lower-end UHD 730 onboard. That said, I've had mixed...

You've hit a fairly nasty bottleneck. Your ARC isn't performing anywhere near what it's capable of on it's own. When you add HyperEncode in, it has overheads. Thus, if your already bottlenecked before, it'll make the bottleneck situation worse. Do you have ReBAR enabled in your BIOS? Can you post an...

This isn't a bug. The Intel document is a little mis-leading due to how they've structured the page. The settings shown, are not for HyperEncode. The handBrake QSV presets won't use HyperEncode. If you start with one of them, you'll need to change the following setting: On the video tab, you need to...

You can't force it. It decides automatically whether to use it, or not.

You may want to try a development snapshot build. https://github.com/HandBrake/HandBrake-snapshots

Quite a few improvements to QSV framework since 1.6 released.

Please ask the HandBrake Batch author for support. It's a 3rd party app not developed by us and not something we support.

https://github.com/HandBrake/HandBrake/commits/master is better to read changes.

The PPA releases have been retired for some time. The Flatpak releases are now the official builds for Linux.

Automatic these days is "smarter" than median. It will fallback to conservative cropping if it detects mixed aspect content to yield the least amount of cropping for the samples taken. For many cases that will stop mixed AR content being overcropped. Conservative is better if you know it's...

Upgrade to a recent version. Autocrop was expanded in 1.6 to cover more cases. IT has conservative mode and automatic will try handle mixed ratio content better. That said, there are limitations and those won't ever go away. There is a preview window for fine adjustments. The summary tab was never i...

The sample you uploaded is video only. Even then, the video appears to be a bit of a mess. (Not Unsurprising. It's quite common with camera devices. Their output is often unusable junk. Had to deal with this myself.) I'm guessing there was maybe a plugin installed to allow WMP to play this as it won...

https://dotnet.microsoft.com/en-us/down ... -installer

Your install of .NET is corrupted. Try the link above. You might want to fully remove the installs first.

If all your doing is hardware based media encoding on it, I'd stay with Intel personally. Nvidia might be faster in some cases but I find the quality of the output to be a bit "meh" and soft. Another thing to note, your 770 can do AV1 encoding. Your CPU onboard QSV cannot. B-Frames will af...

You can try a different video preset, or try a 4K file with it.

Unfortunately, when it doesn't enable, it doesn't tell us why but it's ultimately correct that it sometimes won't enable.
The log shows it was requested.

With those settings I don't believe it will invoke HyperEncode. HyperEncode only kicks in in situations where it will actually make encoding faster. You may also want to make sure the framerate is same as source, VFR or PFR on the video tab. You may also want to use a slower video preset on the vide...

Please provide a full encode log.

The 12900KF (KF) has no graphics. So no QuickSync.

QSV > NVEnc a lot of the time. Typically not faster though.

> I'll retest both, by the way if they return worse quality I think they are pretty useless... It depends. For most, it's close enough that it doesn't matter, even if the file is a bit bigger to compensate but if you want the best quality, stick with software and just tune the settings for more tole...

You need to choose the NVenc encoder on the video tab. x265 is a software encoder that implements the h265 standard. NVENC (H265) is a hardware encoder that implements the same standard. They are not the same. Using NVENC, your trading worse quality/files for, usually, faster encodes.

" enabled Nvidia NVEnc support" > what do you mean? Enabling in preferences is not sufficient for it to be used. Did you actually choose the NVEnc encoder?

I'm just surprised that the RTX was completely useless, it's reported as the fastest hardware encoder, but in the truth there's no improvement compared to a regular software encoder on Core i7. I'm still not sure this is normal... The log above showed you used x265(software encoder), not nvenc. NVE...

My handbrake only allows me to encode 3 Jobs simultaneously, although I have set it in settings to 5. Have newest Nvidia driver and handbrake Version. Any idea what the problem is? Current version of HandBrake is restricted to 3. Future versions will allow 5. I have about 30% GPU load then and the ...

1. Not 100% sure as we don't have 4000 series cards to validate but I believe it's 2 encodes rather than 1 faster. 2. Nope. It's 5 maximum, regardless of whether you have 1 or 2 NVEnc engines. This applies if your on the latest drivers. Older drivers had 3 limit. The number is kind of moot as a sing...

The docker image is not official and not supported by us I'm afraid.