HandBrake

Post the logs.

Motion has an issue on my UHD BD player (Sony UBP-X800M2); will see if 'fast encode' helps and also reduce processing speed in HB (I had set it to 'ultrafast' for the test). That doesn't do what you seem to think it does. Oh, thanks. I was misinformed then. The person who suggested that option has ...

kjparenteau wrote: ↑Thu Feb 25, 2021 7:59 amKeep in mind, the colors and detail now match the original (to my eyes) and look great and MUCH smaller in size, but it does not list HDR10 on the video after encoding... Am I missing something?

Shows you just how little HDR10 means.

njweb wrote: ↑Thu Feb 25, 2021 3:20 pmMotion has an issue on my UHD BD player (Sony UBP-X800M2); will see if 'fast encode' helps and also reduce processing speed in HB (I had set it to 'ultrafast' for the test).

That doesn't do what you seem to think it does.

HB autocrop found 88 pixels of black on the right border, and you chose autocrop, so they were cropped of. You can set cropping to some other value you prefer.

Why not just buy a Roku or something that can play files off a network share?

No transcoding, UDH BR authoring, disks to mess with, etc.

The quality scales aren't really the same on the different encoders.

I don't have a real problem

We don't have real answers without real logs.

Same RF isn't constant quality across different encoder settings.

Need to compare objective quality metrics (and use the appropriate tunes), or do proper double blind subjective testing, for real results.

The resulting quality is also different, since the big flat simple black areas change how the RF quality metric thinks its doing.

The activity log would answer a lot of questions we're not going to repeat over and over.

If you're targeting mid to low quality output, or it's 4K resolution, then no.

Your audio tracks are stereo...

Given how fast 480p will encode, I'd use slower x264 settings for this archival type encode. If you're going to edit them in the future, I'd also keep an encode (from the original AVI source) using the Production Standard preset. And check the results carefully for combing/etc before you toss the or...

Some, but not a lot. More reasonable settings may get you a more desirable tradeoff in performance vs efficiency.

Low 20s are reasonable values; higher for 4K, lower for HD.

There's no matching, they're different metrics for setting quality; specifically x264's CRF incorporates a psychovisual model to vary the QP target depending on the content. Even when they're the same _on average_ they may differ in behavior for low/high motion or low/high detail scenes.

Nightly, when the build system is working.

The presets targeting different resolutions have different quality targets (each suitable for their named resolution).

Rip to the SSD first using MakeMKV, then you can do a proper head to head comparison of the CPUs/ASICs.

Mostly pull requests.

HQ 1080p preset would be a good starting point.

Use the speed presets and tune options, not copypasta nonsense.

Code: Select all

[20:20:43]        + frame rate: 59.764 fps -> peak rate limited to 23.976 fps

[20:21:19] vfr: 1014 frames output, 1672 dropped and 0 duped for CFR/PFR

Your real problem is dropping 60 fps content to 24 fps, not interframe compression.

kbyeeeeeeeeee