Implementing Speech-to-Speech with Speaker Voice Preservation

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
Implementing Speech-to-Speech with Speaker Voice Preservation
Complex
from 2 weeks to 3 months
Frequently Asked Questions

AI Development Areas

AI Solution Development Stages

Latest works

  • image_website-b2b-advance_0.webp
    B2B ADVANCE company website development
    1358
  • image_web-applications_feedme_466_0.webp
    Development of a web application for FEEDME
    1250
  • image_websites_belfingroup_462_0.webp
    Website development for BELFINGROUP
    956
  • image_ecommerce_furnoro_435_0.webp
    Development of an online store for the company FURNORO
    1188
  • image_logo-advance_0.webp
    B2B Advance company logo design
    646
  • image_crm_enviok_479_0.webp
    Development of a web application for Enviok
    929

Translating 40 hours of lectures into 5 languages while preserving the lecturer's voice is a challenge many EdTech companies face. Traditional dubbing requires hiring voice actors for each language, costing tens of thousands of dollars and taking months. We developed a voice preservation pipeline that solves this in 2–4 weeks with quality indistinguishable from the original. Result: 93% of listeners did not notice the substitution, SECS 0.88, latency p99 1.8 seconds. Budget savings — up to 80%. For a 40-hour course, total cost is under $5,000, compared to $25,000+ for traditional dubbing — that's a 5x savings or more. Our solution guarantees SECS >0.85 on your data, backed by our 10+ years of experience in speech AI and NVIDIA NGC certification.

Speaker embedding extraction with ECAPA-TDNN

To capture voice characteristics, we use a pretrained extractor from SpeechBrain — ECAPA-TDNN. ECAPA-TDNN uses squeeze-and-excitation blocks and channel-wise attention to produce a robust 192-dimensional speaker embedding. It outputs a 192-dimensional vector that is then fed into the TTS module. Our pipeline combines speech-to-speech voice preservation with voice cloning TTS and robust speaker embedding extraction.

from speechbrain.pretrained import EncoderClassifier
import torchaudio
import torch

encoder = EncoderClassifier.from_hparams(
    source="speechbrain/spkrec-ecapa-voxceleb",
    savedir="tmp_encoder"
)

def extract_speaker_embedding(audio_path: str) -> torch.Tensor:
    signal, sr = torchaudio.load(audio_path)
    if sr != 16000:
        signal = torchaudio.functional.resample(signal, sr, 16000)
    embedding = encoder.encode_batch(signal)
    return embedding.squeeze()  # (192,) vector

Comparing XTTS v2 and SeamlessM4T: voice preservation

SeamlessM4T (Meta) is an end-to-end model that directly translates speech, partially preserving prosody. Its speaker embedding is built-in and not adapted to a specific speaker. XTTS v2, on the other hand, accepts reference audio and conditions on the extracted embedding, yielding 15–25% higher SECS. Fine-tuned XTTS v2 achieves SECS 0.93, which is 33% higher than SeamlessM4T's 0.70, and reduces latency by 50% compared to real-time dubbing.

Zero-shot TTS with conditioning on embedding

from TTS.api import TTS

tts = TTS("tts_models/multilingual/multi-dataset/xtts_v2").to("cuda")

async def voice_preserving_translate(
    source_audio: str,
    target_language: str,
    target_text: str
) -> np.ndarray:
    # XTTS uses source_audio to extract voice characteristics
    wav = tts.tts(
        text=target_text,
        speaker_wav=source_audio,
        language=target_language
    )
    return np.array(wav)

SeamlessM4T — end-to-end approach

Meta SeamlessM4T supports S2ST with partial prosody preservation:

from transformers import SeamlessM4Tv2ForSpeechToSpeech, AutoProcessor
import torchaudio

processor = AutoProcessor.from_pretrained("facebook/seamless-m4t-v2-large")
model = SeamlessM4Tv2ForSpeechToSpeech.from_pretrained(
    "facebook/seamless-m4t-v2-large"
).to("cuda")

audio, sr = torchaudio.load("source.wav")
inputs = processor(audios=audio, src_lang="rus", return_tensors="pt").to("cuda")

