Cinder routes screen exports through hardware encoders
Cinder is a newly forked open-source screen recorder and editor that focuses on hardware-accelerated export for Windows and other platforms. It leverages system ffmpeg with hardware encoder selection (NVENC, QSV, AMF) and utilizes OffscreenCanvas workers to achieve significantly faster video export speeds compared to its upstream project, OpenScreen. The project is an early-stage technical development aimed at optimizing the video encoding pipeline for screen recording applications.
Key Takeaways
- Cinder is an MIT fork of OpenScreen focused on hardware-accelerated exports for Windows and other platforms.
- The export path uses system ffmpeg with hardware encoder selection: NVENC, QSV, AMF, or libx264 as fallback.
- The README says 1080p export speed rises from about 6 fps in the upstream path to 25–40 fps peak in Cinder.
- Cinder uses an OffscreenCanvas worker pool plus MessagePort transfers to keep frame handling parallel and zero-copy.
- The project is early-stage: installers are not yet shipped, and the README labels the export pipeline a preview.
Why It Matters
Cinder tackles a concrete bottleneck in screen recording: MP4 export. By moving encoding into system ffmpeg and pushing frame rendering through OffscreenCanvas workers and zero-copy MessagePort transport, it aims to cut the time users spend waiting after recording. The competitive signal is in the implementation details: hardware encoder selection across NVENC, QSV, AMF, and x264, plus a preview-stage pipeline that still inherits OpenScreen’s recording and editor UX. The next metric to watch is whether the project ships pre-built installers and whether its own README benchmarks hold at the stated 25–40 fps peak for 1080p exports.
Read full article at github.com