LiveKit

“I was very dissatisfied with the built-in Foundry audio chat. So much so that I completely disabled it and defaulted to Discord for Audio. However, I later tried LiveKit, and have been 100% satisfied with its quality. So much so that I’ve stopped using Discord with my players completely. (Note: I’m using the Forge hosting service for my Foundry instance, so my LiveKit setup was already complete when I paid for the service. No config necessary.) -My $0.02”

“having built the prototype of twilio -> nodejs with livekit + deepgram + cartesia + openAI I have faced challenges, which were not obvious at the beginning and for which I didn't find answers online or with Claude Code. So I am curios if anyone has solved these issues on real production systems. Most obvious problem is not only the latency, which is btw. never smaller than 1 second, even if switching to Groq llama3.1-instant-8b instead of openAI and reducing the silence threshold for Voice Activ”

“When starting off, I’d focus on nailing the use case rather than devising a local LLM architecture because it adds so much more complexity. Especially because latency is a real factor. I have tried VAPI, pipecat, OpenAI realtime agents, eleven labs but ultimately settled on using LiveKit Voice Agents, primarily because of their end-of-turn detection model. I saw some others launch something similar but nowhere close to the LK EOT model imho (at least when I tested them). But for others use cases”

“Hi folks, how come no one is talking about livekit, on their site it says « OPENAI uses livekit to deliver voice to millions of users », it’s probably what was used behind gpt-4o demo too. They have examples to test on their github repo, after trying them, i can say its the fastest and most realistic one i’ve seen. For STT, They use deepgram nova-2 speech to text model, crazy fast model, deepgram offer 200$ free credits to all new users and its 0.0043$/min for the model. For TTS, you can use ope”

“Hi folks, how come no one is talking about livekit, on their site it says « OPENAI uses livekit to deliver voice to millions of users », it’s probably what was used behind gpt-4o demo too. They have examples to test on their github repo, after trying them, i can say its the fastest and most realistic one i’ve seen. For STT, They use deepgram nova-2 speech to text model, crazy fast model, deepgram offer 200$ free credits to all new users and its 0.0043$/min for the model. For TTS, you can use ope”

“having built the prototype of twilio -> nodejs with livekit + deepgram + cartesia + openAI I have faced challenges, which were not obvious at the beginning and for which I didn't find answers online or with Claude Code. So I am curios if anyone has solved these issues on real production systems. Most obvious problem is not only the latency, which is btw. never smaller than 1 second, even if switching to Groq llama3.1-instant-8b instead of openAI and reducing the silence threshold for Voice Activ”

“Can’t believe how fast it is. That’s crazy responsive!”

“We ran into the same latency bottlenecks when building a voice-AI call center on LiveKit. The trick that helped us the most was swapping the commercial STT for an open-source Whisper model hosted on a GPU-instance and using a lightweight LLM for the dialogue. If you need a fully self-hosted stack that drops the call-setup time to under 2 seconds, check out Dograh AI – it’s open source, lets you plug-in any STT/TTS you like, and even ships a ready-to-run voice-bot in 2 min template.”

“The official line is we don't add any artificial barriers to migrate from LiveKit Cloud to self-hosting, or vice-versa and it really is as simple as swapping out the LIVEKIT_URL. As others have said, the hard part moving to self-hosting is the extra work required to scale each service, front them with a load balancer and TLS, manage certificates and TURN, run Redis for coordination, and own the monitoring, patching, capacity planning, and incident response. Everything related to media transport,”

“I am working with livekit. I want to update the room's metadata, but the documentation is not great for Vanilla JavaScript use case (I'm not using a framework) and I don't know how to decode their documentation as a beginner because it's not written in a step by step way for vanilla js or have any examples: Here is the documentation for updating a room's metadata: https://docs.livekit.io/home/client/data/room-metadata/ https://docs.livekit.io/reference/server/server-apis/ https://docs.livekit.io”

“Livekit works great, but you've got to have some command line savvy to get it working, along with a central server on a good connection. The main issue with the built in AV is that the architecture is peer-to-peer , like a web. It works fine for small groups of people who all have fast and stable Internet connections to each other. Because it's p2p though, each new participant has to make their own connections to each existing participant, so the whole thing gets exponentially more complex and s”

“I use livekit and it is way better than the built in AV as I have some players with poorer internet connections. I myself am on symmetrical gig, so I can’t speak to how it will perform on a 25mb upload. I do however have it running on a server with 3 foundry servers, and they can all share a single livekit instance which is awesome. My server runs a 4th gen haswell cpu, so as far as resources go you should be good there. It took me a while to get livekit set up because the instructions are so in”