Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

unexpected result in vpxenc test #90

Closed
tawm opened this issue Jul 25, 2019 · 2 comments
Closed

unexpected result in vpxenc test #90

tawm opened this issue Jul 25, 2019 · 2 comments

Comments

@tawm
Copy link

tawm commented Jul 25, 2019

When running the vpxenc test, only performance data from the first pass is used. The performance figures obtained like this do not reflect real world performance well, as the first pass is an order of magnitude faster than the second pass.

@veikk0
Copy link

veikk0 commented Nov 15, 2019

To fix this, the --passes=1 parameter should be used to produce a single-pass encode.

By default, vpxenc also uses a either vbr or cbr (cant remember which) at a very low bitrate. To activate the CRF equivalent intead, the parameters --end-usage=cq and --cq-level=30 should be used.

aomenc is based on vpxenc and thus behaves the same way, so these options should probably be applied to that test profile as well.

@michaellarabel
Copy link
Member

This should be fixed by pts/vpxenc-3.0.0. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants