The business
A recorded walkthrough often needs small, precise cuts before it is useful to someone else. Finding each spoken correction in a timeline adds work between recording the explanation and sharing it.
Internal Tool Evidence level · Delivered capability
Cutroom: edit a recording through its transcript
An internal recording and editing tool that connects spoken words to cuts, export formats and a local share-page handoff.
- Client
- DVlad — internal project
- Sector
- Video production workflow
- Role
- Workflow design, implementation and verification
- Period
- 2026 · internal development
- Services
- Video editing · Production workflow · Local tools
- Tools
- Python · FFmpeg · Local transcription · Static share pages
The real problem
Make spoken edits easy to locate, keep the media on the operator’s machine, and carry the right source file through to the export.
My responsibility
I built the local recording, transcript-editing and export workflow, with checks around source identity and explicit handoff steps.
- An internal tool, not a hosted editing service or a client account platform.
- Transcription timing can be imperfect; the editor still needs to inspect the resulting cut.
- Preparing a share-page folder does not upload or publish it.
What was built
The solution, in modules
01
Words as edit points
A local transcript connects words to timestamps. Removing a phrase defines the ranges to keep in the rendered cut.
02
Keep source identity explicit
The editor checks the source media digest before rendering. A different file with the same size and rounded duration must not silently stand in for the recording that was transcribed.
03
A deliberate export and handoff
Export presets prepare the agreed output shape. A local share-page folder can package the video, poster and captions; uploading remains a separate operator action.
System view
From explanation to a reviewable cut
- 01
Record or select the source
Keep the recording and its identity together.
- 02
Review the transcript
Use the words to find the parts that need cutting.
- 03
Render and inspect
Check source identity, create the cut and review the actual output.
- 04
Prepare the handoff
Export the agreed format or local share page. Publication is separate.
Inspectable proof
Proof you can inspect
Sanitized artifacts show the underlying work without exposing client identities, credentials, private dashboards, or customer data.
-
What the engineering check establishes
A narrow local regression check; not a production reliability certificate.
- Scenario
- Different source bytes, same size and rounded duration
- Expected behavior
- Reject before renderer invocation
- Observed result
- Replacement rejected in the synthetic regression
Evidence
What backs this up
-
Source identity regression, September 23, 2026
VerifiedA synthetic replacement with the same size and rounded duration was rejected before rendering after the editor’s digest check was repaired. This tests a specific failure path, not the creative quality of an edit.
-
Workflow implementation
Project recordThe local project includes recording, transcript edits, rendering, export presets and static share-page packaging.
-
Client outcome measurement
PendingNo time-saved, adoption or business-result claim is made for this internal tool.
Results & current state
What's true today
-
The transcript and render are tied to the same source media.
The repaired editor compares the media digest before invoking the renderer.
-
The handoff is explicit.
Preparing a static share folder does not send or upload the work.
Have footage that needs a clear edit? Describe the purpose, source material and delivery format.
Describe your setup in a few sentences. You'll get a plain answer about whether and how I can help.