HandBrake

There is a portable.ini.template file included. Rename it to portable.ini and configure as you wish.
The defaults are probably ok for what you want.

May I ask why you are diving into this level of detail? Unless you plan to distribute HandBrake publicly as a download, it's highly unusual to delve into this level of detail. If you are running/installing the application on a personal, business or corporate machine(s), the terms of the GPL are your...

https://github.com/HandBrake/HandBrake/ ... nformation May also be relevant.

Ultimately HandBrake's GPLv2 takes priroty here. Everything we use internally is a GPLv2 compatible license.

Nope, that's a perfectly normal MP4 file.

My guess is you've got your system file associations set to open MP4 with ClipChamp. You can open an Mp4 with whatever you want that supports it. Should be options on the macOS right click menu to open with other apps.

Your streams all appear to have issues with them as well, so it's having to do an awful lot of additional seeking which seems to be blowing out the amount of time it's taking. It does appear to be getting though it though. I'd be inclined to run them though a stream repair tool before running though...

It's not particularly slow. Encode time will of course vary depending on source resolution / complexity, Settings used and hardware. HandBrake should be fully utilising that CPU without much issue. I'd drop off the Interlace Detection and Deinterlace options on the filters tab unless you know that y...

After starting an encode, grab the encode log from the log window. It may provide a clue as to what's going on.

You need the "Desktop" runtime, not the base runtime
https://dotnet.microsoft.com/en-us/down ... -installer

First of, If you've paid for HandBrake, you've been likely been the victim of a scam. HandBrake is free, open-source software. There is no paid version, nor any account or subscription required to use it. The project also doesn't accept donations. I'd advise you to report this to your payment provid...

Process isolation essentially protects the Main UI from any crashes that may occur when encoding. So if a job fails in an unexpected way, the Main UI will continue orchestrating further jobs on the queue.

Something on your system is blocking the worker process from initialising. Probably a 3rd party security software package / firewall.

You can turn off process isolation in Tools -> Preferences -> Advanced which will bypass this

You'd need the formal AMD GPU Pro driver. I'm not sure if there is any special configuration needed to passthru to flatpak or not.

That said, The GPU in your APU, is not on the list of GPU's we support so you may or may not be able to get it working.

Anyone in the normal registered users group cannot edit posts. It's turned off to limit spam/abuse.

CPU: 13th Gen Intel(R) Core(TM) i9-13900K https://www.pcgamer.com/hardware/processors/intel-cpu-crashes-what-you-need-to-knowmicrocode-to-blame-but-fix-incoming-this-month-alongside-two-year-extended-warranty/ Sounds like you've fallen foul of this Intel CPU drama with teh 13th and 14th gen CPU's fa...

We'd need to see an log of an encode to see exactly what it's doing

I've split your post off into a new thread for you.

A fix for the installer was just pushed. When 1.8.2 is released, it will read correctly.

The erroneous .NET information for older versions of HandBrake will also no longer show the next time the site update is pushed.

Thanks for the heads up.

Nope

r/handbrake is not a official HandBrake channel and isn't associated with the project

We don't have any contact with the moderators over there.

As long as you follow the community guidelines here, your welcome.

The docker version of HandBrake is 3rd party and not supported by us. I'm not sure how docker will affect hardware support. Hardware encoding on linux is a bit more problematic so mileage may vary depending on the OS and drivers available for it. One thing i'd also be mindful of is 10th gen and earl...

The Docker version of HandBrake is a 3rd party version and not supported by us. You'd want to ask them about it. I suspect it's an issue with QuickSync inside docker but it's just a guess at this point.

This is perfectly normal. Scaling will vary a lot depending on hardware, source, settings etc. Xeons tend to have lower clock speeds which can hurt performance scaling. NUMA can get in the way of core scaling as well. Just a hint, since your dealing with 4K, you probably won't need combdetect or dec...

That looks normal to me. It's doing a fair bit of work during that phase and your doing it on 8400 titles so it's going to take a while.

Turn off QuickSync decode in preferences for now. It'll be sorted in a future update.

I'm not sure if linux allows per-app scaling but if it doesn't, you don't have a lot of options I'm afraid.