-
Notifications
You must be signed in to change notification settings - Fork 7
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
Check that hvcC matches ispe
and pixi
#58
Comments
I realize this might be a large ask, but given that the compliance warden can handle the |
We need two things:
|
I would say that this is already a requirement. But potentially it's not spelled out as such clearly enough. From HEIF:
So we have:
I don't know my way around the HEVC spec well enough to immediately say which section describes the output dimensions, but it's most likely a combination of |
Is anyone able to comment here? |
I agree with @leo-barnes's analysis |
I investigated the file mentioned in this comment and concluded that the issue is that the
ispe
does not match the actual dimensions of the coded item.In this case the
hvcC
says that the dimensions of the coded item is 1600x1096, while theispe
says 1599x1096. This in turn leads to theclap
property specifying a crop rect that starts at a negative offset.It would be great if the compliance warden could do some minimal validation of the HEVC codec config with regards to the
ispe
. Other properties that could be checked would potentially bepixi
,colr
and potentially the MIAF brands that set limits on profiles.The text was updated successfully, but these errors were encountered: