Documentation Index
Fetch the complete documentation index at: /llms.txt
Use this file to discover all available pages before exploring further.
How many camera frames reach the app each second, how many the system threw away instead, and why
AVCaptureVideoDataOutputSampleBufferDelegate. One reading per rolling
one-second window while a session runs, plus a single reading the first time
a delegate class is seen, naming it.
Real output from basset request get, captured against a running
AVCaptureSession:
CAPTURED ELAPSED INSTRUMENT
launch 7641138352239166559
2026-08-23T13:11:17.055Z +0.0s camera.frames.delivery(videoFrames)
├─ windowNanoseconds 999996459
├─ framesDeliveredCount 0
├─ framesDroppedCount 0
├─ delegateDurationNanoseconds 0
└─ delegateDurationPeakNanoseconds 0
2026-08-23T13:11:18.055Z +1.0s camera.frames.delivery(videoFrames)
├─ windowNanoseconds 1000004166
├─ framesDeliveredCount 23
├─ framesDroppedCount 0
├─ delegateDurationNanoseconds 211291
└─ delegateDurationPeakNanoseconds 14833
2026-08-23T13:11:19.054Z +2.0s camera.frames.delivery(videoFrames)
├─ windowNanoseconds 999502834
├─ framesDeliveredCount 30
├─ framesDroppedCount 0
├─ delegateDurationNanoseconds 268332
└─ delegateDurationPeakNanoseconds 13833
framesDroppedCount is counted even when the app’s own delegate implements
only the drop callback — the reading still shows delivery, rather than
silently reporting zero for a camera that is running fine.