Repository navigation
Multi-language support #55
Description
Hi, I had an idea yesterday about combining playwright with a voice synthesizer to record the same script in multiple languages, I started the implementation and after having a working POC, I thought, "what if someone already had the same idea and implemented it already", funny enough, I found this project and it seems it already does what I was looking for.
The main difference with this project vs my POC as far as I can tell, is the multi-language perspective. Would you be open to add this functionality to the project? If this is something that could be interesting for the project, I think I could contribute it with some guidance.
Thanks in advance 🙏
Activity
shreyaskarnik commentedon Oct 27, 2026
Thanks for opening this, and for #58! Yes, I'd welcome multi-language support, and I'm happy to help guide it.
Some context on what already exists, so you can reuse it:
langis already in the clip cache key (src/tts/cache.ts) and is used as the Whisper language hint.video.contextOptions.localealready reaches Playwright, so the recorded app can switch language.export.variants(src/pipeline.ts, the "Viewport-native variants" loop) already does TTS → re-record → export under another name, with each run in its own.argo/<demo>-<name>/folder. Multi-language fits most naturally as a sibling of that loop.One constraint that shapes the design: a translation needs its own recording, not just new audio. Translated narration often runs 15–25% longer, and
narration.durationFor()sets the script's waits from clip length, so laying French audio over the English recording would drift.A rough shape I'd suggest (open to your POC's approach):
demos/<demo>.scenes.<lang>.jsonsidecars with the same scene names, translatedtextand overlay copy.argo validatechecks that scene names match the base manifest.locales: [{ code: 'fr', voice?, engine?, contextOptions?: { locale: 'fr-FR' } }]list, with per-language voice/engine overrides.videos/<demo>.<lang>.mp4. Expose the language to the demo script as anARGO_LOCALEenv var, for apps without locale-based routing.argo pipeline <demo> --locale frplus a way to build every language. Subtitles and chapters come out per language for free.Things to keep in mind:
baseUrlwork in feat(tts): OpenAI engine talks to any OpenAI-compatible server #58.argo export, preview export, and variants (see CLAUDE.md). README andskills/argo-guideneed updates too.Could you post a short design sketch here first (manifest layout, config shape, CLI) before opening a PR? Happy to iterate on it with you.
lordrip commentedon Oct 27, 2026
Hi @shreyaskarnik, thanks for the reply, absolutely, that's my goal, first get the design right and agreed, then implement.
Yes, I agree, we would need to record everything, we're just gonna reuse the scene steps.
I'll draft something and post it in this very same issue. Thanks once again.
shreyaskarnik commentedon Oct 27, 2026
Sounds good, looking forward to the sketch! 🙌