HandBrake

Since this thread is going round in circles, let me end it by this: Your options are as follows: 1. Speak to the folks behind Twonky and see if they'll fix the issue. Don't assume they won't help because a change in HandBrake triggered a dormant issue. It's only fair to give them a chance to respond...

But the guy is looking for tips on quality settings, not support.

That's literally asking for support ...

Regardless, knowing exactly where a user started and understanding what happened with existing settings allows one to better derive changes that would improve things.

Not on that operating system version. It’s too old. You’d need to use Flatpak builds

If the CPU Supports it, yes

If you read carefully, the recommendations for Quality level are for the x264 software encoder. Not NVEnc H264 There are no recommendations available for NVEnc and note that the scale is not the same. Apart from Rate Control, HandBrake uses default settings for the encoder. We don't change anything....

It'd only reach that kind of level if something was preventing cleanup.

You'd need a mac equivalent to windirstat to easily find what's eating the space.

setting up affinity doesn't even work as it'll just reset, possible to find out why? also would HB team please consider adding it in the future? It's something about your environment so it's not something we can look into. This doesn't happen for most people. We already have the Process Priority dr...

Not with HandBrake.

HandBrake has no code to change CPU affinity settings. Only priority. There must be something external of HandBrake that's tampering with the process.

baseline main and high are just standard H.264 profiles also listed in the link above.

H.264 Levels: https://en.wikipedia.org/wiki/Advanced_Video_Coding#Levels We don't have any documentation on the encoder presets, so it's essentially a blackbox. That said, the hardware is very limited so I doubt they really do an awful lot. P.s if your hitting 78C on a 2600, you might want to take a...

We use Nvidia's presets, minus a couple that don't appear to do much, or don't make sense.

Also, any nvenc config option that ffmpeg supports, should be passable via the advanced options box unless we explicitly override it already.

It's coming soon-ish (tm)

Your system is rejecting HandBrakes call to take an exclusive lock on the device. Make sure you don't have any screen capture, gaming, overclocking, overlay tools etc running in the background that might have a handle to the hardware. Might also want to make sure you have a monitor attacked to the I...

@gmb -> Post a log and we can probably give you a clue why.

Just note, QSV only supports decoding a limited number of formats. Also note, that everything between decoding and encoding is all done on CPU and depending on your hardware, could still easily max out the CPU depending on settings used.

@alangstein -> Are you using DNLA by chance and if so, which vendor?

This is such a cop-out answer. If it used to work on earlier versions, and now it no longer works, then the issue is clearly with Handbrake. That would be a cop-out argument. Infact, it's not even an argument since you've not actually backed it up with any proof that HandBrake is at fault here ... ...

Those are the presets Nvidia Created. There is no documentation from them that I'm aware of that actually tell us what the presets do. Their behaviour hasn't changed unless Nvidia has changed them within the drivers. There is still a very minor speed difference although it's less noticeable in 1.3.3...

As far as I understand it, it's supposed to behave more like CRF but I don't believe it's exactly the same. I haven't seen any clear documentation on it to fully understand it.

Don't think so.

Read the port above. Different Rate Control method. (The CQ label is actually wrong on the + line)

[13:32:51] encavcodec: encoding at rc=vbr 21.00 (1.3.1) vs [00:41:38] encavcodec: encoding at rc=constqp QP 21.00 (1.2.2) vbr_hq is a much better rate control method that Nvidia supports. You need to note that the quality scale is not the same between he two though. So 21 has a different meaning to ...

The error message above is irrelevant. It says it on all non nivida systems. Did you clear the log file before loading the GUI as I'd suspect that's an old log if it's crashing on startup. Boot windows into Safe mode, and try again. If that works, it's the interaction with something on your system t...

In all likelyhood, it's either the audio encoder (which you don't appear to be running in ffmpeg) or just the video decoding on the CPU that's holding it back at this point. HandBrake is more than a GUI to ffmpeg, although it does make heavy use of it's libraries along with many others. For transpor...

Not the same workload. 1. There are several CPU only filters running in HandBrake which are not running in ffmpeg. These will defiantly introduce a bottleneck. You can probably turn these off for this particular source. (Decomb, Comb Detect and Framerate shaping) 2. ffmpeg might also be using nvdec ...