HandBrake

Best practice for the Apple ecosystem is to include the 2ch AAC audio as the first audio track.

Balanced is fine, you just need to turn off the lowpower QSV mode in the HB settings.

Try without low power mode (I think its in settings).

No.

Because you don't have an nVidia driver installed. It's irrelevant to your actual issue.

“DVD upscale” and “high quality” seems like a bit of a stretch, but the obvious choice would be the HQ 2160p HEVC preset as a starting point.

Segfault would be a problem outside of HB... do you get the same segfault if you boot from a livecd?

You probably can't, since HB/video encoding doesn't use the main GPU execution units.

Not with HB. Use exiftool or similar.

Post the encoding log from that most recent encode so we can make specific suggestions for improvement.

When encoding a DolbyVision file (sourced from output from MakeMKV, the DolbyVision profile changes Just like the documentation says it will : Dolby Vision is supported only when using the x265 10-bit encoder, the following Dolby Vision profiles and cross compatibility IDs are supported: - 5.0 - 7....

More generally, set the level limit to what your playback environment supports.

Since we're just doing vibes here, keep both.

What you describe is combing, you may have to learn more advanced decomb options.

Try updating HB first.

Also if you're going to use x265 preset fast you may as well use preset veryfast.

Crop the appropriate number of pixels off the top and bottom for your resolution. Could save a preset to do that.

In the encode log provided, no cropping was done in HB.

I'd make efforts to understand the file you have/are providing, rather than just shotgunning every option.

Save a preset with the subtitle behavior you want, then use that preset for all the files.

For the frame rate, choose 60 or same as source, not 30.

The frame rate is curiously high... what if you choose same as source or 60 fps, still with peak/variable framerate, instead of forcing it down to 30.

Oh, it's missing on rate control by a lot given how short the content is and how high the QPs are. The encode looks worse because it's a third smaller.

For non-stillimage HD video in the 300 kbps range, you may be better off targeting like RF 50 rather than a specific bitrate.

Can you post both encoding logs so we can see whats happening?

The turbo first pass just skips a bunch of options that are slow and typically don't make a difference.

For trying something with extremely low bitrates, I'd leave it off, you want all the encode options applied to the first pass.

dwiercioch wrote: ↑Thu Mar 07, 2024 4:10 pmI'm in the middle of a longer stress test with prime 95 while I watch temps with HWinfo. Just to be sure, I also reset the bios to optimized defaults

What if you try non-optimized defaults. Like default defaults. Vanilla. No optimization.