A better API for querying device capabilities
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 35/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 冷清
- 技术栈
- rust
调研方向
Start by reviewing the existing Device::supported_formats API and the host implementations that expose device capabilities; the issue does not name specific files. Compare how hosts report sample formats and sample rates, including whether rates are ranges or discrete values. A useful first result is a consolidated account of those differences to inform a scalable querying API.
由索引模型根据 Issue 内容生成。
描述
CPAL's current approach to querying capabilities is the Device::supported_formats method, which aims to enumerate all possible formats supported by the device. Providing an exhaustive list of formats in this manner is not very scalable, especially as we anticipate adding support for alternate sample formats, audio data layouts (#367) and buffer sizes in the future.
#203 proposes a slimmer API that allows querying individual formats, though this is equally unscalable for users wishing to determine the full set of capabilities of a device.
I wonder if we can look to Vulkan's device capabilities API for inspiration here? Edit: I guess Vulkan has the advantage of co-ordinating with driver implementers on a standard for this, whereas we are restricted to working with what host's currently provide access to.
A useful first step might be to consolidate all our existing knowledge of how capabilities are exposed by each Host so that we can get a clearer idea of what we have to work with. E.g. are the same sample rates supported for all sample formats across all hosts? Are supported sample rates always described in continuous ranges? Or do some hosts provide supported sample rates only as a set of discrete integers?
- 主要语言
- Rust
- 星标
- 4k
- 派生
- 554
- 平均合并
- 3 天 3 小时
- 30 天内合并 PR
- 4
环境准备
- 提供 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
RustAudio/cpal 的其他 Issue
-
aaudio: dynamic buffer tuning never grows the buffer (set_buffer_size_in_frames reports Err on success)可能已有人在做 @dannyward630 于 3 天前认领。 未关闭host - aaudio platform - android
难度 2/5 1-3 小时 新手友好度 79/100
维护者通常 1 天内回复
-
WebAudio wasm build fails with wasm-bindgen panic=unwind closures可能已有人在做 @bogusyogi 于 12 天前认领。 未关闭host - webaudio platform - web
难度 2/5 1-3 小时 新手友好度 75/100
维护者通常 1 天内回复
-
code quality dependencies host - wasapi platform - windows
难度 5/5 一周以上 新手友好度 35/100
维护者通常 1 天内回复
-
host - pipewire platform - linux
难度 4/5 1-2 天 新手友好度 52/100
维护者通常 1 天内回复
-
WASAPI: default-device activation fails with RPC_E_CHANGED_MODE after endpoint-notification callbacks put thread-pool threads into an STA可能已有人在做 @dannyward630 于 4 天前认领。 未关闭correctness host - wasapi platform - windows
难度 4/5 3-5 天 新手友好度 20/100
维护者通常 1 天内回复
相似的 Issue
-
bug dependencies kind:fix priority: P3 ready-for-agent
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 76/100
维护者通常 2 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 78/100
swc-project/swc-next#1165 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 73/100
Alive24/shea-symphony#574 ·
-
难度 1/5 1 小时以内 新手友好度 84/100
维护者通常 1 天内回复