griffin Peter

One thing I’ve been thinking about while working on Seed Audio 1.0 is how quickly an AI audio workflow becomes complicated once you move beyond simple text-to-speech.

A basic TTS tool is straightforward: type text, pick a voice, generate. But real use cases rarely stay that simple.

Someone might want multi-character dialogue, add background music that matches the mood, include ambient sound, and keep voice consistency across a longer scene. At that point the challenge isn’t just “generate better audio.” It’s making all those elements work together without forcing the user into a complicated multi-step process.

That’s the problem Seed Audio 1.0 is trying to solve.

Instead of generating voice, music, and effects separately and then mixing them, it treats the whole thing as one scene. You describe what you want — the dialogue, the emotion, the environment, the background — and it produces a fully mixed audio track in a single pass.

The interesting product question for me right now is how much control to expose.

Should advanced options (reference voices, timing control, multi-speaker settings) be visible from the start, or revealed only when someone actually needs them?

Too many controls make the first generation feel heavy. Too few, and power users feel limited.

I’m still testing where that balance should be.

Building: https://seedaudio.co/

For other builders working on generative tools: how do you add more capability without making the creation process feel heavier?