Subtle Foley Accents S07

Pairs well with

# CES style instruction — S07 Subtle Foley Accents

You are an experienced motion designer and video editor working in Claude Code. Apply the **S07 Subtle Foley Accents** 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** — Restrained foley — a soft tap when a button is pressed, a paper slide when a card moves, a gentle click on a toggle — is matched to visible interactions in UI animations or object movement. Kept far below the voice and slightly varied, it makes graphics feel physical without ever drawing attention to itself.

### S07 Subtle Foley Accents

- **When:** ≈ 00:15.00 (2.00 s) (≈ derived — adjust to the nearest natural beat in the footage)
- **Layer / track:** A2+ (under the original voice on A1)
- **What it does:** Quiet taps, clicks and soft slides play on the frames where on-screen buttons are pressed or objects move, adding tactile realism.
- **Parameters:** Foley sample set: (not set); Level: -28 dB; Accent: Both; Sync offset (ms): -10; Variation: 25%; Pan to on-screen position: on
- **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: keep interactions silent (silence-based fallback); never imitate a specific product's signature UI sounds.
  2. List the visible interaction events at 00:15.00 — button taps, toggles, card slides and object landings — with the exact contact frame for each (from animation keyframes or by stepping through the footage).
  3. Place one accent per event at -10ms (0 frames) relative to the contact frame; taps/clicks are 30–80ms long, slides follow the movement duration with a 40ms fade in/out.
  4. Level: peak -28 dBFS, at least 12 dB under dialogue; high-pass at 150 Hz. Vary pitch ±1.0 semitones and alternate samples so repeats never sound identical.
  5. Pan each accent to the horizontal position of its on-screen event (left edge = −40%, right edge = +40%); keep it mono-compatible.
  6. Skip accents that would land within 120ms of a stressed word, and never stack more than 3 per second. 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) · optional: Screen recording
- **Fallback:** Without licensed foley, request a small sample set or record simple taps/slides locally (self-made is fine). Otherwise leave the interactions silent.

**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.