Closed podborski closed 3 months ago
$ python aomrules.py --spec av1isobmff --dump
Is there an easy way to combine this output with the existing implementation?
Hi, thank you. Could you resubmit your PR against the master branch? Since av1isobmff (was merged), the current configuration makes it difficult to review. Thanks!
Is there an easy way to combine this output with the existing implementation?
Unfortunately no. We should think about a way to update (that would just insert the assert-ids when done for the first time). Any idea?
Is there an easy way to combine this output with the existing implementation?
Unfortunately no. We should think about a way to update (that would just insert the assert-ids when done for the first time). Any idea?
Not sure, one way would be to see if we can automatically map somehow. I just did change a couple manually after running: python aomrules.py --spec av1isobmff -i https://aomediacodec.github.io/av1-isobmff/v1.2.0.html --dump
Unfortunately I don't have time to finish this mapping myself at the moment. I will be available for any related work next month. If there is anyone who can sit down and map the implemented rules to the existing assert-ids from v1.2.0 this would be cool. If not, I'll try to do it in February.
FYI, the build process of the spec now generates and publishes the conformance report using ComplianceWarden, see https://aomediacodec.github.io/av1-isobmff/conformance/
We now have AV1-ISOBMFF version 1.3.0 the we should use instead.
update script to prepare assert-id's for AV1-ISOBMFF.