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

documentation on how audio streams were encoded and packaged #58

Closed
jpiesing opened this issue Dec 7, 2022 · 8 comments
Closed

documentation on how audio streams were encoded and packaged #58

jpiesing opened this issue Dec 7, 2022 · 8 comments
Assignees
Labels
documentation Improvements or additions to documentation Release V2 Deferred to Release V2

Comments

@jpiesing
Copy link
Contributor

jpiesing commented Dec 7, 2022

In the December 6th meeting, we had a discussion about issue #3 which relates to properly documenting how a stream was encoded and packaged so it can be re-generated several years later if a problem is found. The conclusion was that we have most of this for video and what's left can be deferred. Fundamentally the AVC streams can be regenerated using open source tools and scripts that are in this repo.

Eurofins need to decide how this issue will be addressed for audio. What documentation will they provide for how to re-generate the audio they are/will be encoding and packaging. What scripts will be provided in this repo? They may be using commercial tools & not open source. They may be using pre-release or R&D versions of commercial tools. All that makes reproducing the encoding in the future complex but it is important.

@rbouqueau
Copy link
Collaborator

FYI the DTS/XPERI streams are generated using this repository, see https://github.com/cta-wave/Test-Content-Generation#audio-content-xperidts

@rcottingham
Copy link
Collaborator

rcottingham commented Sep 28, 2023

@rbouqueau I can update the Readme with this info and submit to you for review or provide to you to update. Let me know the best approach please.

@rbouqueau
Copy link
Collaborator

Any approach works: modify the Readme or provide a PR.

@jpiesing
Copy link
Contributor Author

@rcottingham Ideally, I would like to see sufficiently detailed documentation that a new suitably qualified engineer could reasonably attempt to regenerate the test material at some future time when Yan and yourself have moved on to other things and are not available. I fully appreciate your obligations to those paying for the work may be rather less than this. For AVC, Romain has provided the scripts used to generate the test content from the mezzanine.

@jpiesing jpiesing added the Release V2 Deferred to Release V2 label Oct 20, 2023
@gitwjr gitwjr added the Deferred Deferred for future work label Oct 20, 2023
@mbergman42
Copy link

I'm doing theory of operation, but not how to regenerate the test material. Richard, I'll send you a draft on the side.

@jpiesing jpiesing added documentation Improvements or additions to documentation and removed Deferred Deferred for future work labels Feb 13, 2024
@jpiesing
Copy link
Contributor Author

A solution of this has been proposed at #67

@rcottingham
Copy link
Collaborator

Pull request merged. I believe this can now be closed.

@rbouqueau
Copy link
Collaborator

Agreed. We now need to make decisions in #66 .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation Release V2 Deferred to Release V2
Projects
None yet
Development

No branches or pull requests

6 participants