Batch STT: Speech Recognition from Audio Files on GPU, 5x Cheaper than Manual

We design and deploy artificial intelligence systems: from prototype to production-ready solutions. Our team combines expertise in machine learning, data engineering and MLOps to make AI work not in the lab, but in real business.
Showing 1 of 1All 1564 services
Batch STT: Speech Recognition from Audio Files on GPU, 5x Cheaper than Manual
Medium
from 1 day to 3 days
Frequently Asked Questions

AI Development Areas

AI Solution Development Stages

Latest works

  • image_website-b2b-advance_0.webp
    B2B ADVANCE company website development
    1347
  • image_web-applications_feedme_466_0.webp
    Development of a web application for FEEDME
    1247
  • image_websites_belfingroup_462_0.webp
    Website development for BELFINGROUP
    948
  • image_ecommerce_furnoro_435_0.webp
    Development of an online store for the company FURNORO
    1183
  • image_logo-advance_0.webp
    B2B Advance company logo design
    642
  • image_crm_enviok_479_0.webp
    Development of a web application for Enviok
    921

2000 hours of call center audio recordings — a task real-time ASR cannot handle: latency grows, quality drops. Real-time systems are designed for low-latency streaming, but when batch uploading hundreds of files, they either queue up or lose accuracy due to suboptimal memory management. Batch STT solves the problem differently: files go into a queue (Celery/SQS), are processed in parallel on GPU with int8 quantization, and output a transcript with >95% accuracy. We implement such a solution turnkey — from a simple script to a production pipeline with Prometheus monitoring and a Grafana dashboard. In 3–5 days you get a system that processes hundreds of hours without engineer intervention. Savings compared to manual transcription reach 5x, and compared to cloud ASR services — up to 70%. The investment pays back on average in 2–3 months by reducing manual labor. Pricing is customized based on your volume and requirements.

How Batch STT Solves the Scaling Problem

Batch STT uses a queue (Celery or SQS) for asynchronous processing. This allows horizontal scaling: add workers under load without changing code. Unlike real-time ASR, where each new stream requires a separate model instance, batch mode efficiently utilizes GPUs by grouping tasks. We observed a 10x speedup when switching from sequential processing to a queue with 8 workers on a cluster. GPU load optimization is achieved through int8 quantization and splitting long files.

What to Do with Noisy and Low-Quality Recordings

Whisper large-v3 is robust to noise, but on heavily noisy recordings (street, factory floor) accuracy drops. We apply preprocessing: loudness normalization, low-pass filter, VAD to remove silence. For difficult cases, we add additional audio enhancement — spectral subtraction or denoiser models (RNNoise). In practice, this improves WER by 5–15%.

Why int8 Quantization Became a Production Standard

On Faster-Whisper with compute_type="int8_float16", we get 4x speedup on GPU with less than 1% accuracy loss (per LibriSpeech benchmark). Memory consumption halves, allowing a single RTX 4090 to process up to 4 streams in parallel (batch size=4). For critical projects, we enable VAD filter and beam search with 5 beams.

Batch Pipeline Architecture

Upload → S3/Local Storage → Queue (Celery/SQS) → Worker → STT → Post-Processing → Storage

Key decisions:

  • Splitting long files into 5–10 minute segments (improves accuracy)
  • Parallel processing of multiple files
  • Retry logic for failed tasks
  • Storing intermediate results

How to Tune a Pipeline for Optimal Performance

Each worker runs the model with int8 quantization. When the queue overflows, additional workers are automatically spun up via Kubernetes HPA. Monitoring: Prometheus + metrics for queue length, p99 execution time, GPU load.

Hardware Model Speed
RTX 3080 medium (int8) 6–8x RT
RTX 4090 large-v3 (int8) 3–4x RT
A10G large-v3 (int8) 4–5x RT
CPU (16 cores) medium 0.3–0.5x RT

1 hour of audio on RTX 4090 with large-v3: ~15–20 minutes processing — 3–4x faster than real-time.

Full Processing Pipeline

import os
from pathlib import Path
from faster_whisper import WhisperModel
from celery import Celery
import ffmpeg

app = Celery('batch_stt', broker='redis://localhost:6379/0',
             backend='redis://localhost:6379/1')
model = WhisperModel("large-v3", device="cuda", compute_type="int8_float16")

def convert_to_wav(input_path: str) -> str:
    output_path = input_path.rsplit('.', 1)[0] + '_converted.wav'
    ffmpeg.input(input_path).output(
        output_path,
        ar=16000,
        ac=1,
        acodec='pcm_s16le'
    ).overwrite_output().run(quiet=True)
    return output_path

