Repository navigation
fix(uvc): detect capture interfaces beyond index0 - #364
Conversation
|
Thanks for the PR. It's actually a very clean solution ^^ I knew of those Creality cams exposing two different nodes but as I don't own one, I didn't bother to log them correctly as I would have to assume things. |
Thanks for the thoughtful review and for giving an AI-assisted contribution a fair chance. |
As long as I won't get too much AI PRs and the PR text is not a wall of text, I will consider them if they make sense. As a note to your config: |
Leftovers from the investigation of the problem. |
|
Sry that it took so long to release. I completely forgot this PR 🙈 |
Fixes #363.
What changed
UVC discovery now registers symlinked V4L2 nodes that enumerate capture formats instead of assuming the usable interface always ends in
index0.This supports composite cameras such as Creality CAM, where index0 exposes H264/HEVC and index2 exposes MJPEG, while excluding metadata-only nodes with no capture formats.
Validation
1d6c:0103v4l2-ctlpython -m compileall -q crowsnestruff format --checkruff checkbasedpyrightAI disclosure
This PR was prepared with assistance from OpenAI Codex. I reproduced and tested the issue on the physical Creality CAM hardware, reviewed the proposed change, and verified the resulting service behavior.