performance.markdown should get a refresh (Rework? Retry?)
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 5/5
- Tempo stimato
- Più di una settimana
- Idoneità per principianti
- 35/100
- Tipo di issue
- Documentazione
- Chiarezza
- Abbastanza chiara
- Stato di attività
- Ferma
- Stack tecnologico
- markdown
- Ambito
- documentation, performance
Direzione di ricerca
Inizia leggendo performance.markdown e confronta le sue tabelle di confronto della qualità e le indicazioni sugli encoder hardware con i risultati VMAF forniti, il progetto Netflix VMAF e il report collegato. Il lavoro sarà considerato completato quando sarà stato concordato l'ambito dell'aggiornamento e saranno stati aggiornati i confronti documentati e le affermazioni sulla codifica accelerata via hardware.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
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.
- Lingua principale
- Shell
- Stelle
- 268
- Fork
- 104
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Guida per i contributori
Apri la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di HandBrake/HandBrake-docs
-
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 95/100
HandBrake/HandBrake-docs#272 ·
-
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 45/100
HandBrake/HandBrake-docs#253 ·
-
Improvement
Difficoltà 3/5 1-2 giorni Idoneità per principianti 35/100
HandBrake/HandBrake-docs#232 · 1 commento ·
-
Improvement
Difficoltà 3/5 1-2 giorni Idoneità per principianti 35/100
HandBrake/HandBrake-docs#204 · 1 reazione ·
-
GUI preset usage in the CLI ApertaImprovement
Difficoltà 2/5 1-3 ore Idoneità per principianti 55/100
HandBrake/HandBrake-docs#199 ·
Tutte le issue di HandBrake/HandBrake-docs
Issue simili
-
align on terminology Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
CycloneDX/transparency-exchange-api#393 · 1 commento ·
-
module/agent platform/macos type/bug/regression
Difficoltà 2/5 1-3 ore Idoneità per principianti 88/100
-
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 92/100
CachyOS/cachyos-aur-derived#754 ·
-
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 90/100
CrowdStrike/falcon-scripts#528 ·
-
bug(cli): hapi doctor inline-media prints a fabricated B:\ helper-script path in packaged installs Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 70/100