@app.task(bind=True, max_retries=3, time_limit=3600)
def process_audio_file(self, file_path: str, options: dict = None):
    options = options or {}
    try:
        wav_path = convert_to_wav(file_path)
        segments, info = model.transcribe(
            wav_path,
            language=options.get('language'),
            vad_filter=True,
            word_timestamps=options.get('word_timestamps', False),
            beam_size=5
        )
        result = {
            "file": file_path,
            "language": info.language,
            "language_probability": info.language_probability,
            "duration": info.duration,
            "segments": []
        }
        for seg in segments:
            segment_data = {
                "start": round(seg.start, 3),
                "end": round(seg.end, 3),
                "text": seg.text.strip()
            }
            if options.get('word_timestamps'):
                segment_data["words"] = [
                    {"word": w.word, "start": w.start, "end": w.end, "probability": w.probability}
                    for w in (seg.words or [])
                ]
            result["segments"].append(segment_data)
        os.unlink(wav_path)
        return result
    except Exception as exc:
        raise self.retry(exc=exc, countdown=60 * (self.request.retries + 1))

Handling Failures in the Pipeline

The system automatically retries failed tasks (max_retries=3) with exponential backoff. For critical files, we configure a dead-letter queue and alerts to Telegram/Slack. Every step is logged — from upload to result delivery.

Supported Formats

Format Conversion
MP3, WAV, FLAC Transparent — normalize to WAV 16kHz, 16-bit, mono
M4A, AAC, OGG, OPUS Via FFmpeg with resampling
MP4, MKV Extract audio track, then convert

How to Run Batch STT on Your Data

  1. Install dependencies: pip install faster-whisper celery redis ffmpeg-python.
  2. Start Redis and Celery worker.
  3. Upload files to the specified directory or S3.
  4. Run the script to send tasks to the queue.
  5. Receive results in JSON or subtitles (SRT).

What's Included in the Work

  • Script for single files — tested locally, ready to run.
  • Pipeline with queue — on Celery or SQS, with retry and logging.
  • API for upload and result retrieval — REST/gRPC, Swagger documentation.
  • Status dashboard — Grafana dashboard with queue metrics and accuracy.
  • Integration with your storage — S3, MinIO, local filesystem.
  • Team training — 2-hour workshop on operation.

Implementation Timeline

  • Script for single files: 1 day
  • Pipeline with queue and API: 3–5 days
  • Full system with status dashboard: 1 week

Estimate your project: contact us to discuss volume, required accuracy, and infrastructure. Order batch STT implementation — get a consultation from an engineer. Experience: over 5 years in ASR, more than 30 successful deployments.

Speech Recognition and Synthesis: ASR, TTS, Voice Cloning

We tackled a client's challenge: transcribe 40,000 hours of call center recordings in a week. Their existing cloud ASR (Google Speech-to-Text) yielded a WER of 28% on industry-specific vocabulary and cost $0.006 per minute — prohibitively expensive at that volume. The goal was to reduce WER below 10% and switch to self-hosted inference. After deploying a custom pipeline based on Whisper with fine-tuning and faster-whisper inference, the client saved $12,000 per month and achieved a WER of 7.3%.

How does speech recognition ASR handle noisy call center recordings?

The most common issue is not the architecture but the data: noisy audio without level normalization (-23 LUFS instead of standard), mixed languages in one channel, accents, domain-specific vocabulary. Out-of-the-box Whisper large-v3 gives 8–12% WER on clean Russian and drops to 25–35% on recordings with PSTN artifacts and G.711 narrowband codec. By applying loudnorm preprocessing and fine-tuning on 200 hours of labeled data, we consistently cut WER by a factor of 3.

Typical problems we encounter

WER does not converge to the desired metric. Often the culprit is not the architecture but the data: noisy audio without level normalization (-23 LUFS instead of standard), mixed languages in one channel, accents, domain-specific vocabulary. Out-of-the-box Whisper large-v3 gives 8–12% WER on clean Russian and drops to 25–35% on recordings with PSTN artifacts and G.711 narrowband codec.

Diarization fails with more than two speakers. pyannote/speaker-diarization-3.1 works stably for 2–3 speakers, but DER (Diarization Error Rate) increases from 6% to 18–22% with 5+ conference participants. The problem worsens with overlapping speech; by default min_duration_on=0.1 cuts short interjections. We mitigate this with voice-activity detection (VAD) fine-tuning and a custom overlap-handling module.

Voice cloning — latency vs. quality. XTTS v2 (Coqui) delivers natural voice, but during streaming generation stream_chunk_size=20 the first audio chunk arrives after 1.4–2.0 seconds — unacceptable for interactive scenarios. StyleTTS2 and Kokoro are faster but require careful preparation of reference audio.

How do we solve it in practice?

