Wavel AI

Generates synthetic speech in 50+ languages with native accent options by routing audio synthesis requests through language-specific TTS models (likely leveraging APIs from providers like Google Cloud TTS, Azure Speech Services, or proprietary models). The system maps input text to language-specific phoneme sets and prosody rules, then synthesizes audio that preserves accent characteristics rather than applying a single neutral voice across all languages. Browser-based processing allows real-time preview of voiceover quality before export.

Extracts spoken dialogue from uploaded video files using cloud-based ASR (automatic speech recognition) engines, likely Google Cloud Speech-to-Text or similar, which converts audio to timestamped text transcripts. The system detects the source language automatically or accepts manual language specification, then segments transcript into sentences or phrases aligned to video timeline. This transcript serves as the source for voiceover generation and subtitle creation, enabling a single-pass workflow from video input to multilingual output.

Generates subtitle files (SRT, VTT, or embedded) from extracted transcripts with automatic timing synchronization to video frames. The system maps transcript timestamps to video playback timeline, segments text into readable chunks (typically 40-60 characters per line), and applies subtitle formatting rules (duration per subtitle, reading speed constraints). Supports multiple subtitle tracks for different languages, allowing a single video to display subtitles in the user's selected language while audio plays in another language.

Provides a web-based interface (likely React or Vue frontend) for uploading video, previewing voiceover and subtitle changes in real-time, and exporting final output without requiring desktop software installation. The system handles video playback, audio synchronization, and subtitle rendering in the browser using HTML5 video player APIs, while offloading heavy processing (TTS, ASR, encoding) to cloud backend. Users can iterate on voiceover language, voice selection, and subtitle timing through browser UI before committing to export.

Translates extracted transcript or user-provided text into target languages before feeding to voiceover synthesis. The system likely uses neural machine translation (NMT) models via APIs like Google Translate, DeepL, or proprietary models, with language pair optimization for common localization routes (English→Spanish, English→French, etc.). Translation output preserves sentence structure and timing information from source transcript, ensuring translated subtitles and voiceovers remain synchronized with video timeline. May include domain-specific terminology handling for technical or specialized content.

Implements a freemium business model where free tier users can access core voiceover and subtitle generation features with restrictions: watermark overlay on exported video, 2-minute maximum video length per export, limited voice variety (1-2 voices per language), and likely daily/monthly usage quotas. Paid tiers remove watermarks, increase video length limits (10+ minutes), expand voice options (5-10+ per language), and provide priority processing. The system enforces tier-based rate limiting and feature gating at the API level, allowing free users to experience full workflow before committing to paid subscription.

Allows users to select from multiple pre-trained voice options for each language, with likely 1-2 voices on free tier and 5-10+ on paid tiers. The system maintains a voice catalog indexed by language and gender/age characteristics, enabling users to choose voice personality (e.g., 'professional male', 'friendly female', 'narrator') that matches content tone. Voice selection is applied at the segment or full-video level, allowing consistent voice throughout or voice switching for dialogue. Backend routes selected voice to appropriate TTS model or voice cloning service during synthesis.

Accepts multiple video input formats (MP4, WebM, MOV, AVI) and handles codec detection, transcoding, and re-encoding during processing. The system likely uses FFmpeg or similar backend to normalize input videos to a standard intermediate format for processing, then re-encodes output to user-selected format. Supports common video codecs (H.264, VP9, AV1) and audio codecs (AAC, Opus, MP3), with automatic fallback to widely-compatible formats if user selects unsupported codec. Preserves video quality during processing (likely 1080p or 4K depending on tier) and maintains aspect ratio and frame rate.