This is a list of known issues. For the latest list of all issues see the Github Issues page.
Seems to be a very well-known issue with iOS devices. Apple requires a user event to play audio in the browser - basically.
A possible fix is to use the launchpage click to start the app to play a zero-audio mp3 file, and change the context of that audio object when playing audio from the queue.
See: https://matt-harrison.com/posts/web-audio/ Issue: #4
Caused by a user not using peer-devices. Here is the ticket: https://bugs.chromium.org/p/chromium/issues/detail?id=687574 It basically says that the echo cancellation only works for audio that is coming from a peer connection. As soon as it is processed locally by the Web Audio API it will not be considered anymore by the echo cancellation.
Possible fix is to go ahead and volume-down the playback when you start speaking. This will improve the barge-in experience, and possibly duck the playback under the microphones' decibel threshold so it doesn't pick itself up.
Issue: #5
Rename ErrorContextProvider to be a general toast message handler.
See: https://tailwindui.com/components/application-ui/overlays/notifications Issue: #6
We have not plugged ANY errors into the ErrorContextProvider yet.
Issue: #7
Request errors should retry (and display notice when "taking longer than usual" using the ErrorContextProvider)
Issue: #8
We'd like to be able to start the TTS response earlier. We have chunking logic for JavaScript, so we want to buffer the TTS input as a stream, clear the buffer into individual TTS requests, and combine the responses into a single response stream.
See: https://www.npmjs.com/package/multistream Issue: #12