Save projects in this browser and reopen them. Reimport media to restore previews.
Real metadata inspection and transparent quality checks. No fabricated AI analysis.
Organize your editorial vision and keep decisions with the project.
Clip-level edits are editable in the browser. Multi-track compositing and effects require later development.
Import audio and add it to the audio lane. Listen to your music while reviewing clips.
Export an experimental FCPXML timeline and a human-readable edit decision list. Source paths are placeholders and require relinking.
Analyze actual video frames on your device to identify scene changes, exposure, and visual detail. These are explainable computer-vision measurements, not emotional understanding or cloud AI. Results stay in this browser session.
Choose an imported video. We sample frames at regular intervals and flag large visual differences. Long footage may take time on an iPad.
Waiting for footage.
Import an existing SRT subtitle file from a transcription tool, then search the actual dialogue and generate timecoded story markers. This version does not transcribe audio itself.
Compare measured brightness, detail and detected visual changes. These are starting points for your editorial judgment, not guarantees of shot quality.
Run scene detection to see recommendations.
Keep the original editing workspace above. Use this analysis alongside your manual timeline, creative directions and experimental Resolve export.
Turn your footage notes and imported subtitles into an editable shot plan. This version builds a real, reviewable cut list from timecodes and text matches; it does not pretend to understand emotion or generate a rendered film.
No footage or subtitles have been processed in this workspace.
Add specific source ranges from any video. These become part of the same rough-cut plan.
Change the order or remove selects before exporting. The exports reference source filenames and time ranges; relinking and compatibility must be checked in Resolve.
For true automatic transcription, semantic shot recognition, and cloud projects, a processing backend is still required. EDL supports one simplified video track; frame rates and source reel mapping are approximate.