Skip to content
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

Process to attach JCCP test reports with submitted material #49

Open
yanj-github opened this issue May 30, 2023 · 8 comments
Open

Process to attach JCCP test reports with submitted material #49

yanj-github opened this issue May 30, 2023 · 8 comments
Assignees
Labels
Deferred Deferred to future work

Comments

@yanj-github
Copy link
Contributor

As commented here: #47 (comment)
We would like to know a bit more details about the process please?

  1. Where to attach the JCCP test reports
  2. In which format
  3. Which version on JCCP should we use? - we have run with latest release on master
@yanj-github
Copy link
Contributor Author

yanj-github commented May 31, 2023

We have used http://beta.conformance.dashif.org/ and summary of report is attached here.
CTA WAVE_AAC streams_JCCP DASH-IF Conformance Tool Results_300523.xlsx

@gitwjr
Copy link

gitwjr commented Aug 1, 2023

@yan please discuss with Nicholas.

@jpiesing
Copy link
Contributor

Here is a proposal since nobody else has made one.

In this repo, create a new directory /validator-reports/ then a sub-directory that is the media type 4CC then perhaps another directory that is the date in ISO form (yyyy-mm-dd) and the file.

As for the format, what choice is there? Pick the format with the most available information.

@rbouqueau
Copy link
Collaborator

Would it be acceptable to upload these reports to the server? I feel they belong more to the media than this git repository (which is for the front-end).

Also I had envisioned that the validation script would be eventually called automatically at the end of the generation process. It already has an option to call JCCP and to emit a report.

@gitwjr
Copy link

gitwjr commented Oct 30, 2023

@yanj-github @rbouqueau
Can this issue be closed?

@rbouqueau
Copy link
Collaborator

Not yet, we haven't agreed on the location (and process) for the report. Then we'll need to implement it.

@gitwjr
Copy link

gitwjr commented Dec 5, 2023

@rbouqueau This is not a blocker. On 12-5-23 we agreed to use @rbouqueau proposal for a location. He can proceed.

@rbouqueau rbouqueau self-assigned this Dec 5, 2023
@gitwjr gitwjr added the Deferred Deferred to future work label Dec 19, 2023
@gitwjr
Copy link

gitwjr commented Dec 19, 2023

Deferred to V2. Waiting for additional/new content to be generated and posted before reports are attached to the new content.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Deferred Deferred to future work
Projects
None yet
Development

No branches or pull requests

4 participants