Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

Update Performance article with new codecs like AV1 and observations on newer hardware.

Offen
  • Stimmt etwas nicht?
#154 2 Kommentare 0 Reaktionen 1 zugewiesene Person Auf GitHub ansehen

@bradleysepos arbeitet bereits daran.

Seit 29.9.2026.

Bewertung

Schwierigkeit
5/5
Geschätzter Aufwand
Über eine Woche
Anfängerfreundlichkeit
35/100
Issue-Typ
Dokumentation
Klarheit
Größtenteils klar
Aktivitätsstatus
Veraltet
Tech-Stack
markdown
Bereich
documentation, performance

Rechercherichtung

Beginne mit dem Lesen von performance.markdown und vergleiche dessen Tabellen zum Qualitätsvergleich und die Hinweise zu Hardware-Encodern mit den bereitgestellten VMAF-Ergebnissen, dem Netflix-VMAF-Projekt und dem verlinkten Bericht. Als abgeschlossen gilt die Abstimmung über den Umfang der Aktualisierung sowie die Aktualisierung der dokumentierten Vergleiche und Aussagen zur hardwarebeschleunigten Kodierung.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

Improvement

First things first: The handbrake site about performance is the most serious and best site I know which deals with this subject quality vs. performance. It should be keeped alive. It just seems to me it should get a rework in 2022 as there happened something serious in this area in the meantime.

Issues:
Quality comparison:

Netflix gave us all a tool into our hands to make a serious and comparable assessment of the results: https://github.com/Netflix/vmaf. The tests should be compared with that, resulting in comparing numbers instead of visual opinions with magnifiers. So the site should add a column to all tables, just to show how far or near the result is from the source material.
That could be even very easily included in Handbrake as a library, but that would be an enhancement I'm not sure if it would be useful in the sense of the Handbrake as transcoder or not.

Hardware accelerated rendering:

That part seems to be fairly actual (e.g. GTX 1060), but it seems that at least the nvenc part should get another try with a Turing chip (RTX) in 2022. Beside of the marketing yaddayadda by Nvidia you'll find too, this report here has some surprises in it: https://youtu.be/ccoOGfX9qxg

Handbrake is not streaming. So what does that mean for Handbrake transcoding and is that worth a serious try? A short check of tears_of_steel_720p.mov with my RTX 2070 Super gives me the following results:

CPU: HQ 720p30 Surround (Modified: BpS same as source with x.264):

render time VMAF min[^1] VMAF max[^1] VMAF mean[^1] VMAF harmonic mean[^1] file size
2:41 min 83.984472 100.000000 98.063116 98.020935 276'968'288 Bytes

GPU: HQ 720p30 Surround (Modified: BpS same as source and H264 nvenc):

render time VMAF min[^1] VMAF max[^1] VMAF mean[^1] VMAF harmonic mean[^1] file size
00:29 min 84.678945 100.000000 98.965836 98.947771 490'314'770 Bytes

[^1]: higher number is better. Maximum value is 100.

It seems as Nvidia did something very serious in the quality apartment of the Turing chips. Mainly for the streamers, but we also get some benefits here. The sentence "Hardware encoders are typically much faster than software encoders, at the expense of some loss in quality and/or larger file sizes." should be more precise: the file size of x.264 is still remarkably smaller (that part keeps true, as it seems) but the quality outcome of x.264 is even a bit less than the result of nvenc with the same quality settings. Nothing on the page actually goes in that direction. I think, to be fair for Nvidias effort to get better there (and maybe other hardware accelerated solutions too): You do not have to expect a loss of quality if you have the right hardware. You get bigger files, that seems to be always true.

Vorherrschende Sprache
Shell
Sterne
268
Forks
103
Ø Merge
9 T. 5 Std.
Gemergte PRs (30 T.)
1

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus HandBrake/HandBrake-docs

Alle Issues in HandBrake/HandBrake-docs

Ähnliche Issues

Weitere Issues zu Shell/Bash

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.