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

Custom Scalability Structures #3

Open
aboba opened this issue Apr 10, 2019 · 8 comments
Open

Custom Scalability Structures #3

aboba opened this issue Apr 10, 2019 · 8 comments
Assignees
Labels
enhancement New feature or request

Comments

@aboba
Copy link
Contributor

aboba commented Apr 10, 2019

What if an application requires a custom scalability structure not supported in the defined scalability modes? For example, what if an application wants a 4:1 scalability ratio rather than 2:1 or 1.5:1?

Codecs such as AV1 support custom scalability structures, so that the encoder can be configured to support scalability structures beyond those defined in scalability modes.

Do we need a way to support scalability structures beyond those defined in scalability modes?

@aboba aboba self-assigned this Apr 10, 2019
@aboba aboba added the enhancement New feature or request label Apr 10, 2019
@alvestrand
Copy link
Contributor

The existing scalability structures show clearly that the design space for scalability structures is very large, and probabliy requires something like a turing-complete language to specify all possible permutations.
I would think that an application-defined scalability structure would be best done by defining an interface that installed a name and a function to be called to make the send/size decisions for each frame - and that it's something we should experiment with before trying to standardize it.

@aboba
Copy link
Contributor Author

aboba commented Jul 21, 2019

There are several ways to address the need for extending the resolution ratios that do not involve support for custom scalability structures:

  • Add scalability modes to the table. For example, modes featuring 4:1 resolution ratios could be added. It is even possible to add a mode where the resolution ratio is not constant, such as a mode to support simulcast encoding at 1080p, 720p and 360p (e.g. "S3T1p").

  • Allow layers to be disabled. For example, if a mode with 3 spatial layers were selected and the middle layer were to be disabled we would have a 4:1 ratio (for S3T1) or a 3:1 ratio (for S3T1h).

@aboba
Copy link
Contributor Author

aboba commented Jul 29, 2019

Related to Issue #14

@aboba aboba added question Further information is requested and removed enhancement New feature or request labels Aug 9, 2019
@alvestrand
Copy link
Contributor

In S3T1, doesn't the top layer depend on the middle layer?

@jan-ivar
Copy link
Member

TPAC ACTION: aboba to add a paragraph to the table to describe considerations for adding new values to the table of modes.

aboba added a commit that referenced this issue Jan 30, 2020
@aboba aboba added PR exists and removed question Further information is requested labels Jan 30, 2020
aboba added a commit that referenced this issue Jan 31, 2020
aboba added a commit that referenced this issue Jan 31, 2020
@aboba
Copy link
Contributor Author

aboba commented Apr 8, 2020

With the merger of PR 27, this issue has largely been resolved.

@aboba aboba closed this as completed Apr 8, 2020
@aboba
Copy link
Contributor Author

aboba commented Mar 15, 2021

Reopening issue due to a request for support of "flexible mode" in WebCodecs.

@aboba aboba reopened this Mar 15, 2021
@aboba aboba added the enhancement New feature or request label Nov 2, 2021
@aboba
Copy link
Contributor Author

aboba commented Dec 11, 2023

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

No branches or pull requests

4 participants