Record restored Kiyo Pro buffer ingest
This commit is contained in:
parent
2347495824
commit
88b08a7dae
3 changed files with 14 additions and 18 deletions
|
|
@ -62,21 +62,18 @@ a named invariant that the native runtime cannot protect yet.
|
|||
|
||||
## Next
|
||||
|
||||
1. Recover the Kiyo Pro KS acquire path, which currently enumerates but leaves
|
||||
its runtime smoke buffer empty with `KSSTATE_ACQUIRE failed: The handle is
|
||||
invalid`.
|
||||
2. Replace the frame-event diagnostic bridge with concrete direct capture
|
||||
1. Replace the frame-event diagnostic bridge with concrete direct capture
|
||||
drivers for Leap stereo IR first, then the
|
||||
other cameras.
|
||||
3. Feed those drivers into `MimirVideoCaptureDriverSource` and prove sustained
|
||||
2. Feed those drivers into `MimirVideoCaptureDriverSource` and prove sustained
|
||||
frame cadence in the rolling buffers.
|
||||
4. Add native audio capture workers for local mic, loopback, and network audio
|
||||
3. Add native audio capture workers for local mic, loopback, and network audio
|
||||
feeds.
|
||||
5. Bind Aquarium UI to the synchronization hub so buffer depth, stream cadence,
|
||||
4. Bind Aquarium UI to the synchronization hub so buffer depth, stream cadence,
|
||||
source timestamps, and output settings are visible and adjustable.
|
||||
6. Move GPU feature extraction, fusion, material fitting, render budgeting, and
|
||||
5. Move GPU feature extraction, fusion, material fitting, render budgeting, and
|
||||
Spout2 publication into Aquarium.
|
||||
7. Move mic alignment, room suppression, voice separation, spatialization, and
|
||||
6. Move mic alignment, room suppression, voice separation, spatialization, and
|
||||
stem generation into Faust/native DSP.
|
||||
8. Keep the OBS bridge witness ledger as evidence before expanding receiver
|
||||
7. Keep the OBS bridge witness ledger as evidence before expanding receiver
|
||||
machinery.
|
||||
|
|
|
|||
|
|
@ -25,3 +25,4 @@
|
|||
{"ts":"2026-05-22T03:35:00+00:00","type":"verification","status":"ok","note":"Rechecked the final full local topology after the regular Kiyo was moved to a rear port and a mouse moved into the Leap USB neighborhood. All five camera devices / six optical sensors remained visible and cadence stayed healthy. High-rate Eye run: Leap 110.84 fps, Kiyo Pro 25.08 fps, regular Kiyo 30.18 fps, PS3 Eye 0 187.59 fps, PS3 Eye 1 187.02 fps. Full-frame Eye run: Leap 110.76 fps, Kiyo Pro 25.14 fps, regular Kiyo 30.18 fps, PS3 Eye 0 59.66 fps, PS3 Eye 1 59.95 fps. Mouse traffic does not reproduce the Focusrite-induced Leap collapse."}
|
||||
{"ts":"2026-05-22T04:10:00+00:00","type":"implementation","status":"ok","note":"Added a diagnostic frame-event path from native camera probes into Mimir.Runtime rolling buffers. MimirFrameEventProcessStreamSource reads JSON-line video-frame metadata into MimirVideoFrameDescriptor samples; KS and repo-owned PS3 Eye probes can emit those frame events. This is a playground witness for Aquarium UI/cadence, not the final pixel hot path."}
|
||||
{"ts":"2026-05-22T04:45:00+00:00","type":"verification","status":"partial","note":"Mimir.BufferSmoke loaded the probe runtime config, started the KS and PS3 Eye frame-event probes, polled MimirSynchronizationHub, and confirmed live samples in rolling buffers for leap-stereo-ir, kiyo-rgb, ps3-eye-0, and ps3-eye-1. Kiyo Pro is declared but empty: the KS path enumerates the device and modes, then fails at KSSTATE_ACQUIRE with ERROR_INVALID_HANDLE. PnP camera interface reports OK, composite reports OK, media interface reports Error, and non-elevated pnputil restart is denied."}
|
||||
{"ts":"2026-05-22T05:05:00+00:00","type":"verification","status":"ok","note":"After replugging the Kiyo Pro, all Pro PnP interfaces reported OK and the KS probe again measured 1280x720 MJPG at 24.97 fps and 1920x1080 MJPG at 25.19 fps. Mimir.BufferSmoke with --require-samples then confirmed all five declared local optical buffers received samples: kiyo-pro-rgb 99, kiyo-rgb 120, leap-stereo-ir 401, ps3-eye-0 937, ps3-eye-1 937 over the 8 second smoke run. Pro remains UsbHighSpeed and ~25 fps, but it is now in the runtime buffers."}
|
||||
|
|
|
|||
|
|
@ -152,12 +152,10 @@ current_status:
|
|||
Kiyo 30.18 fps, PS3 Eye 0 59.66 fps, and PS3 Eye 1 59.95 fps. A mouse in
|
||||
the Leap USB neighborhood does not reproduce the Focusrite-induced collapse.
|
||||
next_action: >
|
||||
Recover or replug the Kiyo Pro KS acquire path, then rerun
|
||||
Mimir.BufferSmoke with `--require-samples` until all declared local optical
|
||||
buffers are non-empty. Current smoke proves live rolling-buffer samples for
|
||||
Leap stereo IR, regular Kiyo, and both PS3 Eyes; Kiyo Pro still enumerates
|
||||
but fails KSSTATE_ACQUIRE with ERROR_INVALID_HANDLE. After that, replace the
|
||||
diagnostic JSON-line process bridge with direct native capture drivers that
|
||||
push buffer handles into Mimir.Runtime. Keep the Focusrite away from the
|
||||
Leap USB neighborhood and treat Kiyo Pro as a ~25 fps source until its
|
||||
Replace the diagnostic JSON-line process bridge with direct native capture
|
||||
drivers that push buffer handles into Mimir.Runtime. Current
|
||||
Mimir.BufferSmoke with `--require-samples` proves all five declared local
|
||||
optical buffers receive samples after replugging the Kiyo Pro: Leap stereo
|
||||
IR, Kiyo Pro, regular Kiyo, and both PS3 Eyes. Keep the Focusrite away from
|
||||
the Leap USB neighborhood and treat Kiyo Pro as a ~25 fps source until its
|
||||
SuperSpeed negotiation is fixed.
|
||||
|
|
|
|||
Loading…
Reference in a new issue