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

naming convention for output folders #22

Closed
rbouqueau opened this issue Feb 10, 2021 · 6 comments
Closed

naming convention for output folders #22

rbouqueau opened this issue Feb 10, 2021 · 6 comments
Assignees

Comments

@rbouqueau
Copy link
Collaborator

Hi @louaybassbouss

@nicholas-fr and I got an email discussion about the opportunity to find a better naming the output folders. At the moment these folders are called '1', '2', etc. (see http://dash.akamaized.net/WAVE/index.html?cache=clear)

Nicholas mentioned that we could think of a naming convention related to the use of the content. For example

This is just a suggestion. Please let us know if this has some added value for you.

@jpiesing
Copy link
Contributor

jpiesing commented Feb 11, 2021

@rbouqueau @louaybassbouss @nicholas-fr

Looking at where we want to be in a few months time, I could see a hierarchy something like this ...

1st level - WAVE media profiles (codecs)
2nd level - only for video, 50Hz / 60Hz (?)
3rd level - CMAF switching sets (as per the original proposal from @rbouqueau )

@jpiesing
Copy link
Contributor

So for example, would this give the following?

That's the sort of thing I had in mind.

@louaybassbouss
Copy link

So for example, would this give the following?

That's the sort of thing I had in mind.

Also fine for me

@jpiesing
Copy link
Contributor

Since everyone seems to be OK with this proposal & it's been implemented for 15_30_60, can the issue be closed?

@jpiesing
Copy link
Contributor

May 25th
Encryption addressed.

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

No branches or pull requests

4 participants