-
Notifications
You must be signed in to change notification settings - Fork 246
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
Prevent passing Frames with the wrong dimensions and/or chroma sampling #2461
Labels
Comments
I'd like to take this on, also because I'd like access to the configuration for the jsapi. |
lu-zero
added a commit
to rust-av/rav1e
that referenced
this issue
Jul 27, 2020
It is a big footgun (xiph#2461) and should be avoided.
lu-zero
added a commit
to rust-av/rav1e
that referenced
this issue
Jul 27, 2020
It is a big footgun (xiph#2461) and should be avoided.
lu-zero
added a commit
to rust-av/rav1e
that referenced
this issue
Jul 27, 2020
It is a big footgun (xiph#2461) and should be avoided.
lu-zero
added a commit
to rust-av/rav1e
that referenced
this issue
Jul 27, 2020
It is a big footgun (xiph#2461) and should be avoided.
lu-zero
added a commit
that referenced
this issue
Jul 28, 2020
It is a big footgun (#2461) and should be avoided.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As in the code snippet from #2460 we do not validate that the frame provided has the correct dimensions since we assume the user uses
Context::new_frame()
to create a new frame with the correct settings.In order to add validation we either need to store the configuration in the
Frame
.The text was updated successfully, but these errors were encountered: