3 ms·

(I work at Google, on Chrome) I know both people from both the MSE team and the Project Stream team. Project Stream doesn't use MSE (it uses WebRTC) and the

(I work at Google, on Chrome) I know both people from both the MSE team and the Project Stream team. Project Stream doesn't use MSE (it uses WebRTC) and the code in Chrome to detect live streams and optimizing them has been around long time, (see, for example, this change from almost 4 years ago: https://codereview.chromium.org/692323002 https://codereview.chromium.org/692323002) and they've steadily added better support for live streams over the years. It's not "game-streaming tech in a web browser". It's just a few simple heuristics to function better for low-latency streams. You can read the code for yourself if you'd like: https://cs.chromium.org/chromium/src/media/renderers/video_renderer_impl.cc?type=cs&sq=package:chromium&g=0&l=240 https://cs.chromium.org/chromium/src/media/renderers/video_r...

deleted 8y ago
[deleted]
graphememes 8y ago
Nothing stopping the single vendor to stop servicing it though, other than a small collective of individuals. OP has a point.
- pthatcherg 8y ago
  It's been there for years and they've been steadily improving it. If anything, it will keep getting better, not go away.
  - mynewtb 8y ago
    Oh, blissful unawareness of the crazy untrustworthiness of Google product longevity.
- thisgoodlife 8y ago
  but it's an open source project, a lot of browsers based on the same code base will have the same functionality sooner or later.
  - deleted 8y ago
    [deleted]
  - graphememes 8y ago
    Open source projects die too
DaleCurtis 8y ago
(I work at Google, also on Chrome) Amusingly, we added the implicit signal a long time ago for 1FPS security cameras: https://bugs.chromium.org/p/chromium/issues/detail?id=338529 https://bugs.chromium.org/p/chromium/issues/detail?id=338529 Coincidentally, we're at FOMS right now talking to other browsers about standardizing an explicit signal that will provide additional effects on MSE buffering and audio preroll size.

deleted 8y ago

[deleted]

graphememes 8y ago

Nothing stopping the single vendor to stop servicing it though, other than a small collective of individuals. OP has a point.

pthatcherg 8y ago
It's been there for years and they've been steadily improving it. If anything, it will keep getting better, not go away.
- mynewtb 8y ago
  Oh, blissful unawareness of the crazy untrustworthiness of Google product longevity.
thisgoodlife 8y ago
but it's an open source project, a lot of browsers based on the same code base will have the same functionality sooner or later.
- deleted 8y ago
  [deleted]
- graphememes 8y ago
  Open source projects die too

DaleCurtis 8y ago

(I work at Google, also on Chrome) Amusingly, we added the implicit signal a long time ago for 1FPS security cameras: https://bugs.chromium.org/p/chromium/issues/detail?id=338529 https://bugs.chromium.org/p/chromium/issues/detail?id=338529 Coincidentally, we're at FOMS right now talking to other browsers about standardizing an explicit signal that will provide additional effects on MSE buffering and audio preroll size.