HandBrake

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.

Can you post the encoding log from when you tried threads=1? There will be some CPU usage other than the video encoder but I wouldn't expect to use all cores on an i9.

In preferences, enable the advanced options box for video encoders.

On the video tab, put threads=1 in that box.

No, I mean in the video encoder advanced settings, since you're using x264 use threads=1.

Simultaneous encodes should also be set to 1 given your instability issues.

Have you tried limiting the encoder threads in the current release? Perhaps even start at 1.

How do you get the error from the worker?

The mystery error -12 has been around since they separated the encoding process from the gui.

You can try limiting encoder threads to try to work around your hardware problem; try threads=8 and experiment higher or lower from there.

Silent_Strider wrote: ↑Wed Mar 06, 2024 7:23 pm Ripping does not, transcoding (which Handbrake does, because it's a transcoder, not a dedicated ripper) does.

I disagree, transcoding has no effect on the physical disk.

Which of the many playlists in your disk image are you looking at?

The fix needs to come from Intel/Gigabyte, not HB. HB can't (intentionally) make your computer suddenly reboot.

Here's a story about the broader 13/14th gen Intel stability issues and workarounds.

It's a pretty new machine - only about a month old - but has been working great up to now. There is no overclocking or any other tweaking. My previous machine ran this combination of software for many years on an AMD processor. Let's see what I find when I stress test the hardware a little... You h...

No... you need to read the CLI help.

Code: Select all

[17:21:41]  * subtitle track 1, English (VOBSUB) (track 0, id 0x4, Picture) -> Render/Burn-in, Default

You need --subtitle-burned=none

Sometimes I have optimism about the angry spaghetti, and then it bites me again.

OP, use the CLI.

You can launch different instances with separate queues.

Open another copy of HB with QSV as your encoder.

theoldwizard1 wrote: ↑Fri Feb 23, 2024 12:38 pm

mduell wrote: ↑Fri Feb 23, 2024 1:42 am Completely legal versions of a commercial TV series on DVD are always encrypted.

So why did Handbrake evode Disc 1 with no problem ?

Unreliable third party hacks? How would we know without an encoding log provided for Disc 1?

Completely legal versions of a commercial TV series on DVD are always encrypted.

You need MakeMKV to rip the disks before you use HB.

Yes, although better to make an MKV with MakeMKV.

Try updating to a supported driver for your GPU.

Did you get all the sub tracks in MakeMKV?

The French sub track you picked hardly contains anything.

Code: Select all

[18:40:43]  * subtitle track 1, Unknown (SRT) (track 0, id 0xff000000, Text) -> Passthrough, offset: 0, charset: UTF-8

Are you choosing the correct character set for the sub you're providing? I.e is the bad one really UTF-8?