Mimir/state/evidence.jsonl
2026-05-18 16:08:14 +01:00

33 lines
11 KiB
JSON

{"ts":"2026-05-18T00:00:00+00:00","type":"decision","status":"ok","note":"Use FFmpeg SRT endpoints plus OBS Media Source for v1; OBS plugin or fork is not justified until standard ingest fails a concrete invariant."}
{"ts": "2026-05-18T09:55:45+00:00", "type": "verification", "status": "ok", "note": "State helper and sender dry-run produce valid repo status and SRT URLs with explicit ports for the example config."}
{"ts": "2026-05-18T10:24:49+00:00", "type": "deployment", "status": "ok", "note": "Neighbor sender 192.168.1.84 has LocalCastBridge under C:\\Meta\\LocalCastBridge, FFmpeg 8.1.1 with SRT/h264_nvenc, and desktop start/stop launchers targeting receiver 192.168.1.66 ports 5100/5101."}
{"ts": "2026-05-18T10:27:41+00:00", "type": "deployment", "status": "ok", "note": "Receiver OBS Untitled scene now has Neighbor PC - Video and Neighbor PC - Focusrite ffmpeg_source Media Sources listening on SRT ports 5100 and 5101; original scene JSON was backed up before edit."}
{"ts": "2026-05-18T10:52:05+00:00", "type": "deployment", "status": "ok", "note": "Installed Voicemeeter and SoundVolumeView on sender, added system-loopback using DirectShow device Voicemeeter Out B3 on SRT port 5102, and added matching OBS source Neighbor PC - System Audio."}
{"ts": "2026-05-18T11:38:25+00:00", "type": "fix", "status": "ok", "note": "Transmission failure traced to three issues: stale OBS SRT source state, sender live launcher splitting/closing FFmpeg due Start-Process/stdin handling, and SSH-launched gdigrab seeing a 1024x768 remote desktop with capture error 5. Patched sender-start with quoted argument string, -nostdin, repo-root logs, and set sender video config to 1024x768; OBS restarted and listening on UDP 5100-5102."}
{"ts": "2026-05-18T11:39:19+00:00", "type": "decision", "status": "ok", "note": "Ambisonic AquaSynth path should use one clocked multichannel capture feeding a declared ambisonic bus; four heterogeneous mics must not be treated as raw first-order A-format without geometry and calibration."}
{"ts": "2026-05-18T11:43:08+00:00", "type": "fix", "status": "ok", "note": "Madman's interactive launcher could not resolve winget aliases for SoundVolumeView, so desktop CMD files now use absolute winget-link paths. Sender video config restored to 1920x1080 because 1024x768 was only the SSH session display and captured a slice."}
{"ts": "2026-05-18T11:45:18+00:00", "type": "fix", "status": "ok", "note": "Replaced path-heavy desktop CMD launchers with PowerShell wrappers start-localcast-desktop.ps1 and stop-localcast-desktop.ps1 after cmd.exe parsed Voicemeeter/SoundVolumeView paths incorrectly on Madman's interactive desktop."}
{"ts": "2026-05-18T11:50:22+00:00", "type": "decision", "status": "ok", "note": "Live adaptive sync research supports a two-loop design: slow SRO estimation/variable-rate resampling plus faster delay/TDOA tracking; prove with a two-mic harness before feeding Ambisonic AquaSynth."}
{"ts": "2026-05-18T11:52:12+00:00", "type": "decision", "status": "ok", "note": "AquaSynth Ambisonic output must include a playback profile: speaker layout decoder plus per-speaker delay/gain/response correction and latency ledger; playback calibration is separate from capture sync."}
{"ts": "2026-05-18T11:55:34+00:00", "type": "decision", "status": "ok", "note": "Speaker feedback should be mined as an online system-identification signal: estimate a speaker-to-mic transfer matrix with confidence/convergence gates, separate from clock sync, localization, and Ambisonic decoding."}
{"ts": "2026-05-18T12:01:09+00:00", "type": "decision", "status": "ok", "note": "Visual tracking subsystem assumes PlayStation Eye / PS3 Eye cameras for high-rate low-res tracking; PS2 EyeToy is only a naming confusion/rejected path."}
{"ts": "2026-05-18T12:16:09+00:00", "type": "decision", "status": "ok", "note": "Visual rig is two PS3 Eyes for high-rate low-res tracking, two Razer Kiyo-class RGB/mic cameras (one Pro), and one Leap Motion/LeapUVC stereo IR sensor for near-field fusion; all publish into one world model."}
{"ts": "2026-05-18T12:21:18+00:00", "type": "constraint", "status": "ok", "note": "LeapUVC driver mode makes the Leap Motion appear as a generic UVC device and prevents addressing it through Ultraleap software; do not require LeapUVC raw frames and Ultraleap tracking simultaneously unless the actual machine proves both can coexist."}
{"ts": "2026-05-18T12:25:08+00:00", "type": "decision", "status": "ok", "note": "Fusion/rendering approach should follow EpiphanyAquarium domain-cache discipline: world-space semantic claims are truth, volumetric brushstroke/splat packets are cached render lowerings, and ambisonics reads listener/source claims rather than rendered geometry."}
{"ts": "2026-05-18T12:32:40+00:00", "type": "decision", "status": "ok", "note": "GPU fusion/splatting pass: use pinned host frame rings, async CUDA uploads, GPU feature/marker/stereo extraction, GPU-shaped observation and brush packet buffers, and CUDA/Vulkan/D3D splat rendering with minimal readback; CPU owns orchestration and semantics."}
{"ts": "2026-05-18T12:46:08+00:00", "type": "verification", "status": "partial", "note": "Calibration harness enumerated the local rig: LeapUVC raw IR video, two Razer Kiyo-class RGB cameras, Scarlett/Kiyo/PS3 Eye microphones, and Scarlett speakers are accessible; both PS3 Eye video interfaces are attached but report Windows problem code 28 (missing video-side driver)."}
{"ts": "2026-05-18T13:14:03+00:00", "type": "decision", "status": "ok", "note": "PS3 Eye video driver path should prefer the opentrack open driver via Zadig/libusb on interface MI_00; CL Eye remains historical reference only, not a repo dependency or redistribution target."}
{"ts": "2026-05-18T13:24:02+00:00", "type": "verification", "status": "partial", "note": "Footage status: LeapUVC and two Kiyo-class cameras produce snapshots; PS3 Eye video still needs opentrack/Zadig driver. LeapUVC MSMF accepted 320x240x120 and reported about 115 fps, but rough OpenCV measured throughput was about 52 fps in a short probe; Kiyo FPS mode probes timed out."}
{"ts": "2026-05-18T13:48:09+00:00", "type": "verification", "status": "partial", "note": "PS3 Eye MI_00 interfaces now bind as libusb-win32 and opentrack enumerates valid modes up to 320x240@205Hz/640x480@83Hz, but frame reads fail with payload error data[1]=78; next cuts are libusbK or WinUSB fallback and one-camera/direct-port USB tests."}
{"ts": "2026-05-18T13:51:32+00:00", "type": "verification", "status": "partial", "note": "USB topology after PS3 Eye driver install: Eyes, Kiyos, and Leap share an external hub/root path; one PS3 Eye composite/audio side and two descriptor-failed devices show Unknown while opentrack mode enumeration works but frame streaming fails. Treat hub topology/bandwidth/scheduling as live suspect."}
{"ts": "2026-05-18T13:56:00+00:00", "type": "verification", "status": "partial", "note": "With one PS3 Eye active after hub replug and switching to the other Eye, opentrack again enumerates high-rate modes but frame reads fail with payload error data[1]=78/bad header. This reduces suspicion of a single bad Eye and points to libusb0/backend or hub streaming."}
{"ts": "2026-05-18T14:02:51+00:00", "type": "verification", "status": "partial", "note": "Both PS3 Eyes direct to motherboard and live MI_00 instances bound as libusbK: opentrack mode-test now reports all listed modes GOOD including 320x240@30, but frame-test still fails with payload error data[1]=78/79 and bad headers. Stale Unknown PS3 Eye instances from previous hub path remain in PnP."}
{"ts": "2026-05-18T14:05:40+00:00", "type": "verification", "status": "failed", "note": "WinUSB on the two live PS3 Eye MI_00 instances still enumerates high-rate modes but frame streaming fails: one device open hit Access is denied, the other repeated payload error data[1]=78/79 until killed. libusb0, libusbK, and WinUSB have all failed frame reads via opentrack on this machine."}
{"ts": "2026-05-18T14:22:36+00:00", "type": "verification", "status": "partial", "note": "Audio-field sidecar added and offline FOA encode verified; current PortAudio enumeration shows no matching six-channel WASAPI input device, so live Ambisonic capture needs a shared six-input interface/profile or a separately proven adaptive sync path before using independent USB microphones."}
{"ts": "2026-05-18T14:25:36+00:00", "type": "verification", "status": "ok", "note": "PS3 Eye video path found: AllanCat PS3 Eye Universal Driver / PS3EyeDirectShow exposes both Eyes as DirectShow indices 3 and 4 after registering the source filter for two cameras; simultaneous default 640x480 capture produced about 30 fps from both. High-FPS DirectShow mode negotiation remains unproven."}
{"ts": "2026-05-18T14:48:48+00:00", "type": "verification", "status": "ok", "note": "PS3 Eye frame-rate squeeze: OpenCV DirectShow indices are reliable only at default 640x480@30; FFmpeg DirectShow capture by device name negotiates high-rate modes. Both PS3 Eyes simultaneously delivered 320x240@60 with 300 frames per Eye over five seconds. Dual 640x480@60 works but settles around 54-56 fps per Eye. Requests above 60 fps through the installed PS3EyeDirectShow filter do not increase delivered frame rate."}
{"ts": "2026-05-18T14:50:58+00:00", "type": "verification", "status": "partial", "note": "Audio profile updated for actual distributed rig: local Focusrite shielded cardioid and neighbor Focusrite shotgun are dialogue anchors; Kiyo/PS Eye mics are spatial/context sources. Local PortAudio/WASAPI probe: Scarlett input accepts 48 kHz and rejects 96 kHz; Scarlett output accepts 44.1 kHz and rejects 48/96 kHz, so ASIO/native Focusrite access must be checked before high-rate calibration."}
{"ts": "2026-05-18T14:55:13+00:00", "type": "decision", "status": "ok", "note": "Audio field live output may use bounded buffering: latency is acceptable while delay/SRO estimates settle, but cache depth must converge toward real-time. Core audio code now has testable seams for buffers, latency policy, injectable capture/alignment/encoder/sink ports, and pipeline orchestration."}
{"ts": "2026-05-18T14:57:32+00:00", "type": "decision", "status": "ok", "note": "Sensor-fusion sidecar starts with semantic observation authority: calibrated cameras plus timestamped 2D marker observations triangulate into cached 3D point claims, then lower to PLY/brush/splat packets. Capture adapters and render lowerings stay outside the pure fusion core so unit tests can inject synthetic cameras, frames, and observations."}
{"ts": "2026-05-18T15:07:24+00:00", "type": "decision", "status": "ok", "note": "OBS visualization boundary: LocalCastBridge should emit typed render-frame packets from the sensor-fusion cache; Aquarium Engine should consume them, render points/brushes/splats to a GPU render target, and publish that texture as Spout sender 'LocalCastBridge Point Cloud'. Render packets carry visual presentation and audio-alignment timestamps so latency can converge with the ambisonic output timeline."}