Mark Backman

Ok, that's helpful. Flows relies on function calling to make transitions between nodes. Previously (versions earlier than 0.0.60), function calls were susceptible to being interrupted, which would cause them to...

Sorry for the delay. Here's the PR in question: https://github.com/pipecat-ai/pipecat/pull/1508. I added this change because the assistant context aggregator was blocking user `BotStoppedSpeakingFrames`. This is unlikely to have an impact...

Also, generally, common causes for the bot not responding are that the VAD picked up a human-sounding input but the STT service couldn't transcribe it. You could also look for...

@abrar360 are you still having issues?

It sounds like there may have been an interruption cause by background noise. This is a common issue and requires a noise cancellation solution to filter out background noises and...

Something has to cause the bot to stop responding. The mechanism for that is an InterruptionFrame which happens when either the application pushes it or the user starts speaking. The...

You're right, this is an issue. We are planning to migrate away from the internal `match_endofsentence` util to something more robust. We haven't put the time in yet, but this...

There are a few issues like this one. I'm going to close this and instead track in an issue where we'll ultimately implement an improvement to end of sentence detection:...

@Razziat are you still impacted? I'd recommend using SileroVADAnalyzer as it has superior performance.

Two questions: - What are your VAD settings? - What version of Pipecat? In 0.0.57, we added handling for the case where the VAD doesn't fire but a TranscriptionFrame is...