Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

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

Ouverte
  • Quelque chose ne va pas ?
#154 2 commentaires 0 réactions 1 personne assignée Voir sur GitHub

@bradleysepos y travaille déjà.

Depuis le 29/9/2026.

Évaluation

Difficulté
5/5
Temps estimé
Plus d'une semaine
Accessibilité débutants
35/100
Type d'issue
Documentation
Clarté
Plutôt claire
Activité
À l'abandon
Stack technique
markdown
Domaine
documentation, performance

Piste de recherche

Commencez par lire performance.markdown et comparez ses tableaux de comparaison de la qualité et ses indications sur les encodeurs matériels avec les résultats VMAF fournis, le projet Netflix VMAF et le rapport lié. Le travail sera considéré comme terminé lorsque le périmètre de la mise à jour aura été convenu et que les comparaisons documentées ainsi que les affirmations sur l'encodage accéléré matériellement auront été mises à jour.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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.

Langage dominant
Shell
Étoiles
268
Forks
103
Merge moyen
9 j 5 h
PR mergées (30 j)
1

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de HandBrake/HandBrake-docs

Toutes les issues de HandBrake/HandBrake-docs

Issues similaires

Plus d'issues Shell/Bash

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.