Timeline assembly
Arrange source clips and remove unwanted intervals to evaluate how the editor handles a short sequence.
OpenCut is an open-source video editor for timeline-based work. The browser beta uses Classic while the team builds a new Rust-based editor.
Turn a transcript or clip inventory into an editing plan with in and out points and a short playback checklist.
Include source filenames, timestamps, target duration, and intended audience.
Copy the request into a new Floatboat conversation and provide the required material.
Download FloatboatPreview and copy the request. It is not sent automatically from this page.
Reference: OpenCut https://github.com/OpenCut-app/OpenCut Read the original documentation and check the current environment and dependencies. Propose any new installation or tool connection before proceeding. My task: Use the OpenCut README to distinguish Classic from rewrite plans. From my timecoded customer interview transcript, draft a 45-second cut list with source ranges, continuity checks and a review question for each cut. Mark uncertain timestamps and leave media editing for my approval. Expected deliverable: A cut list, review checkpoints, and a target export specification for a manual timeline edit.
OpenCut is a timeline editor positioned as an open-source alternative to CapCut. Its public browser beta runs the original Classic codebase. The team archives that code separately while building the next version in the main repository.
The rewrite is intended to share a Rust core across platforms and make room for plugins, an editor API and headless operation. Upstream also lists MCP among the planned capabilities. Keep an edit plan independent of those interfaces until the one you need is available and tested.
For a Floatboat workflow, prepare clip names, timecodes, a target duration and export checks. Use the browser editor to assemble and review the result by hand, and keep the source media and cut decisions available for a later revision.
Classic provides a browser editor for hands-on trials. The main repository tracks the replacement, so use the appropriate source when checking an editor behavior or following development.
Arrange source clips and remove unwanted intervals to evaluate how the editor handles a short sequence.
Start with the official early beta and verify that it accepts your media and can produce the output your workflow needs.
Follow the main repository for work on a shared core and plugin-oriented interfaces. Check the documented release status before designing around any new API.
Plan one short cut with a delivery target, then compare the exported file with the timeline. Check whether the intended trims, caption timing and playback survived the export.
Mark a candidate opening, the main quote and a clean closing in the transcript with timecodes. Assemble the selected intervals in the browser editor and verify that transitions preserve the meaning of each answer.
Order source recordings around one user task, then remove waiting time and repeated navigation. Review the short version against a checklist for visible labels and continuity before sharing the export.
Record the source filenames, in and out points and the reason for each replacement. Give the reviewer the new video and a change list so they can compare the intended edits with the actual playback.
Use representative clips and a small test project. Record how the beta handles import, timeline edits and export on the browser and device you actually use, then judge whether it covers the delivery requirements.
Use a copy of a short source clip for the first trial. Verify import, preview and export in your own browser before moving a long or deadline-sensitive edit.
Open the official early beta with a short set of clips you may edit and share.
Write down the intended duration, framing and playback checks before committing to the editor for a deliverable.
Compare the workflows, operating requirements, and source licenses of these projects.