Align Streaming Protocol Capabilities with Media Capabilities?
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 25/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 停滞
- 技术栈
- html
- 领域
- api
调研方向
Start by comparing the Open Screen Protocol streaming capability fields with the Media Capabilities API’s AudioConfiguration and VideoConfiguration, as the issue describes. Review the linked Media Capabilities issue 160 for the ongoing audio discussion. Done means deciding which listed capabilities belong in the protocol and resolving whether to add, retain, or drop them; the issue names no repository files or tests.
由索引模型根据 Issue 内容生成。
描述
Reviewing #225, I wondered how streaming protocol capabilities exposed in a streaming-capabilities-response mapped to capabilities defined in the AudioConfiguration and VideoConfiguration constructs in the Media Capabilities API.
For Video:
- The Open Screen Protocol has a
max-pixels-per-secondand asupports-rotationfield, neither of which match any property in the Media Capabilities API. When are these fields useful? If they are, should they be considered in the Media Capabilities API as well? If not, could they be dropped? - On top of HDR related properties that will be added to the Open Screen Protocol, Media Capabilities also has
scalabilityMode, which targets identifiers defined in WebRTC-SVC. Would that be worth adding to the Open Screen Protocol? - Media Capabilities also defines
hasAlphaChannel. That does not strike me as particularly useful in a remote streaming scenario though?
For Audio, Media Capabilities API also has:
samplerate. The Open Screen Protocol has [max-frames-per-second] for video capabilities, but no equivalent for audio.spatialRendering
Note that there is an ongoing discussion on these audio configuration capabilities in the Media Capabilities repo https://github.com/w3c/media-capabilities/issues/160.
- 主要语言
- 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 ·
查看 w3c/openscreenprotocol 的全部 Issue
相似的 Issue
-
BUG: catalog database credentials printed to logs at startup可能已有人在做 @cjboyle 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 70/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
-
backend bug ready-for-agent
难度 2/5 1-3 小时 新手友好度 78/100
geolens-io/geolens#3639 ·
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 78/100
apache/maven-enforcer#1074 ·
维护者通常 1 天内回复
-
bug libcudf
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 2 天内回复