Agent skill

TTS Audio Mastering

Practical mastering steps for TTS audio: cleanup, loudness normalization, alignment, and delivery specs.

Stars 897
Forks 232

Install this agent skill to your Project

npx add-skill https://github.com/benchflow-ai/skillsbench/tree/main/tasks-no-skills/multilingual-video-dubbing/environment/skills/text-to-speech

SKILL.md

SKILL: TTS Audio Mastering

This skill focuses on producing clean, consistent, and delivery-ready TTS audio for video tasks. It covers speech cleanup, loudness normalization, segment boundaries, and export specs.

1. TTS Engine & Output Basics

Choose a TTS engine based on deployment constraints and quality needs:

  • Neural offline (e.g., Kokoro): stable, high quality, no network dependency.
  • Cloud TTS (e.g., Edge-TTS / OpenAI TTS): convenient, higher naturalness but network-dependent.
  • Formant TTS (e.g., espeak-ng): for prototyping only; often less natural.

Key rule: Always confirm the native sample rate of the generated audio before resampling for video delivery.


2. Speech Cleanup (Per Segment)

Apply lightweight processing to avoid common artifacts:

  • Rumble/DC removal: high-pass filter around 20 Hz
  • Harshness control: optional low-pass around 16 kHz (helps remove digital fizz)
  • Click/pop prevention: short fades at boundaries (e.g., 50 ms fade-in and fade-out)

Recommended FFmpeg pattern (example):

  • Add filters in a single chain, and keep them consistent across segments.

3. Loudness Normalization

Target loudness depends on the benchmark/task spec. A common target is ITU-R BS.1770 loudness measurement:

  • Integrated loudness: -23 LUFS
  • True peak: around -1.5 dBTP
  • LRA: around 11 (optional)

Recommended workflow:

  1. Measure loudness using FFmpeg ebur128 (or equivalent meter).
  2. Apply normalization (e.g., loudnorm) as the final step after cleanup and timing edits.
  3. If you adjust tempo/duration after normalization, re-normalize again.

4. Timing & Segment Boundary Handling

When stitching segment-level TTS into a full track:

  • Match each segment to its target window as closely as possible.
  • If a segment is shorter than its window, pad with silence.
  • If a segment is longer, use gentle duration control (small speed change) or truncate carefully.
  • Always apply boundary fades after padding/trimming to avoid clicks.

Sync guideline: keep end-to-end drift small (e.g., <= 0.2s) unless the task states otherwise.

Expand your agent's capabilities with these related and highly-rated skills.

benchflow-ai/skillsbench

csv-processing

Use this skill when reading sensor data from CSV files, writing simulation results to CSV, processing time-series data with pandas, or handling missing values in datasets.

897 232
Explore
benchflow-ai/skillsbench

pid-controller

Use this skill when implementing PID control loops for adaptive cruise control, vehicle speed regulation, throttle/brake management, or any feedback control system requiring proportional-integral-derivative control.

897 232
Explore
benchflow-ai/skillsbench

yaml-config

Use this skill when reading or writing YAML configuration files, loading vehicle parameters, or handling config file parsing with proper error handling.

897 232
Explore
benchflow-ai/skillsbench

simulation-metrics

Use this skill when calculating control system performance metrics such as rise time, overshoot percentage, steady-state error, or settling time for evaluating simulation results.

897 232
Explore
benchflow-ai/skillsbench

vehicle-dynamics

Use this skill when simulating vehicle motion, calculating safe following distances, time-to-collision, speed/position updates, or implementing vehicle state machines for cruise control modes.

897 232
Explore
benchflow-ai/skillsbench

web-interface-guidelines

Vercel's comprehensive UI guidelines for building accessible, performant web interfaces. Use this skill when reviewing or building UI components for compliance with best practices around accessibility, performance, animations, and visual stability.

897 232
Explore

Didn't find tool you were looking for?

Be as detailed as possible for better results