HandBrake

You create a new preset and set the resolution limits in the "create new preset" dialog, e.g. here under macOS:

The tooltip for "Encoder Profile: Auto/High/Main/Baseline" says 'Sets and ensures compliance with the specified profile'. I want to use all of the Advanced Settings that previously existed in older versions of Handbrake in the text box. Which of these settings will the Encoder Profile setting then ...

mduell wrote: ↑

Tue May 14, 2019 6:20 pm

Yes, specific options will override the preset/tune/etc selections.

Not etc. -- extra options (text box) overrides preset and tune, but it overridden by profile and level unless those are set to auto

Initializing the VT H.264 encoder with hardware acceleration fails for some reason. Not sure what the error code means, maybe Ritsuka would know, he spent a lot more time than me working with this API.

Can we get a log for that please? Also a screenshot of the subtitle tab?

Subtitle tab -- Foreign Audio Search appears as a subtitle track and triggers the subtitle scan pass.

x265 -- but they have no useful effect since HandBrake is 8-bit 4:2:0 all the way.

Yes, it depends on the graphics hardware. Though in theory HEVC capable hardware should be AVC capable too. My wildest guess would be Apple decided to provide H.264 encoding using the Intel UHD graphics on the i9 board and HEVC via the other card or something; perhaps the way we initialize or detect...

NVENC support is listed separately from the QSV stuff (or not listed at all, cannot remember). The GPU at least should be NVENC HEVC capable, but no idea about whether other requirements are missing.

If you use x264 as the encoder, it is aware of frame durations and accounts for it in rate control, hence why 30 and 60 fps content comes out about the same size.

Just FWIW, that checkbox is for really really old iPods that probably no longer even power on nowadays. And you would need to adjust other settings too, the checkbox by itself is not enough to make the output iPod-compatible.

No blending, but there is some frame analysis so we try and drop frames that are least relevant, so to speak. j45 will have to elaborate on exactly how it affects motion smoothness as I didn't write that code.

rollin_eng wrote: ↑

Fri Apr 26, 2019 7:24 am

[ipod @ 00000141c79b7600] Could not find tag for codec eac3 in stream #1, codec not currently supported in container
muxavformat: avformat_write_header failed!

Looks like eac3 is not supported in mp4 container.

Only if you request the iPod Atom (for the 5th generation iPod ).

x264 is fully deterministic unless you specifically tell it not to be though (even with VBV).

No idea, ask x265 devs.

rollin_eng wrote: ↑

Thu Apr 25, 2019 5:42 pm

What exactly causes the difference then?

s55 wrote: ↑

Thu Apr 25, 2019 3:44 pm

x265 won't always produces identical results for subsequent runs.

https://en.wikipedia.org/wiki/Deterministic_algorithm (or in this case, lack thereof)

Dates would most likely be fixed-length fields and have no impact on the final output size, too.

The difference is like 1 kilobits per second average over the whole video… though typically this is only expected if e.g. the CPUs aren't the same, but maybe x265 isn't fully deterministic?

Description of problem or question: Is there a way to set an incremental QP setting when ripping with NVENC, like there is with normal x264 encoding? For example, using QP 21.25, instead of QP 21. The activity log seems to show that the QP value can be set to 21.XX, but using the normal -q setting ...

While it might technically be possible to split the Atmos extension from the TrueHD stream and attach it to an E-AC-3 re-encode of the TrueHD stream, I suspect it would not work as the Atmos must be tied to the audio stream it was authored for, and since TrueHD -> E-AC-3 is lossy it's likely the Tru...

What checksum did you get? Can you share the corresponding exe file on Dropbox or similar?

ISO images of DVD or Blu-ray discs have multiple titles each, so they kind of are are folders themselves, so to speak. HandBrake can't scan folders of folders, only folders containing standalone video files.

Pretty sure BMWs have square pixels, displays are just very wide nowadays. My father's can't yet play videos though, IIRC.

Not sure… you'd have to compile from source, and also make sure you have an x86_64 microprocessor, not ARM.