DEDUPED Hot AI repos, turned into use cases Get the Monday 5

How to speak English and hear the Bosnian reply with Lilly

Talk in English, get the Bosnian reply, and hear it read aloud in Bosnian.

Who it is forA person in a Bosnian-speaking meeting or class who wants to answer in Bosnian without knowing how to say it.

The problemYou know what you want to say in English but cannot produce a correct Bosnian reply or pronounce it.

The outcomeA Bosnian text reply and a spoken Bosnian reply from your English words.

What you need first

  • Python 3.12 and uv for the local install, or a browser for the live demo
  • Internet access for the first model fetch; the README says nothing reaches the network after fetch_models.py finishes
  • Optional: a microphone for speech and a camera for photographs

Steps

  1. Set up and fetch the models with the README steps, including .venv/bin/python scripts/fetch_models.py
  2. Start the server: .venv/bin/uvicorn app.server:app --port 8000
  3. Open http://localhost:8000 and press the swap arrow between the two language names so Lilly hears English
  4. Press the microphone, say your English sentence, and read the Bosnian reply
  5. Play the spoken reply, which uses the Bosnian voice

Prompt for your agent

In the repo ssaaffaakk/Lilly, confirm that translator-en-bs/ and speak-bs/ exist after setup, then call POST /api/reply with the English text <english sentence>. Expected output: the Bosnian reply text. Verify that /api/speak with language bs returns WAV audio rather than a 503.

Caveat. The Bosnian voice is a stock regional Piper checkpoint trained on Lower Sorbian recordings, and the README measures its output at 22.3% word error, so it is not a native Bosnian voice.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page