makeitmore

4 ms·

1. 1.▲
   by makeitmore 2y ago

   Very true. I think we are a bit aggressive with the VAD timeout. The demo was intended to showcase speed, but the bot can be a bit eager! You can tinker with the VAD settings, it could definitely use a bit more air (but that will impact lat
2. 2.▲
   by makeitmore 2y ago

   This particular demo is using Llama3 8B. We initially started 70B, but it was a touch slower and needed much more VRAM. We found 8B good enough for general chit-chat like in this demo. Most real-world use-cases will likely have their own fi
3. 3.▲
   by makeitmore 2y ago

   Thanks for sharing. I did make some changes that seems to have improved things, although I do still see the occasional misfire. Perhaps good enough to remove that ugly red banner though!
4. 4.▲
   by makeitmore 2y ago

   Yes, echo cancellation via the browser (and maybe also at OS-level too, if you're on a Mac with Sonoma.) The accuracy of speech detection vs. noise is largely thanks to Silero, which runs on the client via WASM. I'm surprised at h
5. 5.▲
   by makeitmore 2y ago

   Hi, I built the client UI for this and... yea, I really wanted to get Firefox working :( We needed a way to measure voice-to-voice latency from the end-user's perspective, and found Silero voice activity detection ( https://g
6. 6.▲
   by makeitmore 2y ago

   Most of the Pipecat examples we've been working on are focused on speech-to-speech. The examples guide you through how to do that (or you can give the hosted storytelling example a try: https://storytelling-chatbot.fly.dev&