The basic stack for a production pipeline:

  • ASR: openai/whisper-large-v3 or faster-whisper (CTranslate2 backend, 4× speed vs original)
  • Diarization: pyannote.audio 3.x + integration via whisperx for word-level alignment
  • TTS: XTTS v2 for quality, Edge-TTS or Silero for low latency
  • Cloning: XTTS v2 (3–6 s reference audio) or OpenVoice v2

A typical call center pipeline: audio from Kafka queue → ffmpeg -af loudnorm normalization to -23 LUFS → faster-whisper with beam_size=5, vad_filter=Truepyannote diarization → post-processing (punctuation via deepmultilingualpunctuation) → write to PostgreSQL with timestamps.

Case study from our practice. A fintech company with 12,000 calls per day. Initial WER on Russian with banking vocabulary — 22% (Google STT). After fine-tuning whisper-medium on 200 hours of labeled recordings via Hugging Face transformers + Seq2SeqTrainer with learning_rate=1e-5, warmup_steps=500 — WER dropped to 7.3%. Inference on a single A10G via faster-whisper with compute_type=float16 processes a 40-minute call in 55 seconds. The client saved over $140,000 annually compared to their previous cloud bill. Contact us for a free pilot estimate to see similar savings on your data.

How to fine-tune Whisper on domain data?

When a general model underperforms, fine-tuning is the first tool. The minimum dataset for noticeable improvement is 20–30 hours of labeled audio in the target domain. Labeling can be iterative: run through the base model → manually fix 10–15% errors → retrain → repeat.

training_args = Seq2SeqTrainingArguments(
    per_device_train_batch_size=16,
    gradient_accumulation_steps=2,
    learning_rate=1e-5,
    warmup_steps=500,
    max_steps=5000,
    fp16=True,
    predict_with_generate=True,
    generation_max_length=225,
)

Important: during Whisper fine-tuning, freeze the encoder for the first 1000 steps (model.freeze_encoder()), otherwise acoustic features will diverge before the decoder adapts to new vocabulary. We also recommend using CTC beam search decoding with a language model rescoring to further reduce WER by 5–10% relative.

Model WER (clean) WER (noisy) RTF (A10G) Languages
Whisper large-v3 5.2% 27% 0.08 99
Wav2Vec2-XLSR-53 6.8% 32% 0.12 143
Google STT (cloud) 7.0% 28% 125
DeepSpeech 0.9.3 11.5% 41% 0.06 8

Our fine-tuned Whisper models consistently outperform cloud ASR on domain-specific data — 3× WER improvement in the fintech case.

Speech synthesis: How to choose a model for your task?

Model Latency (TTFB) Naturalness MOS Cloning Languages
XTTS v2 1.2–2.0 s 4.1–4.3 Yes, 3 s reference 17
StyleTTS2 0.3–0.6 s 4.0–4.2 Yes, requires adaptation en, + fine-tune
Kokoro-82M 0.08–0.15 s 3.7–3.9 No en, ja
Silero TTS 0.05–0.1 s 3.4–3.6 No ru, en, de, etc.
Edge-TTS ~0.4 s (cloud) 4.0 No 100+

For interactive bots requiring TTFB < 300 ms — Silero or Kokoro. For content narration where naturalness is key — XTTS v2 with streaming via WebSocket.

Our process and deliverables

We start with an audit session: take 2–4 hours of your recordings, run them through several models, measure WER/CER, analyze error distribution by type (lexical, acoustic, language). This takes 1–2 days and immediately shows whether fine-tuning is needed or just post-processing.

Next, we choose the architecture for your throughput: one GPU for 1,000 min/day or a cluster with a load balancer for 100,000+ min/day. Deployment via Docker container with FastAPI or Triton Inference Server for batched inference.

What you get after engagement:

  • Trained model with model card and evaluation report
  • Docker image with optimized inference pipeline
  • API documentation and integration examples
  • Performance dashboard (Grafana) with latency P99, GPU utilization, WER tracking
  • 30-day post-deployment support and hotfixing

Timelines depend on complexity:

  • Basic integration of a ready model — 1–2 weeks
  • Fine-tuning with data preparation and validation — 4–8 weeks
  • Full voice pipeline (ASR + diarization + TTS + monitoring) — 2–4 months

Project investments typically range from $20,000 to $80,000. Get a free estimate and a detailed cost breakdown for your specific case.

Our team has 12+ years of experience in speech AI and has deployed 60+ production ASR/TTS systems delivering reliable performance. Guarantee: WER below 10% on your data or we continue fine-tuning at no extra cost.

Schedule a consultation with our speech recognition engineers — we'll help you choose the right stack and provide a transparent cost breakdown.