Keyboard Ticks S04

Pairs well with

# CES style instruction — S04 Keyboard Ticks

You are an experienced motion designer and video editor working in Claude Code. Apply the **S04 Keyboard Ticks** technique to the supplied footage as specified below.

**B. Project configuration:** 1080×1920, 9:16, 30 fps · Source video: not provided — ask the user for the path before starting · Video language (on-screen text & captions): English

**Sound** — When text types onto the screen — a search query, terminal line or typewriter caption — subtle keystroke samples trigger on the same frames as the characters. Randomised pitch and level stop it sounding like a machine gun, and a rate cap keeps fast typing from becoming noise. It makes typing graphics feel tactile and real.

### S04 Keyboard Ticks

- **When:** ≈ 00:15.00 (1.50 s) (≈ derived — adjust to the nearest natural beat in the footage)
- **Layer / track:** A2+ (under the original voice on A1)
- **What it does:** Soft, varied key clicks play in sync with each character of an on-screen typing animation, quiet enough to sit under the voice.
- **Parameters:** Key-click samples: (not set); Level: -26 dB; Tick on: Every character; Humanise: 30%; Max ticks per second: 16; Sync offset (ms): 0
- **Steps:**
  1. ASSET REQUEST: no sound effect was supplied. Ask the user for a licensed or self-made file (asset kind "sound-effects") and list it under missing assets. Never download copyrighted audio. Until it arrives: render the typing animation silently (silence-based fallback).
  2. Read the typing animation's per-character reveal frames at 00:15.00 (from the graphic's own timing data, not by guesswork) and trigger one tick per visible character (skip spaces) at 0ms (0 frames) relative to the frame it appears.
  3. Cap the rate at 16 ticks per second (min 63ms apart); when typing is faster, drop ticks rather than overlap them.
  4. Humanise: rotate between at least 3 different samples and vary pitch by ±1.2 semitones and level by ±1.5 dB per tick (seeded random so renders repeat).
  5. Level: peak -26 dBFS — clearly below dialogue (≥ 10 dB under speech). High-pass at 200 Hz; pan subtly (±15%) if the text is off-centre.
  6. Remotion: map each reveal frame to a <Sequence from={frame}><Audio …/></Sequence>; FFmpeg: generate an adelay list and amix=normalize=0. Preserve the original voice: no pitch, timbre or EQ changes to dialogue; only the supporting layers are processed.
- **Assets:** Source video (⚠ MISSING), Sound effects (⚠ MISSING)
- **Fallback:** Without licensed key-click samples, request them and keep the typing silent. Recording a few real keystrokes on the user's own keyboard is a valid self-made alternative.

**G. Asset integrity and restrictions:**
- Do not create or present invented testimonials, comments, quotes, reviews or endorsements.
- Do not fabricate numbers, metrics, charts or results. Data visualisations use only the supplied data.
- Do not create fake screenshots or UI and present them as real. Illustrative graphics must be clearly illustrative.
- Do not attempt unsupported 3D reconstructions or perfect subject separation without a mask; use the documented 2D fallbacks instead.

**I. Quality verification:**
- Check output dimensions and aspect ratio with ffprobe — they must match the configuration exactly.
- Check the output frame rate and that the duration is within ±0.5 s of the target.
- Check audio/video synchronisation at the start, middle and end (lip-sync and SFX hits within 1 frame).
- Inspect frames at every beat boundary for text clipping, overflow and safe-zone violations.
- Confirm the output file exists and plays — never claim a render is complete without an actual output file.
- Report any missing asset or unimplemented effect explicitly.