-
Notifications
You must be signed in to change notification settings - Fork 5
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
Comments
@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) |
That's the sort of thing I had in mind. |
Also fine for me |
Since everyone seems to be OK with this proposal & it's been implemented for 15_30_60, can the issue be closed? |
May 25th |
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.
The text was updated successfully, but these errors were encountered: