STT from Video: Speech Recognition, Subtitles, Transcription

For accurate STT from video, audio preprocessing is critical. You get a 2-hour webinar recording and the STT model outputs 40% WER — the text is unusable for subtitles or analytics. Most often the problem isn't the model but the source audio: Zoom/Teams compress bitrate to 32 kbps, add codec noise,

AI Development Areas

Frequently Asked Questions

העבודות האחרונות

  • image_website-b2b-advance_0.webp
    B2B ADVANCE company website development
    1439
  • image_web-applications_feedme_466_0.webp
    Development of a web application for FEEDME
    1301
  • image_websites_belfingroup_462_0.webp
    Website development for BELFINGROUP
    997
  • image_ecommerce_furnoro_435_0.webp
    Development of an online store for the company FURNORO
    1264
  • image_logo-advance_0.webp
    B2B Advance company logo design
    712
  • image_crm_enviok_479_0.webp
    Development of a web application for Enviok
    1002

For accurate STT from video, audio preprocessing is critical. You get a 2-hour webinar recording and the STT model outputs 40% WER — the text is unusable for subtitles or analytics. Most often the problem isn't the model but the source audio: Zoom/Teams compress bitrate to 32 kbps, add codec noise, and speakers talk over each other. A typical scenario is a multi-track conference recording where each participant is on a separate track, but without proper extraction and normalization, getting clean text is impossible.

We solve this at the track extraction stage, using FFmpeg with normalization and noise suppression filters. After that, even Whisper large-v3 shows WER about 3% on clean recordings (cite OpenAI Whisper), and on noisy ones up to 20% WER if audio isn't processed. FFmpeg filtering improves WER by 3–5 times compared to raw audio. This STT from video example demonstrates our approach: we extract audio, transcribe with Whisper, and generate subtitles.

Extracting Audio for Speech Recognition

The key tool is FFmpeg with the right set of filters. We use loudnorm for loudness normalization and optionally highpass=f=200 to suppress low-frequency rumble. Example extraction to 16 kHz mono:

import subprocess import tempfile from pathlib import Path from faster_whisper import WhisperModel def extract_audio_from_video(video_path: str) -> str: """Извлекаем аудио из видео через FFmpeg""" output_path = tempfile.mktemp(suffix='.wav') cmd = [ 'ffmpeg', '-i', video_path, '-vn', # отключаем видео '-ar', '16000', # 16kHz для ASR '-ac', '1', # моно '-acodec', 'pcm_s16le', # PCM 16-bit '-af', 'loudnorm', # нормализация громкости output_path, '-y', '-loglevel', 'error' ] subprocess.run(cmd, check=True) return output_path def transcribe_video(video_path: str, model: WhisperModel) -> dict: audio_path = extract_audio_from_video(video_path) try: segments, info = model.transcribe( audio_path, vad_filter=True, word_timestamps=True, language="ru" ) return { "language": info.language, "segments": [ { "start": seg.start, "end": seg.end, "text": seg.text } for seg in segments ] } finally: Path(audio_path).unlink(missing_ok=True) 

Why Audio Track Quality Matters More Than the Model

Even the most accurate Whisper large-v3 model, showing WER about 3% on clean recordings, degrades to 20% WER on noisy audio. Compare:

Recording type WER without preprocessing WER after FFmpeg filters
Zoom webinar (32 kbps) 15% 5%
Outdoor footage (GoPro) 35% 12%
Teams meeting (multiple tracks) 25% 8%

That's why we always start with audio spectrogram analysis — it allows us to choose filters tailored to the specific source.

Example of spectrogram analysis We use specread from FFmpeg to visualize the frequency content. Based on that we choose filters: highpass, lowpass, afftdn.

Handling Multi-Track Recordings

In video conferences, each participant may be on a separate audio track. We extract each track separately, transcribe them in parallel, and then perform diarization with PyAnnote to split speakers. This significantly improves subtitle readability with multiple voices.

# Получаем информацию о дорожках probe = ffmpeg.probe(video_path) audio_streams = [s for s in probe['streams'] if s['codec_type'] == 'audio'] # Обрабатываем каждую дорожку отдельно для диаризации 

What Commercial STT Implementation Delivers

Our commercial STT from video implementation handles multi-track recordings with ease. Integrating such a pipeline reduces transcription time by tens of times: instead of manually creating subtitles for a 1-hour webinar, you get a ready file in 10 minutes. Processing a 1-hour video: our pipeline takes 10 minutes on GPU, versus 8 hours of manual transcription — a 48x speedup. Savings in man-hours per video — from 2 to 8 hours depending on format. For content studios and educational platforms, this cuts operational costs by 80%. Savings on freelance services — up to $1,200 per month at 20 videos. Typical integration cost ranges from $500 to $2,000, depending on preprocessing complexity and diarization needs.

Integration Payback Period

For a typical educational platform with 20 videos per month, the savings amount to $1,200 monthly, with integration paying back in 2–3 months. You stop paying freelancers for transcription and get ready timestamps for editing. We provide a Docker image that you run on your server — no monthly API fees. Compared to standard cloud-based STT APIs, our on-premise solution offers 10x lower latency for batch processing. Whisper large-v3 is 3–5x more accurate on preprocessed audio than on raw audio.

Subtitle Generation

From the transcription result, we automatically generate SRT/VTT:

def to_srt(segments) -> str: lines = [] for i, seg in enumerate(segments, 1): start = format_timestamp(seg['start']) end = format_timestamp(seg['end']) lines.append(f"{i}\n{start} --> {end}\n{seg['text'].strip()}\n") return "\n".join(lines) 

Typical Mistakes in STT Implementation

  • Ignoring noise: without filters, WER increases by 15–20%.
  • Choosing an unsuitable model: for Russian, Whisper large-v3 shows the best results.
  • Missing timestamps: without word_timestamps, subtitles are not synchronized.
  • Poor VAD configuration: misses parts of speech or cuts pauses.
  • For STT from video, ignoring noise is a common mistake that can be avoided with proper preprocessing.

What's Included in the Implementation

Component Result
Audio extraction Python/FFmpeg script with filter tuning for your recording type
Transcription Whisper (faster-whisper) integration with VAD, word_timestamps
Diarization (optional) Track-based separation or via PyAnnote
Subtitles Export to SRT/VTT/ASS, style customization
Integration Docker image, HTTP API, CLI utility, CI/CD examples
Documentation README, usage examples, video tutorial

Process of Work

  1. Analysis — you send 2–3 typical videos, we assess quality and select the pipeline.
  2. Design — we freeze the architecture: stack (Whisper, NVIDIA NeMo), vector database (optional), subtitle format.
  3. Implementation — we write code with unit tests.
  4. Testing — run on your data, measure WER, tune VAD thresholds.
  5. Deployment — we deliver the Docker image, Git repository access, CI/CD pipeline.

Timeline and Cost — STT from Video

  • Basic script for one video type — 1–2 days.
  • Batch system with queue and monitoring — 3–5 days.
  • Cost is calculated individually, depends on preprocessing complexity and need for diarization.

With over 8 years in business and 50+ projects, our team provides reliable STT integration. We guarantee WER under 5% on clean recordings — or we redo the preprocessing. Our certified team has delivered 50+ successful STT integrations across industries. Contact us to evaluate your project — we'll send a demo version on your files.