We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Overview With --aq-mode 0 as the only parameter, the encode aborts with no error message.
--aq-mode 0
Branch In which branch does the issue appear to be occurring?
master
testing
Reproduction Steps to reproduce the behavior:
SvtAv1EncApp -i input0.y4m -b asdf.ivf --aq-mode 0
Expected behavior The encode results in an output file larger than 0KB.
Platform (please complete the following information):
Version String (please complete the following information):
SVT-AV1-PSY Encoder Lib v2.3.0-B
Additional context / Relevant Files --aq-mode 0 appears to work fine in vanilla svt-av1.
The text was updated successfully, but these errors were encountered:
Yeah, this is sadly an annoying behavior with --tune 2/3 where the encoder is supposed to abort: https://github.com/psy-ex/svt-av1-psy/blob/master/Source/Lib/Codec/mode_decision.c#L4807
--tune 2/3
I'm currently working on a way to disable SSIM-RD, or simply refuse the use of --aq-mode 0 when --tune 2/3 are active.
Sorry, something went wrong.
No branches or pull requests
Overview
With
--aq-mode 0
as the only parameter, the encode aborts with no error message.Branch
In which branch does the issue appear to be occurring?
master
testing
Reproduction
Steps to reproduce the behavior:
SvtAv1EncApp -i input0.y4m -b asdf.ivf --aq-mode 0
Expected behavior
The encode results in an output file larger than 0KB.
Platform (please complete the following information):
Version String (please complete the following information):
SVT-AV1-PSY Encoder Lib v2.3.0-B
Additional context / Relevant Files
--aq-mode 0
appears to work fine in vanilla svt-av1.The text was updated successfully, but these errors were encountered: