-
Notifications
You must be signed in to change notification settings - Fork 12
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
Need media encoder agility #12
Comments
Do we need to specify this explicitly? If we allow container agility (#11), this will follow. |
@vasilvv may be you are right here . I was thinking media container agility meant support cmaf vs x vs y .. where the wg decides at some point if one of the proposed container format is not efficient or something like that .. what do you think ? |
I think it is worth explicitly mentioning that we want codec agility as it is a huge issue for some people. However if it turned out the way we got codec agility was just having container agility which then gave us codec agility, that would be a a perfectly fine way of getting it. |
Based on my experience, containers are sufficiently agile - once a new codec is done, it is relatively a fast process to complete the container support. If a container does not want to support a particular codec, well, that is usually known on day one. Having said that, I don't think this charter should focus on any specific choice of codec but an explicit list of containers (start with one and add more in the future) is desirable. At the end, part of a container's role is to separate the protocol from the internal mechanics of a codec. |
No description provided.
The text was updated successfully, but these errors were encountered: