You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
But the validation process isn't configured for CTA vectors. I used --cmaf --ctawave --segments. Here's the aggregated result of running JCCP on CTA-WAVE's database: db.validation-staging.json
There are several different failure points that may be issues with the validator's staging deployment.
For instance, on cfhd_sets/12.5_25_50/t12/2023-09-01/ we are getting a test failure with the message : For a CMAF Track to comply with one of the media profiles in Table A.1, it SHALL conform to the colour_primaries, transfer_characteristics and matrix_coefficients values from the options listed in the table
But inspecting the content, it appears the vui is present and valid as described in ISO/IEC 23000-19:
The development branch / staging deployment of Dash-If-Conformance software is being used to validate CTA-WAVE test content.
Test failures are being reported, however after initial manual inspection there seems to be failures reported where the content is found to be valid.
This issue is also tracked on CTA-WAVE's Test-Content-Generation/issues/55.
I see that running the validation on cta-wave vectors is part of the GitHub workflows : https://github.com/Dash-Industry-Forum/DASH-IF-Conformance/actions/workflows/run-cta-wave-test-vectors.yml
But the validation process isn't configured for CTA vectors. I used
--cmaf --ctawave --segments
. Here's the aggregated result of running JCCP on CTA-WAVE's database:db.validation-staging.json
There are several different failure points that may be issues with the validator's staging deployment.
For instance, on cfhd_sets/12.5_25_50/t12/2023-09-01/ we are getting a test failure with the message :
For a CMAF Track to comply with one of the media profiles in Table A.1, it SHALL conform to the colour_primaries, transfer_characteristics and matrix_coefficients values from the options listed in the table
But inspecting the content, it appears the vui is present and valid as described in
ISO/IEC 23000-19
:cc @rbouqueau
The text was updated successfully, but these errors were encountered: