HandBrake

0xc0000005 is just a generic unknown error. To get a hard crash like this on startup, it has to be a low level operation so it's highly likely to the be quicksync probe that's causing it. (and has been for several other users). The fix for them was updating drivers so your a bit screwed if Dell are ...

Make sure your Intel UHD Graphics drivers are up-to-date From Intels site, not Dell Same applies to those with Nvidia or AMD parts. All 3 vendors have a drivers that work, and those that don't. Failing that, something a bit more complex is broken on these systems and unfortunately there won't be any...

Same encoder, but it didn't use fdkaac.exe or fdkaac.dll It was statically linked into HandBrake. It's never been an externally called library. In short, There is no easy way around this. You must compile from source if you want this functionality in a new version but note, you'd be using an unsuppo...

You failed to include the entire log so I can't say for sure but in all likely hood, you're using settings that are invalid or beyond the capability of the hardware.

Is the other program setup to output anamorphic content?

Does Blender actually support Anamorphic? Your desciption makes it sound like it doesn't.

Mod Note: Topic Split since this was unrelated to the other topic.

There is a link to old versions on the actual download page (see link at the top of the page)

Windows doesn't support preset upgrades and will usually leave a copy of the old presets in the C:\Users\%appdata%\AppData\Roaming\HandBrake if it can.

So, you can recover into the old version, but not use with a new version.

The HandBrake pipeline is 8bit only currently so even the 10bit encoder options can only ever be fed by an 8bit source.

This is something that will hopefully be supported in a future version of HandBrake.

I think you mis-understand. You can't output HDR10 with HandBrake, thus, there are no parameters.

Nope. 1.0.7 will still work ok so you should use that.

Ywou can't have menus or multiple movies in a single output file.

Each movie is a separate title. Select the correct title for each movie, add it to the queue and let HandBrake encode to two separate files.

It's not a case of people sending you a copy. They can't. Distributing it is a breach of license which would then be revoked.

HandBrake is properly signed and is known to Microsoft.

It's far more likely that they keep pushing out the bad Intel UHD driver from a month or two ago.

Handbrake keeps logs in your "user home" area, and security settings activated in the last major windows update block programs from writing to that area. Where are you getting this from? I think I've only ever seen 1 case where permissions were screwed and that was result of user error. If windows ...

hb_queue_recovery cannot be imported with the queue import function. Installing different versions is a bad idea in this kind of situation since we don't support migrating queues between versions, so it can do more damage than good. If the app is "ignoring" the file, then it's either corrupted or do...

Increasing the thread count can change results. As long as those results are the same at a given thread count, t's deterministic.

@Woodstock, the video will also be different (in some cases), even with identical settings. x265 won't always produces identical results for subsequent runs. While not identical, the differences is minuscule. Thus, safe to say, they are the same. (Although wouldn't produce the same checksum) While s...

We don't allow folks to solicit paid support on this forum. If something goes wrong, or you get scammed, it's bad for everyone. If using the queue doesn't meet your needs (https://handbrake.fr/docs/en/1.2.0/advanced/queue.html) and your not willing to learn, or simply not interested then you might b...

x265 has modes which can be non-deterministic. This introduces very small variances for each run but for all intensive purposes, can be ignored.

Your settings are the same for both encodes, and the output stats for the video tracks are close enough for it to be irrelevant.

Your source has PGS Subtitles.

MP4 files do not support PGS subtitles which means you must burn-in if your using this, or use other software to OCR and convert the subtitle images to a text based format like SSA.

Otherwise, you can use MKV which won't force burn-in.

Nope, afraid not. The log is agnostic to the encoder so it's not indicating whether an encoder supports more granular setting.

https://handbrake.fr/docs/en/latest/tec ... nvenc.html See the performance section.

Already on my list to extend this functionality