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.

Sign up for GitHub

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

Jump to bottom

Interaction with Congestion Control #31

Open
aboba opened this issue May 28, 2020 · 3 comments
Open

Interaction with Congestion Control #31

aboba opened this issue May 28, 2020 · 3 comments
Labels
TPAC 2022 For discussion at TPAC

Comments

@aboba
Copy link
Contributor

aboba commented May 28, 2020

The Virtual Reality Gaming use case may potentially involve adding metadata to the encoded frame. The metadata could be substantial (hundreds of bytes).

Similarly, there are accessibility scenarios (captioning) in which the captions might be sent along with the frames.

So the question arises as to the interaction with congestion control in these scenarios. When adding to (or even substracting from?) the size of the encoded frame, is there a way to properly interact with congestion control?
@alvestrand
Copy link
Contributor

The streams mechanism allows pushback to avoid buffer overrun, but doesn't allow any other mechanism for congestion signalling.
Such feedback is one of the core usages for a feedback channel as requested in #90

@youennf
Copy link
Collaborator

youennf commented Jul 1, 2021

Two potential sub-issues:

  • Make sure that implementors handle size increase triggered by the transform.
  • Should the transform itself be able to understand how much space it can use. If so, we might need to expose some values about encoder bitrate, encoder+transform allocated bitrate

@aboba aboba added the TPAC 2022 For discussion at TPAC label Sep 2, 2022
@alvestrand
Copy link
Contributor

This is even more intense when you consider single-ended use cases as in #106.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
TPAC 2022 For discussion at TPAC
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@alvestrand @aboba @youennf