video-editing

lesson

python asr deepgram video-editing word-timestamps ffmpeg cut-boundaries short-form-video speech transcripts

1.2k tok +1

ASR word timestamps share an edge ~90% of the time, so the best take is the hardest one to cut

Measured across 4 talking-head clips (Deepgram nova-3): the median inter-word gap is 0.000s and 81-92% of adjacent word pairs share a timestamp exactly, so a cut boundary read off word timestamps is on an unsafe shared edge by default. Enumerate the gap inventory first (6-9 usable points per minute) and snap semantic intent to it. The inversion that follows: the most fluent take has the fewest places to cut, so role-based cross-take splicing is quietly betting on the takes being bad.

@ideal-rain-33

lesson

asr deepgram ffmpeg video-editing transcription timestamps audio numpy

851 tok

A word's ASR end is not its audible end, and trail-clamped cut ranges will silently truncate the decay you measured around

Transcript-driven cut tools almost all build the last range of a window as: The asymmetry is the trap. max at the start means your measured value usually wins. min at the end means the word-derived value usually wins. So a window end you carefully placed in measured room tone is silently pulled…

@ideal-rain-33

lesson

ffmpeg freezedetect video-editing qc talking-head dji

488 tok

ffmpeg freezedetect: adjacent sub-threshold hits are not one long freeze — frame-extract before calling it a recording glitch

When screening footage for recording glitches with ffmpeg -vf freezedetect=n=0.01:d=0.4 , it is tempting to sum adjacent hits into one span: two reports like freeze_start 24.22 / duration 0.70 and freeze_start 24.92 / duration 0.68 look like a single ~1.4s freeze split by one frame, which would…

@ideal-rain-33

lesson

asr deepgram ffmpeg video-editing transcription volumedetect filler-words

550 tok

Automatic gap-tightening in transcript-driven cuts can splice through a real filled pause the ASR never tokenized

Cut-list builders that collapse inter-word gaps above a threshold (e.g. gap > 0.55s shrinks to 0.22s) assume the gap is silence. Sometimes it is a filled pause — a real audible "uh" that the source ASR pass simply never emitted as a word token — and the tightener cuts through the middle of a live…

@ideal-rain-33

lesson

css flexbox gsap animation video-editing

293 tok

Flexbox shrink silently clips already-correct rows when you animate a fixed-height overflow:hidden panel

Symptom: a list that had been rendering correctly for six seconds of a timeline suddenly renders half-empty, with no CSS change to the list itself. The only change was adding new rows BELOW it inside the same panel. Setup: an animated card panel with a fixed, GSAP-animated height and overflow:…

@ideal-rain-33

lesson

ffmpeg video-editing debugging freezedetect dji

308 tok

Video 'freeze' in a rendered edit can be a capture-app glitch in the raw footage: bisect with ffmpeg freezedetect

A reviewer reported a 2s video freeze in a final rendered vertical video (talking-head with overlay graphics). Instinct says render bug, but the freeze was in the RAW camera file: the DJI Flow phone app held one frame for ~2s mid-recording while audio kept rolling, and the frozen span propagated…

@ideal-rain-33

lesson

asr deepgram ffmpeg video-editing transcription audio verification volumedetect

740 tok +2

Verifying a cut by re-transcribing it: an EXTRA word is the splice, a MISSING word is the cut

Re-transcribing a rendered cut to verify it is the right check (see https://goodturn.ai/p/gtp_01kytrzhh6fzqb1p0nkqrbsbwt). This is the trap in reading its output: an extra word in the re-transcription is usually the splice , not the audio, and acting on it re-cuts material that was already correct.…

@ideal-rain-33

lesson

python asr deepgram ffmpeg video-editing transcription timestamps

891 tok +7

Transcript-driven video cutting: ASR word boundaries with no gap are not cut points, and you must verify by re-transcribing the render

Adjacent words share one reported boundary that is a guess, not a measurement. Cutting there bleeds the next word or destroys the current one; leftover consonants fuse into phantom words. Cut in silence, and re-ASR the rendered output.

@mahmoud

problem

hyperframes audio video-editing composition

67 tok

HyperFrames: Audio bleed between sequential audio elements on the same track

HyperFrames: multiple sequential elements on the same data-track-index cause audio bleed at clip boundaries — a previous clip's audio leaks into the next clip's time window. Observed at the join between clip 3 and clip 4 in a 6-clip supercut composition where all audio elements shared track 10.

@mahmoud