Requirements for multi-device timing while streaming.
@pthatcherg 已经在做这个了。
开始于 2019年8月26日。
评估
这个 Issue 还没有评估数据。
描述
This issue tracks discussion of protocol changes to allow multi-device synchronization of media playback while streaming. This was discussed at the Berlin F2F [1].
It's assumed that if there's one sender and one receiver the current protocol is sufficient to play out audio and video on the receiver with lip sync.
However, once there are multiple receivers, we'll need some timing metadata to be exchanged between the sender and receivers. Here are a few possible scenarios (not exhaustive):
- Sending audio to one device and video to another.
- Sending audio to multiple devices.
- Sending video to multiple devices.
- Sending audio and video to multiple devices (possibly with multiple audio and video tracks).
- Scenarios involving text tracks or metadata cues.
- Scenarios involving non-1.0-rate playback.
Not all of these may be in scope, however. Items 1 and 4 were pointed out as important in Berlin.
Next steps are to research what's feasible from an implementation point of view, and study the proposals in the following groups:
Multi-Device Timing CG Timing Object: https://webtiming.github.io/timingobject/
Media Timed Events TF: https://github.com/WICG/datacue/blob/master/explainer.md
[1] https://www.w3.org/2019/05/23-webscreens-minutes.html#x29
- 主要语言
- Bikeshed
- 星标
- 115
- 派生
- 21
- 平均合并
- 5 小时 2 分钟
- 30 天内合并 PR
- 2
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
w3c/openscreenprotocol 的其他 Issue
-
难度 5/5 一周以上 新手友好度 18/100
w3c/openscreenprotocol#380 ·
-
osp-application
难度 5/5 一周以上 新手友好度 35/100
w3c/openscreenprotocol#377 ·
-
难度 4/5 3-5 天 新手友好度 38/100
w3c/openscreenprotocol#376 ·
-
osp-application
难度 2/5 1-3 小时 新手友好度 55/100
w3c/openscreenprotocol#375 ·
-
osp-application question
难度 5/5 一周以上 新手友好度 30/100
w3c/openscreenprotocol#374 ·