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
Thanks for filing this issue. It's a duplicate of #21, already on VNext.
Chromium currently has some heuristics for detecting a low-latency video renderer mode signal in each of webm and ISOBMFF bytestream types and using that signal if the rendering path supports low latency, but of course such is not standardized, nor is the current Chromium signal parsing logic final [1] [2] [3]. See #21.
Add a flag/mode requesting a low-latency mode (e.g. for videochats or cloud gaming).
When using WebRTC the browser assumes low-latency, but there seems to be no way of telling the browser that you want low-latency with MSE.
The text was updated successfully, but these errors were encountered: