{
  "schema": "sync-camera-research-findings-v1",
  "researchDates": [
    "2026-09-18"
  ],
  "findings": [
    {
      "cycle": "A",
      "title": "CoreMediaIO Extension and Daemon Relay Capacity",
      "finding": "The CoreMediaIO DAL plugin system extension and syncd IPC relay sustained zero frame drops, zero consecutive duplicate pictures, and zero unexplained missing sequence numbers across 23,664 measured frames over 600 seconds. Queue-to-relay latency (pts -> arrival) achieved median 3.22 ms and p95 5.74 ms on host-time timestamps. The native camera infrastructure is fully capable of lossless 1080p60 delivery."
    },
    {
      "cycle": "B",
      "title": "Chromium Capture Pipeline Loss and Repeating",
      "finding": "Under identical producer, daemon, and extension inputs, Chromium MediaStreamTrackProcessor capture delivered 30,031 arrivals containing 6,277 consecutive repeats (20.9% repeat rate), 4,529 zero-ms duplicate timestamp pairs, and 332 dropped frames. Median end-to-end latency expanded from 34.38 ms on native AVFoundation to 58.97 ms in Chromium, with p95 reaching 113.30 ms. The 50-55 FPS capture ceiling observed in browsers originates entirely within Chromium capture thread polling and IPC buffering."
    },
    {
      "cycle": "C",
      "title": "Paced Uncompressed Socket Backpressure",
      "finding": "Both arms revealed substantial sender-side backpressure in Node.js when transmitting uncompressed 1920x1080 RGBA frames (8.29 MB/frame) over a local stream socket (p95 write durations: 30.55 ms in AVF run, 39.48 ms in Chrome run). Because socket write times exceeded the 16.67 ms deadline interval, the producer skipped 12,335 and 11,914 ticks, bounding injected frame rates to ~39.4 FPS. Full 60 FPS uncompressed ingest requires zero-copy shared memory or frame pooling rather than socket byte streaming."
    }
  ]
}