You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This adds a new encoding parameter to WebRTC allowing the app to say which resolution it wants to send in absolute terms ("send 360p") instead of relative terms ("downscale by 2" + frame is 720p), avoiding race conditions when the track dynamically changes size.
Example use case is sending {360p, 720p} simulcast and when dynamically disabling the 720p layer also adjusting the track size to 360p in order to avoid expensive effects processing in 720p when only 360p is sent.
Request for Mozilla Position on an Emerging Web Specification
@
-mention GitHub accounts): @henbosOther information
This adds a new encoding parameter to WebRTC allowing the app to say which resolution it wants to send in absolute terms ("send 360p") instead of relative terms ("downscale by 2" + frame is 720p), avoiding race conditions when the track dynamically changes size.
Example use case is sending {360p, 720p} simulcast and when dynamically disabling the 720p layer also adjusting the track size to 360p in order to avoid expensive effects processing in 720p when only 360p is sent.
See https://www.w3.org/2024/08/27-webrtc-minutes.html#t06 where this was discussed and approved by the W3C WebRTC WG.
The text was updated successfully, but these errors were encountered: