Pick up new cameras as they are plugged in
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 48/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 停滞
- 技术栈
- linux, rust
调研方向
Start in main, where v4l::context::enum_devices currently scans cameras only during startup. Read the Tokio setup and the existing Device::new flow, then implement the requested background scan of /dev/v4l/by-id/ using Device::with_path. Done means newly plugged-in cameras are detected without restarting, while stable paths preserve camera settings when devices are unplugged and reconnected.
由索引模型根据 Issue 内容生成。
描述
The following code is present in main:
// available_camera_paths is only updated at initial start, however, this could be better changed to run when a camera is plugged in or removed.
for node in v4l::context::enum_devices() {
let mut device = Device::new(node.index())?;
let Ok(modes) = CameraMode::fetch_all(&device) else {
continue;
};
let initial_mode = *modes.first().ok_or("Error Creating a CameraThreadHandle: Failed to initialize camera as no valid Camera operating modes were provided by video4linux. (Check the camera as this was an OS-level issue!)")?;
// If can't query or create a stream, then it can't be displayed.
if H264CameraReader::new(&mut device, initial_mode).is_ok() {
available_camera_paths.push(node.path().to_path_buf());
}
This means that new video capture devices won't be detected if they're plugged in, making testing rather difficult.
We should make it such that a background thread refreshes the available cameras when a new one is plugged in. However, we're already using Tokio here, so we could use an async task instead!
Either way, the cameras should update for ease of use (and to prevent having to restart the backend at comp!)
Edit:
A quick implementation checklist:
- Add a new background thread/task to scan
/dev/v4l/by-id/for new entries - Initialize devices via
Device::with_path- Right now, we just use
Device::new, which uses indices. That won't work for competition -- if cameras unplug, we'll lose the settings for that camera alongside its assigned index!!
- Right now, we just use
- 主要语言
- Rust
- 星标
- 1
- 派生
- 3
- PR 合并指标
- 30 天内没有已合并 PR
环境准备
我们还没有检查这个项目的环境配置文件。先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
Sooner-Rover-Team/RoverGUI 的其他 Issue
-
Look into styles未关闭
难度 4/5 3-5 天 新手友好度 35/100
-
难度 2/5 1-3 小时 新手友好度 55/100
-
难度 2/5 1-3 小时 新手友好度 45/100
-
good first issue
难度 3/5 1-2 天 新手友好度 45/100
-
devops frontend good first issue
难度 2/5 1-3 小时 新手友好度 48/100
查看 Sooner-Rover-Team/RoverGUI 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 92/100
bytecodealliance/wasmtime#14433 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 68/100
-
bug
难度 2/5 1-3 小时 新手友好度 76/100
-
难度 2/5 1-3 小时 新手友好度 88/100
维护者通常 1 天内回复