Authorization notice. AuK is dual-use. Only use it on software, sites and systems you own or have explicit permission to test.
Who it is forA game or app developer who needs a placeholder narrator voice and has no recording to start from.
The problemFinding or recording a voice for prototype dialogue takes time before the content can be tested.
The outcomeA WAV file with the requested text spoken in the described voice.
What you need first
- Python 3.10 and uv or Conda
- A GPU with enough VRAM to run the model (CPU offload is CUDA only)
- Disk space and network access to download the AuK weights and the Qwen2.5-Omni-3B encoder from Hugging Face or ModelScope
- Source audio or a reference clip for tasks that need one
Steps
uv venv --python 3.10source .venv/bin/activateuv pip install -e .hf download tencent/AuK --local-dir ./ckpts/AuKauk-infer --instruction "<voice description and the text to speak>" --output <out.wav> --gen_seconds 6.0(inferred, check the README)
Prompt for your agent
In the Tencent-Hunyuan/AuK repo, use auk-infer with only an --instruction that describes the voice and contains <target text>, and write the result to <out.wav>. Verify that <out.wav> is created and that its length is close to the requested seconds.
Caveat. The README lists instruct TTS as a task but does not show its exact command, so the example call here is inferred from the general instruction pattern.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: 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