Hacktoberfest 2026:メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

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

オープン
#154 コメント 2 件 リアクション 0 件 担当者 1 名 GitHub で見る

@bradleysepos がすでに取り組んでいます。

2026年9月29日 から。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
35/100
issue の種類
ドキュメント
明瞭さ
おおむね明確
活発さ
停滞
技術スタック
markdown

調査の方向性

まず performance.markdown を読み、その品質比較表とハードウェアエンコーダーに関するガイダンスを、提供されている VMAF の結果、Netflix VMAF プロジェクト、リンク先のレポートと比較します。更新範囲について合意し、文書化されている比較とハードウェアアクセラレーションによるエンコーディングに関する記述を更新できれば完了です。

索引モデルが issue の本文から書いたものです。

説明

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.

主要言語
Shell
スター
268
フォーク
103
平均マージ
9日 5時間
マージ済み PR(30日)
1

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

HandBrake/HandBrake-docs のほかの issue

HandBrake/HandBrake-docs の issue をすべて見る

似ている issue

Shell/Bash の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。