From 7ffb2d7fa4b73df615fa7439b18b8560047954bc Mon Sep 17 00:00:00 2001 From: Meta Vens Date: Fri, 22 May 2026 00:08:00 +0100 Subject: [PATCH] Record restored local sensor pull --- docs/native-capture-cadence.md | 34 ++++++++++++++++++++++++++++++++++ state/evidence.jsonl | 1 + state/map.yaml | 7 ++++++- 3 files changed, 41 insertions(+), 1 deletion(-) diff --git a/docs/native-capture-cadence.md b/docs/native-capture-cadence.md index 976da32..0bd2510 100644 --- a/docs/native-capture-cadence.md +++ b/docs/native-capture-cadence.md @@ -457,3 +457,37 @@ Conclusion: Raven's PS3 Eye driver binding is fixed enough to open the device, but the current Raven USB path/device state is not delivering usable cadence. Next Raven work is port/controller isolation and a clean single-process cadence run before treating the Eye as a usable remote timing witness. + +## 2026-05-22: Restored Local Five-Device Pull + +After moving the Raven PS3 Eye back to the Mimir host, local enumeration showed: + +- LeapUVC stereo IR pair; +- regular Razer Kiyo; +- two PS3 Eyes; +- Focusrite Scarlett Solo moved away from the Leap USB neighborhood. + +The Kiyo Pro was not local for this run. + +Simultaneous local results with both PS3 Eyes at `320x240@187`: + +| Device | Mode | Delivered FPS | +| --- | --- | ---: | +| LeapUVC | 640x240 YUY2 | 106.07 | +| Kiyo | 1920x1080 MJPG | 30.33 | +| PS3 Eye 0 | 320x240 Bayer | 186.57 | +| PS3 Eye 1 | 320x240 Bayer | 186.14 | + +Simultaneous local results with both PS3 Eyes at `640x480@60`: + +| Device | Mode | Delivered FPS | +| --- | --- | ---: | +| LeapUVC | 640x240 YUY2 | 108.07 | +| Kiyo | 1920x1080 MJPG | 30.34 | +| PS3 Eye 0 | 640x480 Bayer | 57.79 | +| PS3 Eye 1 | 640x480 Bayer | 58.08 | + +Conclusion: the current local topology can run all local sensors in parallel: +Leap stereo plus regular Kiyo plus both PS3 Eyes. With the Focusrite out of the +Leap neighborhood and the Kiyo Pro absent, Leap stays close to its previous +best cadence instead of falling into the old ~81 fps band. diff --git a/state/evidence.jsonl b/state/evidence.jsonl index 89254c9..cd9004a 100644 --- a/state/evidence.jsonl +++ b/state/evidence.jsonl @@ -19,3 +19,4 @@ {"ts":"2026-05-22T01:30:00+00:00","type":"verification","status":"partial","note":"After splitting cameras across Mimir and Raven, the local Mimir host enumerated LeapUVC, regular Kiyo, and one PS3 Eye. Local simultaneous pull with PS3 Eye 320x240@187 delivered Leap 81.34 fps, Kiyo 30.27 fps, and PS3 Eye 185.56 fps. Leap+Kiyo only delivered Leap 82.77 fps and Kiyo 16.83 fps. Leap-only same-session baseline delivered 84.18 fps, with best fast-combined scenario 92.87 fps and 640x120 baseline 173.62 fps. Offloading Kiyo Pro and one PS3 Eye did not restore the previous ~110.8 fps Leap result; current hypothesis shifts to Leap port/controller/device state or KS/usbvideo behavior, not only total local camera bandwidth."} {"ts":"2026-05-22T01:45:00+00:00","type":"verification","status":"ok","note":"Moving the Focusrite Scarlett Solo away from the Leap USB neighborhood substantially recovered local split-host cadence. Leap-only baseline rose to 95.48 fps, best fast-combined scenario to 101.67 fps, and 640x120 baseline to 192.83 fps. With local Leap + regular Kiyo + one PS3 Eye at 320x240@187 active, Leap delivered 105.10 fps, Kiyo 30.17 fps, and PS3 Eye 185.81 fps. The split-host local set is viable; the prior ~81 fps Leap band was caused by local USB layout including the Focusrite, not just camera count."} {"ts":"2026-05-22T02:05:00+00:00","type":"verification","status":"partial","note":"Raven PS3 Eye raw interface initially had no driver binding. Exported the working Mimir host libwdi WinUSB driver package from oem26.inf, copied it to Raven under C:\\Meta\\mimir-ps3eye-winusb-driver, added the libwdi self-signed certificate to Raven Root and TrustedPublisher stores, and installed it as oem34.inf with pnputil. Raven now reports VID_1415&PID_2000&MI_00 as USBDevice OK, provider libwdi, service WinUSB. The copied ps3eye_dual_cadence.exe opens the device, but cadence is not viable yet: 320x240@187 delivered 132.24 fps then 78.93 fps, and 640x480@60 delivered 6.32 fps with multi-second gaps. Driver open is solved; Raven USB path/device cadence still needs isolation."} +{"ts":"2026-05-22T02:35:00+00:00","type":"verification","status":"ok","note":"Moved the Raven PS3 Eye back to the Mimir host. Local enumeration showed LeapUVC, regular Kiyo, and two PS3 Eyes; Kiyo Pro was not local. With Focusrite away from the Leap USB neighborhood, all local sensors ran in parallel cleanly. With both PS3 Eyes at 320x240@187: Leap 106.07 fps, Kiyo 30.33 fps, PS3 Eye 0 186.57 fps, PS3 Eye 1 186.14 fps. With both PS3 Eyes at 640x480@60: Leap 108.07 fps, Kiyo 30.34 fps, PS3 Eye 0 57.79 fps, PS3 Eye 1 58.08 fps. Current local topology is viable for Leap stereo + regular Kiyo + both PS3 Eyes."} diff --git a/state/map.yaml b/state/map.yaml index 084066c..65bf0d0 100644 --- a/state/map.yaml +++ b/state/map.yaml @@ -130,7 +130,12 @@ current_status: now has the same libwdi WinUSB binding as the local Eye and can be opened by the copied cadence probe, but Raven Eye cadence is currently unusable: 320x240@187 delivered 132.24 fps then 78.93 fps, and 640x480@60 delivered - 6.32 fps with multi-second gaps. + 6.32 fps with multi-second gaps. Moving that Eye back to the Mimir host + produced the current clean local topology: LeapUVC, regular Kiyo, and two + PS3 Eyes run in parallel while Kiyo Pro stays off-host. With both Eyes at + 320x240@187, Leap delivered 106.07 fps, Kiyo 30.33 fps, and the Eyes 186.57 + / 186.14 fps. With both Eyes at 640x480@60, Leap delivered 108.07 fps, Kiyo + 30.34 fps, and the Eyes 57.79 / 58.08 fps. next_action: > Move the raw PS3 Eye probe into the repo or replace it with the first runtime capture driver, then isolate Raven's PS3 Eye port/controller until