Open dukesook opened 10 months ago
That would be great!
The first thing is to work on a new branch. Submit a pull request.
it would depend on the heif spec, but 23001-17 can also apply to mp4 files.
The dependency on heif can already be expressed. I am not familiar enough with the 23001-17 spec. If some rules are common to uncompressed items and tracks, you can store them in a std::vector<RuleDesc>
and add it to the SpecDesc.rules member.
The list of rules can be inferred from the normative statements (SHALL, SHOULD...). Do you have such a list?
An important part is to provide both positive and negative test vectors. I can certainly help transform a sample into a NASM assembly file for further editing.
I don't have a list of rules, but they are explicit in the the 23011-17 document itself by searching the terms SHALL and SHOULD.
Yes, I can intentionally create non-compliant uncompressed files simply to test the new rules in the SpecDesc.
I'm interested in having the Compliance Warden verify uncompressed data as per 23001-17.
Perhaps this warrants a new uncompressed.cpp file with its own SpecDesc object. I imagine it would depend on the heif spec, but 23001-17 can also apply to mp4 files.
Any thoughts?