This quarter we shipped the new capture pipeline to every desktop user. Recordings now start in under a second on most machines, the editor opens files twice as fast, and the number of failed uploads dropped by more than half. The remaining work is mostly about long recordings on older laptops, where memory use still grows too quickly after the first twenty minutes.
Segments are uploaded while the recording is still running, which means a ten minute video is usually ready to share a few seconds after the user clicks stop. We also added a resumable upload path for flaky connections; it has already recovered more than 4,000 recordings that would have failed before.
| Metric | Q2 | Q3 | Change |
|---|---|---|---|
| Median time to first frame | 1.8 s | 0.7 s | −61% |
| Failed uploads per 1,000 recordings | 9.4 | 4.1 | −56% |
| Average file size per minute (1080p) | 38 MB | 26 MB | −32% |
| Crash-free sessions | 99.31% | 99.72% | +0.41 pt |
Memory growth on long recordings is the biggest open issue. We see it mostly on machines with 8 GB of RAM when the camera overlay is enabled, and it can lead to dropped frames after about half an hour. A fix for the frame pool is in review and should land in the next release.
For Q4 we want to finish the work on long recordings and start testing the new encoder with real customer content.