Re: [webrtc-extensions] Add API to control encode complexity (#191)

I'm gonna bump this up the prio list again, as this is even more relevant with the [maintain-framerate-and-resolution](https://github.com/w3c/mst-content-hint/issues/62) degradation preference (a.k.a "bring your own adaptation").

Even without that I think a content complexity setting makes sense. 

Re the [comment](https://github.com/w3c/webrtc-extensions/issues/191#issuecomment-1894249533) above:
1) Could we use https://w3c.github.io/webrtc-priority/#rtc-priority-type as a potential knob instead? 
  - Maybe, but that one may affect many other things such as bandwidth allocation, which we don't want to alter.
2)  Is the use case to tell the UA that we prefer high quality, or battery life, and shouldn't that be a global PC setting?
  - Adapting to battery state is certainly a use-case, but the UA is not in the best situation to know which encodings we want to adapt and how. We want to make decisions so that any adaptations lead to the minimum visual penalty from the perspective of the remote receivers.

And just to make it clear - yes I'm thinking mostly about software video encoders right now. Some HW encoders do have a configurable effort setting, but that's rare and the effect isn't usually as pronounced as with SW.

-- 
GitHub Notification of comment by sprangerik
Please view or discuss this issue at https://github.com/w3c/webrtc-extensions/issues/191#issuecomment-3426285836 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Tuesday, 21 October 2025 12:11:59 UTC