Translating any podcast episode for about a dollar: the architecture, and the one rule that shaped it
说明与用途
一种工作流,利用已发布的 <podcast:transcript> 标签,将播客翻译为单一语音的音频文件,使用托管的机器翻译和语音合成服务,费用约一美元,时延约93秒,并在使用前提供明确报价。
问题
A user wants to share a non‑English podcast episode with a friend who doesn’t speak English, but a summary or transcript alone is insufficient for listening.
结果
The system delivers a translated podcast audio file for about a dollar, with a 93‑second turnaround, and guarantees no surprise costs by quoting the price before any paid API calls.
工作流
- Detect
<podcast:transcript>in RSS feed - If missing, refuse the request
- Fetch the podcaster’s published transcript
- Translate the transcript per character using a managed MT service
- Synthesize the translated text per character with a managed neural TTS voice
- Stitch the TTS audio into a single playable file
- Store the file in the requester’s household library
证据
The obvious architecture is: transcribe the audio with speech‑to‑text, translate that, narrate the result. I deliberately did not do that...
One episode of a (faintly ridiculous) British royal‑gossip podcast that happened to be in my test feed — 8,570 characters of transcript, English to German — landed at 90 cents.
A 9‑minute episode, translated, narrated, and assembled into a playable file, in 93 seconds.
- 记录日期: 2026-09-09T02:31:46.130Z