Overview
OpenCut is rebuilding its editor from the ground up, separating the stated usable OpenCut Classic line from a current rewrite scaffold. The series traces the proposed shared foundation—from coordinated scene state and exact time to rendering and explicit timeline operations—then tests whether web, desktop, API, and future automation actually share those semantics. The repository shows serious workspace and UI groundwork, but not a finished replacement, integrated core, feature parity, or stable Editor API.
Learning outcomes
- OpenCut’s rewrite is a ground-up architectural project, not yet a drop-in replacement for OpenCut Classic.
- A shared core would matter only if scene, time, rendering, and edit semantics remain consistent across surfaces.
- The former editor’s MediaTime, rational FrameRate, typed tracks, and ripple adjustments show requirements, not current rewrite proof.
- The repository demonstrates web, desktop, API, workspace, and UI scaffolding, but not an integrated core or feature parity.
Keywords
Preview every chapter · Unlock full text, audio, and video from chapter 4
PlansFAQ
Is OpenCut’s rewrite ready to replace OpenCut Classic?
No; at the pinned repository state, the rewrite is not a drop-in replacement for OpenCut Classic. Its web editor is a placeholder, the desktop app has placeholder panels, and the API lacks editing operations.
What is OpenCut’s shared-core idea meant to solve?
It is meant to keep one scene, time model, rendering path, and editing semantics consistent across web, desktop, and automation surfaces. The repository presents this as a direction, not delivered integration.
Why does OpenCut use an explicit time model?
In OpenCut’s documented former design, integer MediaTime and rational FrameRate align frames, keyframes, playback, audio, and export more precisely than floating-point seconds. This addresses rounding drift, not scheduling or ripple policy.
What evidence would show that OpenCut’s rewrite has become a shared foundation?
Evidence would include a working edit loop plus domain contracts that produce consistent results across preview, playback, export, and external clients. The current snapshot shows shells and scaffolding, not that integration.