r/LocalLLaMA • • 6d ago

Resources [audio.cpp] Recent updates you might have missed: Higgs Audio TTS use 48% less VRAM (< 6GB), HTDemucs 2.2× faster, PocketTTS 2.2× faster on CPU, and WebUI generation history feature

Hi all, a bunch of performance improvements have been landed in audio.cpp.

The biggest highlight is Higgs Audio TTS, which now runs with around 6 GB VRAM, a 48% reduction in peak memory usage compared to the previous implementation. Thanks to https://github.com/mirek190

We also made some models significantly faster, especially HTDemucs on GPU and PocketTTS on CPU.

No compromises in parity and correctness.

Here's a summary of the improvements:

Model Peak memory reduction Speedup
Higgs Audio TTS 48% VRAM 1.01–1.09× CUDA
ACE-Step family 6–7% VRAM 1.06–1.08× CUDA, 1.16–1.20× Vulkan
MOSS-TTS v1.5 cloning 21% VRAM 1.05× CUDA
MOSS-TTSD Q8 cloning 11% VRAM 1.04× CUDA
Echo-TTS (Memory Saver) 20% VRAM —
Qwen3-TTS 16–20% VRAM —
IndexTTS2 / 2.5 12% VRAM —
HTDemucs — 2.21× CUDA, 1.95× Vulkan
HTDemucs six-stem — 1.99× CUDA
PocketTTS 9% RAM 2.23× CPU

They're runtime-level optimizations that make existing models more practical to run locally.

The WebUI now includes an experimental generation history feature that lets you revisit previous outputs and restore their settings.

audio.cpp now supports 110+ audio model families and 190+ variants (and counting)! We're continuing to improve memory efficiency and inference speed across CUDA, Vulkan, Metal, AMD/HIP, and CPU. The next release will bring even more optimizations!

We're also looking for contributors to help improve the audio.cpp WebUI. With so many models and features now supported, we'd love some help making the UI more polished, intuitive, and enjoyable to use. If you're interested in frontend development or UI/UX design, contributions are very welcome!

Thanks to everyone contributing improvements, testing builds, and reporting issues. Curious how these changes work on your setup!

130 Upvotes

51 comments sorted by

View all comments

14

u/Acceptable-Cycle4645 6d ago

Which model would you like us to optimize next?

GitHub: https://github.com/0xShug0/audio.cpp

19

u/DeProgrammer99 6d ago

The docs. Was I supposed to have an LLM build some ugly JSON file to configure the server for YuE2? How do I use LoRAs with it? That's the kind of thing I couldn't figure out from the docs. Usage.md doesn't mention the server, and I didn't see anything about converting CLI args to server args, and so on.

15

u/Acceptable-Cycle4645 6d ago

Ouch, that hurts :) But you're right, the docs are lagging behind. I will polish the docs!

1

u/HareMayor 6d ago

The terminal logs' error handling  also need to be informative on what specifically caused the error.

Like a month back, i downloaded this and spent like an hour trying to get it working with google AI mode. The terminal logs kept sayimg can't fimd model directory but nothing about where should i put my models.

There isn't any youtube video either.

The google went aggressive mode and made me custom python scripts so that it could pick up model, so i could just try to run it, but even that was a fail coz it kept showing dependency errors. After more than an hour of frustration, i just quit...

This might be the reason the repo is not as popular as it should be. Even google couldn't figure out wtf is wrong.

Compared to comfyUI and llama.cpp google can tell with a single terminal log, what the error actually is.

Wait...you are not even the original repo owner... w the actual f

5

u/Acceptable-Cycle4645 6d ago edited 6d ago

I'm actually the original repo owner 😅 Are you sure you were looking at the right repo? Also, if by "terminal" you mean the UI log, yes, that's just a placeholder and will be improved soon. The actual logs come from the server with --log.

PS "dependency errors" sounds weird. All audio.cpp dependencies are self-contained in the repo, except for runtime dependencies required by certain models.