-
-
Notifications
You must be signed in to change notification settings - Fork 167
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TTS not working on microsoft edge #39
Comments
reproduced it, and here is the edge browser console log
|
Can you try update to the latest version ( |
I deployed v0.4.1 this time, in my first two cases, edge can only play one of the audio (not the first, not the last, but one in the middle), and failed to play any other audio in firefox, everything is fine //loading is much faster, cool the second of my two casesin the case below, VERBOSE: False edge browser log
meanwhile terminal log of the comversation loop
third case with VERBOSE: Truesimilar browser console log terminal log of a conversation loop
|
tried in ipad firefox, similar TTS issue |
//thank you so much, great project :)
Description
ubuntu 24.04, kde
Microsoft Edge 131.0.2903.51
ollama (LM studio), llama3.2
I followed deploying instructions in readme, and tested in edge
despite some effort, everything seems fine, but the TTS isn't working
to be clear, I can't hear any audio response
log says payload sent and audio played, but actually not
later I tried in firefox, and TTS is fine
I am not sure whether it's a real bug or a problem caused by edge itself
also works on chromium
//tell me why, edge!
part of my settings in conf.yaml:
I tried different TTS, including edge-TTS, AzureTTS, pyttsx3TTS
none of them works
I played audio files in cache manually (.wav for AzureTTS, .aiff for pyttsx3TTS...)
it's normal, not empty
in the very first start (yesterday), I might used edge-TTS
there are some cases that the first audio response is played, but only the first one
and now there is no audio response at all
Logs/Console Output
I set verbose to true in conf.yaml
didn't found anything critical in console log, though
typical audio log, when TTS fails
init before the conversation
The text was updated successfully, but these errors were encountered: