Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

This looks really interesting.

I feel like there is a lot of room to build great voice-based agents that don't exist right now.

I have found that ChatGPT voice mode is unusable (e.g. hallucinates me saying things); Claude voice mode is usable, but very buggy around tool calling, and it often mishears things. And it only supports Opus, not Fable (though it looks like you don't support either of those). But I use it anyway.

Question, do any of your TTS options support increasing the speaking speed?



> I feel like there is a lot of room to build great voice-based agents that don't exist right now

I agree. Even Codex’s new voice mode isn’t just “It does things I tell it”, all commercially available voice modes have to be dumbed down in the name of latency for some reason. I have even experienced the latency being uncomforably low before.

This is what I enjoy the most about my in-development personal OpenCode client: It’s just STT-LLM-TTS with the original model and all of its capabilities. Latency is obviously higher, but I don’t mind that much given the upside (would be interesting to optimize for completely blind usage, my current MO is mostly hybrid).


thanks! yes, some of them do, cuz speed is a per-provider capability, not universal. And, you can see it in the gateway code (minimax, hume, xai tts adapters all handle a speed param). that unevenness is actually a routing constraint by itself: "voices that support rate control" narrows the candidate list the same way language or latency does. and agree on the voice modes, the gap between the demo and a dependable agent is exactly why we started this. what are you building with it?




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: