HandBrake

RF 0 is senseless, and unless you need the video codec changed for compatibility, completely pointless as the output is likely to be larger than the input. Reasonable values are, as always, far better choices than extremes. Try a few values and as your viewers what they can see. High teens to low tw...

This is very much not a general question, as it relates to a specific encode.

Also, this is sort of par for the course if you choose MKV. It's not a real standard, just a collection of implementations doing whatever and you can't really say they're wrong.

No.

It's mostly a numbers game. Few people use a filter inappropriately because they think it's a good idea, although I'm sure some do. More will attempt to upscale video thinking they're improving quality, and worse there are tutorials out there suggesting people do so; in gross disproportion to those ...

Bold move cotton, lets see where this attitude gets you.

You can increase the number of samples in the app preferences, which may improve the false detection rate.

Wow that's really bad.

@mduell: This is a support request? Why do you need an activity log for two files encoded at 480 and 1080? I'm having a hard time believing you're either not able to explain what I've already shown you without an activity log or trying it yourself. Does this happen to you or have you not tried enco...

HQ 1080p preset would be a good starting point for HD content.

Upscaling is not available in the GUI because it's mostly misused/misunderstood by users.

Upscaling is available in the CLI for users that know what they're doing.

Great, then you're there.

Read up on the encoder presets and tunes, figure out which ones it corresponds most closely to, and pick those.

The answer is still i9-9990XE (or 9980XE if you can't get one).

May still have some form of structural protection.

Best practice is to rip to a video file which removes more forms of protection. MakeMKV is good for this.

Either accept the efficiency penalty (poor quality for size) of the hardware encoders (Intel QSV, nVidia NVENC, AMD VCE), or get an Intel i9-9900K.

I agree PGS subs are a problem, but with no logs we don't know the subs are PGS. We've seen plenty of people muxing in 3rd party subs, or getting out their peg leg, etc.

Are you sure the credits are 24fps, not 30 or 60? I can't download the clips at the moment, but it sounds like the classic case of mixed framerate content.

Try leaving the framerate as same as source, variable framerate, and see how the scene looks.

mp4box or ffmpeg can do the remuxing for you without reencoding. They can likely keep chapters, and maybe keep subs.

Sure, I bet the developers would accept a pull request from you to better surface this error on all supported platforms.

Assuming you don't pick a resolution constrained preset that is lower than your source resolution (either pick one at or above your source resolution, or one with no resolution limit), HB will not change the resolution of the video by default. There is one exception, that HB will crop off useless bl...

Code: Select all

avio_open2 failed, errno -13

Do you have write permission to the destination?

Set the fallback audio encoder bitrate to 640 if you don't want the default 224.

The source bitrate is irrelevant since it's a different codec.

What if you post logs from the current supported verison, 1.2.2, on both platforms?

Also what are you using for playback on each platform, or are you transferring the files to the same platform?

Not with HB.

Also you may not be able to keep the subs depending on their format.

mp4box or ffmpeg can do the remuxing for you.