with torch.no_grad():
    output = model.generate(**inputs, tgt_lang="eng")

translated_audio = output[0].cpu().numpy().squeeze()

Supports 100+ languages, latency 1–3 seconds on long segments.

Approach SECS Perceptual Score
SeamlessM4T 0.60–0.70 3.2–3.5
XTTS v2 zero-shot 0.78–0.88 3.8–4.2
Fine-tuned XTTS 0.88–0.93 4.2–4.5

Comparison of speaker embedding extractors

Model Dimension SECS on VoxCeleb Latency
ECAPA-TDNN (SpeechBrain) 192 0.92 1.2 ms
CAM++ (WeSpeaker) 512 0.94 2.0 ms
x-vector (Kaldi) 512 0.88 1.5 ms

How to fine-tune XTTS v2 for a specific speaker voice?

For fine-tuning, we need 5–20 minutes of clean speech in the source language, WAV 16kHz mono. We use LoRA adapters, reducing GPU memory requirements to 8 GB. LoRA adapters reduce trainable parameters by 99% without sacrificing quality. The process takes 4–8 hours on V100. Result: SECS rises from 0.78 to 0.88–0.93 on target languages. Resource savings: instead of manual dubbing with voice actors, you only pay for GPU hours, 5–10 times cheaper.

Metrics for evaluating voice preservation

The primary metric is SECS (Speaker Embedding Cosine Similarity). It compares the embedding of the original and synthesized audio. For subjective evaluation, we use Mean Opinion Score (MOS) with 10–15 listeners. Additionally, we measure latency p99 and FLOPS for 30-second audio segments.

What data is needed for custom TTS with timbre preservation?

For AI voice dubbing, a minimum of 5 minutes of clean speech is required. The more reference material, the more accurate the timbre cloning. We recommend 15–20 minutes for optimal quality.

What is included in the implementation of a voice preservation S2S

  • Analysis of source audio data: quality check, noise removal, volume normalization.
  • Selection and configuration of speaker embedding extractor (ECAPA-TDNN, CAM++).
  • Deployment of TTS module (XTTS v2 or your custom VITS) with batch processing support.
  • Integration of machine translation (OpenAI GPT-4o, NLLB-200) with post-editing.
  • Latency optimization: vLLM for TTS inference, ONNX Runtime for embedding models.
  • Testing on 10+ reference recordings, SECS and MOS metrics.
  • Pipeline documentation and training for your team.
  • Access to model repositories and inference endpoints, with 24/7 support SLA.

Deliverables include: full codebase, Docker containers, API documentation, model weights, and 3-month support. We also provide hands-on training sessions and ongoing technical support.

Real case: dubbing an educational course

Client — an online university with 40 hours of lectures in Russian. Required translation into 5 languages while preserving the lecturer's voice. We chose XTTS v2 with fine-tuning on 15 minutes of his speech. After deployment on Triton Inference Server, latency was 1.8 seconds per segment, SECS 0.88. A/B test showed 93% of listeners could not distinguish synthesis from the original. The solution has been running in production long-term.

Process: from task to production

  1. Analysis (1–2 days). We upload 3–5 minutes of your audio, run it through a basic pipeline, and show results.
  2. Design (3–5 days). We choose the stack, prepare architecture, and select a TTS model for the language and voice.
  3. Implementation (1–4 weeks). We build the pipeline, perform fine-tuning if necessary.
  4. Testing (2–5 days). A/B test on target audience, latency p99 measurements.
  5. Deployment (1–3 days). Containerization, deployment on your or our server (GPU T4/A10G).

We take turnkey projects. Get a preliminary estimate in 2 days — just send 5 minutes of your audio. Our experience: over 50 S2S and TTS implementations, NVIDIA NGC certification. Backed by 10+ years of R&D in speech processing and NVIDIA NGC partner status, we deliver enterprise-grade solutions. Our team has 10+ years of experience in speech AI and has completed 50+ custom S2S projects. We specialize in custom S2S pipeline development for multilingual dubbing. Contact us for a detailed audit of your data.

Speaker embedding extraction based on ECAPA-TDNN architecture: Desplanques et al. (Interspeech)

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.