HandBrake

ffprobe actually samples some of the audio stream to determine the bit rate. HandBrake's AAC encoders are not constant bit rate, they're variable/average, so it will fluctuate above and below 192 throughout the stream depending on the complexity of the source audio.

Indeed, we had another report of this recently. I believe the bit rate is not stored in the container, so some softwares will attempt to glean the information from the stream itself. Inconvenient but not a bug in HandBrake; more of a shortcoming of MediaInfo.

Quality will be the same, but if the network flakes out even for a moment, the encode will fail. HandBrake has no code for working around issues of that kind. Local is more reliable overall but if you have a perfectly stable LAN and machines you might be okay.

Subler and/or MKVToolnix might help you add/export chapters.

HandBrake cannot do this; you will need a video editor. Something like Shotcut can probably do it, or the free version of Davinci Resolve.

Mentioning other useful softwares where there is no affiliation and the software complements HandBrake's workflows is fine in moderation. We appreciate everyone's enthusiasm for video and related softwares, and in this case, it certainly helped my understanding to get the broader picture of how Hand...

It looks like the destination lacks the .mkv extension; perhaps you accidentally removed it when naming in HandBrake. You do not need to encode the file again, simply rename it to add .mkv at the end and re-add to Kodi.

RF is not the same as QP. QP 4-8 is probably a sane range for the old MPEG-4 codec.

When a gnu.org subdomain goes down on a weekend, does Richard Stallman make a sound?

Temporary alternative download: https://www.dropbox.com/sh/h59iie78v8vk ... Ds3Ua?dl=0

Ha! And to you.

I assure you, Ritsuka and I are separate people.

Glad you got it sorted.

5) As silly as it may sound, if this a notebook PC with a brick-type power adapter, it might be failing under load (voltage sag or inability to provide sufficient current). Has happened to me more than once with all sorts of equipment. Tough to measure without the right equipment, though. Aside, my ...

Source encodes fine on macOS. I booted up my Arch VM and performed: flatpak install runtime/org.gnome.Platform/x86_64/3.34 flatpak --user install HandBrake-1.3.0-x86_64.flatpak # Direct download from handbrake.fr Installed apps and runtimes: [arch@localhost ~]$ flatpak list Name Application ID Versi...

No problem, I'll take a look.

Another thing you might try if you have time is building HandBrake from source (non-Flatpak) and see if that resolves the issue, which would point to something with the Flatpak specifically. We provide documentation for Arch here: https://handbrake.fr/docs/en/latest/developer/install-dependencies-ar...

That's definitely odd and usually points to thermals, but obviously yours seem to be well within spec. HandBrake really can't crash the kernel especially with Flatpak sandboxing so I'm wondering if there's some instability in the underlying Flatpak subsystem. If you can trim (edit: use MKVToolNix or...

I tested your source here, looks excellent on a 4K display using the Playstation 2160p60 4K Surround preset (the only 4K preset we have that makes H.264/AVC). The average bit rate is 18 Mbit/s with peaks up to 39 Mbit/s. If your devices play this well, this is a good starting point. Don't get too hu...

Apologies, I linked the H.264/AVC levels, for which you will need 5.2. The source file is compliant to H.265/HEVC Level 5.1: https://en.wikipedia.org/wiki/High_Efficiency_Video_Coding_tiers_and_levels#Levels HandBrake's primary purpose is not to create editor-friendly encodes, though the Production ...

Also, for H.264/AVC you do need Level 5.2 to support your frame rate (5.1 only does 4K up to about 30 fps): https://en.wikipedia.org/wiki/Advanced_Video_Coding#Levels I would expect no home media player (other than on a computer reading from local storage) to handle more than about 20-25 Mbit/s vide...

For editing or production delivery, that may make sense for their product as repeated transcoding can introduce losses. Regardless, it's somewhat arbitrary, especially applied to HandBrake as different encoders vary in their efficiency. Bit rate is only a measure of quality efficiency for a single e...

Yikes, that's a lot of unfiltered frames for the defaults, which are pretty sensitive. Are you sure the content isn't mixed interlaced and progressive, or telecined ?

Could this be a localization issue?

Seems to work fine here, not sure whether something's being set incorrectly or not. It looks like your settings should be compliant. Anyway, unlike for H.264, pretty much all H.265 decoders we've tested handle any content up to 4K with level set to auto, so use auto unless you run into a specific is...

Level was always auto in 1.2.x. Setting to auto here should resolve your issue.

There may be an additional bug; I'll contact our Linux developer.