HandBrake

No, it shouldn't be a problem.

Add the additional audio tracks on the audio tab.

Add 3 and see how you like it.

The resolution is good, it's non-anamorphic just cropping off the black bars.

The source is heavily compressed, so for a smaller file you need a higher RF.

An Activity Log is required for support requests. Please read How-to get an activity log? for details on how and why this should be provided.

It's not really clear what's happening without seeing the log.

JohnAStebbins wrote: ↑Thu Nov 30, 2023 7:26 pm Given that the 44GB source encodes to about 4GB with default settings, my guess is that the source is a lossless format (either raw or some other lossless codec).

My guess, given the size and MKV container, is it's a Blu-ray (HD or 4K).

Why do you want it the same file size?

Is there something wrong with the 4GB output?

Depends on which one. Probably for HEVC. The data rate is unlikely to be the issue.

There's not necessarily a preset for every encoder.

AV1 and HEVC are different codecs. HEVC is more compatible, but AV1 is more effective at compression. The Apple 4K HEVC preset has been around a while, and is comparable to the HQ 4K HEVC preset. The Super HQ 4K presets are slower for encoding and target even higher quality (although you may not be ...

Yes, there is.

GPUs are nearly worthless for encoding; Nvidia tried it with the original CUDA encoder and the results were utterly lackluster. What has been successful over the last 10 years or so is dedicated hardware on the ASIC for accelerating most of the video encoding pipeline; every manufacturer has their o...

Since the VCE encoder doesn't use the GPU cores, that's expected. The CPU load is probably audio encoding plus maybe video decode; no sense for it to get ahead of the video encode.

Most people are pretty pleased with 170 fps 4K encoding.

[10:28:18] * destination [10:28:18] + C:\Users\redacted\Videos\Suicide Squad (Extended Cut).mp4 [10:28:18] + container: MPEG-4 (libavformat) [10:28:18] * subtitle track 1, English (PGS) (track 0, id 0x3, Picture) -> Render/Burn-in, Forced Only MP4 doesn't support PGS subs, so they have to be burned...

Select the correct character encoding for the sub you're providing.

It's leaving the output at the same dimensions as your input, so it's correct.

An Activity Log is required for support requests. Please read How-to get an activity log? for details on how and why this should be provided.

We can't see your image, but the activity log will tell us a lot more.

I think this is more of a question for ffmpeg than for HB. It's not HB's error message.

What's the activity log say when you try it?

An Activity Log is required for support requests. Please read How-to get an activity log? for details on how and why this should be provided.

FWIW worked fine on macOS in 1.7.0 with the 4K Very Fast preset switched to x264: [16:00:41] macgui: Handbrake Version: 1.7.0 (2023111500) [16:00:41] Compile-time hardening features are enabled [16:00:41] macgui: built-in presets updated [16:00:41] hb_init: starting libhb thread [16:00:47] macgui: S...

The CLI lets you set any decimal value between 1 and 1000.

KSGregg wrote: ↑Thu Nov 16, 2023 7:04 pm And I am certainly not trying to debate you BUT that same screen grab also says 18-20 for standard definition and 20-23 for higher definition so you can see where I might be seeing conflicting info?

This is also explained in the documentation.

For x264, put cabac=0:bframes=whatever number you want in the advanced options.