HandBrake

Ah, Sorry, I mis-read your initial post. I'm not sure if Ryzen has AVX multiplier options or not, but you may want to check the bios. Failign that, try backing off to 4.1 or 4.0 and if you can, reduce the voltage a bit. It's on the high side for that chip which will be good part of the heat your see...

Replace years with decade

Officially, support was Dropped in official releases in November 2008, making that 10 years ago now.

timberflake, This is actually expected. HandBrake uses a CPU heavily, more so than most benchmarks. In particular AVX workloads tend to show an overclock isn't stable. AVX implementations on CPU's tend to be quite power hungry hence your higher temps Some motherboards may allow you to set the multip...

Sadly not, If only we disposal income!

In theory, it should just work when we drop the video toolbox patch in but we won't really know how good or bad it is.

... 3 of you asking for the same thing. One is enough thanks.

He's using Windows I suspect.

The Mac Builds do not yet have QuickSync support enabled.

My guess if SFC found problems, and wasn't able to repair them, there is a good chance it's related to this problem. A corrupted Operating system isn't good. I'd maybe suggest trying one of the Microsoft or populate windows tech forums to see if folks can better help. It's probably going to involve ...

@Melon_life It's not only the bitrate, but essentially none of the config options are available. So It's really not utilising Quicksync to it's full potential.

I'd be surprised if the T2 hardware isn't much more capable than the software allows.

At some point in the near future, we are looking at adding an option to force QuickSync to use DirectX9 rather than 11 to improve another situation where there is issues. I don't think it'll resolve this but it may make it less likely to occur. Unfortunately, given these parts are discontinued by In...

You'd have to use a 3rd party image hosting site. It should tell you that it completed successfully and if there are any errors, I expect it will offer to resolve them.

Failing that, Do you have RivaTuner, MSI Afterburner or any similar software installed?

VLC is a very popular media play https://www.videolan.org/ which an awful lot of folks use. If you don't use that, that's fine, use the system-option as it'll use whatever is default on your system.

I'll correct the erroneous message for the next release. Thanks

It's probably an issue that was fixed a few months back. Older versions of OSX don't render HandBrake correctly.

Try a nightly build: https://handbrake.fr/nightly.php

Unfortunately, it's not a helpful error. My guess is there is some kind of missing or corrupted system file, maybe a bad graphics driver that's triggering this You might want to try running the system file checker (command line sfc) and making sure your fully up-to-date with drivers etc. Can you als...

Is there anything in the Windows Event Viewer under Windows Logs > Applications at the timecode you run this?

I'm not saying it's not a HandBrake Bug, it is.

When installing, becareful that you don't uninstall it after you've installed it.

The prompt on the installer to uninstall, sometimes hides behind the installer so it's easy to inadvertently run that after installing.

It's not an Nividia driver issue. It will require a code change in HandBrake to write this.

There is no way to disable the libav aac encoder option in the GUI.
./configure --help should list all the options.

@schinivision -> There is nothing you can do to force this. It requires a code change in HandBrake. It's being worked but if it fixes it, then the TV firmware is also buggy. And sadly, no firmware updates for my slightly older Samsung TV. Unfortunately, it's h.264 playback is completely broken and w...

The lack of metadata should be irrelevant. You could try the different nvenc presets to see if any of those work. It's more than likely a specific h.264 feature your TV doesn't support, or simply has broken support for. Personally, I gave up on my Samsung TV playing video. It's massively fussy. Sett...

@hanumang -> Remember, decode, filters, audio, libhb etc are all CPU, regardless of T2 chip. So a weak CPU may bottleneck the the chip.

(That's assuming it's even any good)

threads is an x264 option which only limits the encoder, not HandBrake. You can manage CPU affinity of processes through the windows task manager, but do note, limiting to 1 CPU core can cause much higher clock speeds on that core and land you in the same situation. Better off just fixing the cooling.

It works exactly as it has done in the past.

See the docs for a guide: https://handbrake.fr/docs/

Sorry, we don't support 3rd party builds of HandBrake on Linux.
Please see https://handbrake.fr/docs/en/latest/get ... brake.html

There are no plans currently to add gui support or enable by default. If someone wants to put a bit of work into this patches are welcome but we rarely see outside contributions for Linux.