#video

6 tips tagged #video.

• from Loya#video#design

  3×3 storyboard grid → Seedance for 2× better video output

  Before firing a 15s Seedance prompt, draft a 3×3 grid in Figma or any canvas app. Nine frames representing the 9 beats of your clip (shots 1-9, one per second-ish). Attach that grid as image_input to Seedance alongside your text prompt. Seedance follows the visual beat map way more tightly than it follows pure prose. Hit rate jumps roughly 2× on first-take quality — it's the single biggest improvement you can make to video generation without changing models.

  2026-04-24read →
• from Loya#video#content

  Caption alpha-reveal beats whole-line pop-in captions

  On short-form video, captions that pop in one full line at a time lose attention. Instead: reveal caption text ONE WORD AT A TIME, in sync with the spoken audio, using ffmpeg `drawtext` + `alpha` expression keyed to timestamps. 30 min to set up a reusable script per-project. Retention visibly jumps — viewers track the rhythm. Used across Basement Boys + Cheddy clips.

  2026-04-24read →
• from Loya#video#dev

  Deepgram word-level timestamps = frame-accurate sentence cuts

  When transcribing podcast or video audio for clipping, Deepgram Nova-3 returns WORD-LEVEL timestamps, not just sentence-level. Pull them with `&utterances=true&punctuate=true`. Each word gets start and end in ms. Makes frame-accurate sentence cuts trivial: cut at the last word's end, resume at the next sentence's first-word start. No guesswork, no breath clips hanging on front or back.

  2026-04-24read →
• from Loya#dev#video

  ffmpeg filter args with commas? escape them or die trying

  Commas are ffmpeg's filter-chain separator, so any comma INSIDE a filter arg (like drawtext text with "hello, world") silently breaks everything without a clear error. Two fixes: (1) escape inline with \, as in text=hello\,world, or (2) wrap the whole filter expression in single quotes. AI-generated ffmpeg commands fail here more than anywhere else. 3 hours of debug becomes 0.

  2026-04-24read →
• from Loya#video#dev

  Hyperframes vs Remotion — when to swap your code-to-video stack

  If you generate short-form video from code (captions, templated reels, data viz clips): Remotion is stable but React-only, and you own the runtime. Hyperframes is newer, runs inside Claude Code as a skill, and handles Three.js natively. Swap to Hyperframes when you want camera motion or real 3D elements without fighting React-Three-Fiber setup. Remotion still wins for pure HTML/CSS-only templated reels.

  2026-04-24read →
• from Loya#content#video

  Mix hook placement across your feed — tease vs payoff

  Feed algorithms (and viewers) reward rhythm. Some clips should TEASE the punchline up front ('wait for the reveal at 0:12...'). Others should put the BIG HIT at the very end, unannounced. Running one style exclusively flattens your feed. The Clip Law says every clip needs HOOK + ENTERTAINING + PAYOFF — but WHERE you place the hook relative to the payoff should vary across any 20 consecutive posts.

  2026-04-24read →