Camera 1: Spike — camera capture on Linux: V4L2, PipeWire or a crate #953

Closed
opened 2026-11-19 21:48:31 +00:00 by charles · 1 comment
Owner

Task 1 of the Camera plan (docs/superpowers/plans/2026-11-19-camera.md, section "Task 1"; spec docs/superpowers/specs/2026-11-19-fluxer-native-camera-design.md). The plan's "Owner decisions of 2026-11-19" section overrides the task text.

Depends on: nothing.

Task 1 of the Camera plan (`docs/superpowers/plans/2026-11-19-camera.md`, section "Task 1"; spec `docs/superpowers/specs/2026-11-19-fluxer-native-camera-design.md`). The plan's "Owner decisions of 2026-11-19" section overrides the task text. Depends on: nothing.
charles added this to the Camera milestone 2026-11-19 21:48:31 +00:00
Author
Owner

Camera 1 asks for one probe run on the Linux machine (spec §19 Q10, spikes §1.6). Non-blocking: Camera 10 starts on the documented facts.

From the branch camera-1-spike-capture-linux (or camera once merged), with the camera plugged in:

cargo run -p fluxer-capture --example camera_probe -- list
cargo run -p fluxer-capture --example camera_probe -- modes 0
cargo run -p fluxer-capture --example camera_probe -- capture 0

Please paste the output here. What to look for:

  • list reads sysfs only: the light must stay off. Each camera should appear once under cameras:, its metadata node marked skipped (this settles Q4).
  • modes 0 opens the camera without streaming: the light should stay off. It prints the driver, the device caps and every format, size and rate.
  • capture 0 streams for 5 s: the light comes on, then goes off when it prints closed. It prints the format, time to first frame, the measured rate, skipped frames and a mean brightness. No file is written and no picture data is printed.
  • Optional (Camera 10's Busy row): capture 0 20 in one terminal, then capture 0 in another while the first runs; the second should report EBUSY.

The probe refuses to run with FLUXER_CAMERA_FORBID set, so unset it if your shell has it.

Camera 1 asks for one probe run on the Linux machine (spec §19 Q10, *spikes §1.6*). Non-blocking: Camera 10 starts on the documented facts. From the branch `camera-1-spike-capture-linux` (or `camera` once merged), with the camera plugged in: ```text cargo run -p fluxer-capture --example camera_probe -- list cargo run -p fluxer-capture --example camera_probe -- modes 0 cargo run -p fluxer-capture --example camera_probe -- capture 0 ``` Please paste the output here. What to look for: - `list` reads sysfs only: the light must stay off. Each camera should appear once under `cameras:`, its metadata node marked `skipped` (this settles Q4). - `modes 0` opens the camera without streaming: the light should stay off. It prints the driver, the device caps and every format, size and rate. - `capture 0` streams for 5 s: the light comes on, then goes off when it prints `closed`. It prints the format, time to first frame, the measured rate, skipped frames and a mean brightness. No file is written and no picture data is printed. - Optional (Camera 10's `Busy` row): `capture 0 20` in one terminal, then `capture 0` in another while the first runs; the second should report `EBUSY`. The probe refuses to run with `FLUXER_CAMERA_FORBID` set, so unset it if your shell has it.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
charles/fluxer-native#953
No description provided.