Well - he works when using google voice set from home.mycroft.ai. The problem is when using the american voice (mycroft mimic2). And I do like a male voice. But I dont like Allan Pope and not like that he uses some of the one and some of the other 
But maybe I should give OpenVoiceOS try 
1 Like
Try deleting the TTS cache, if then you only get the mimic1 voice perhaps the issue is as simple as a dns problem not be able to reach te servers.
Btw, by the time you are fully back we should be able to give you a fancy OVOS build😜
Where is the tts cache located ?
I did look at networkissues, but didnt find anything that cold be problem.
I will try my Pi3 board and see if it could be the Pi4 tht has some hardware issues.
cache is under /tmp/mycroft/
Sounds like it’s timing out somehow and coming back at odd times. But audio.log should have something about that somewhere if so?
Hence the back and forth. Odd.
Could be our TTS server is borking and giving out 500 errors. Anyone else having this trouble?
1 Like
I just set up one more Picroft on a Pi3 board to make sure it wassnt he Pi4 board that had some issues. But same behavior. So if it isnt my network which I have checked in and out it points to the Mycroft TTS server which also is the one giving the 500 error.
@gez-mycroft - can you take a peek at our TTS server and see if it has fallen on it’s head or if someone has scripted a TTS transcription of The Holy Bible or something?
2 Likes
And if so replace the text with something from Lovecraft or Herbert.
2 Likes
Not sure if this helps or even related but I am using the American male voice as well and it loves to switch back to Allan pope. `Setup was working fine before I did the latest pull. Was using code back in February before that pull.
2020-10-23 19:06:04.641 | DEBUG | 3890 | urllib3.connectionpool | https://mimic-api.mycroft.ai:443 "GET /synthesize?text=How%20long%20of%20a%20timer%3F&visimes=True HTTP/1.1" 200 70680
19:06:04.641 - urllib3.connectionpool - DEBUG - https://mimic-api.mycroft.ai:443 "GET /synthesize?text=How%20long%20of%20a%20timer%3F&visimes=True HTTP/1.1" 200 70680
2020-10-23 19:06:08.141 | DEBUG | 3890 | mycroft.audio.audioservice:_restore_volume_after_record:342 | No audio service to restore volume of
2020-10-23 19:06:08.879 | INFO | 3890 | mycroft.audio.speech:mute_and_speak:127 | Speak: I'm starting a timer for twenty five minutes
2020-10-23 19:06:08.880 | DEBUG | 3890 | mycroft.tts.mimic2_tts:get_tts:232 | Generating Mimic2 TSS for: I'm starting a timer for twenty five minutes.
2020-10-23 19:06:08.956 | DEBUG | 3890 | urllib3.connectionpool | https://mimic-api.mycroft.ai:443 "GET /synthesize?text=I%27m%20starting%20a%20timer%20for%20twenty%20five%20minutes.&visimes=True HTTP/1.1" 200 139201
19:06:08.956 - urllib3.connectionpool - DEBUG - https://mimic-api.mycroft.ai:443 "GET /synthesize?text=I%27m%20starting%20a%20timer%20for%20twenty%20five%20minutes.&visimes=True HTTP/1.1" 200 139201
2020-10-23 19:06:16.163 | INFO | 3890 | mycroft.audio.speech:mute_and_speak:127 | Speak: An error occurred while processing a request in Timer Skill
2020-10-23 19:06:16.164 | DEBUG | 3890 | mycroft.tts.mimic2_tts:get_tts:232 | Generating Mimic2 TSS for: An error occurred while processing a request in Timer Skill.
2020-10-23 19:06:16.257 | DEBUG | 3890 | urllib3.connectionpool | https://mimic-api.mycroft.ai:443 "GET /synthesize?text=An%20error%20occurred%20while%20processing%20a%20request%20in%20Timer%20Skill.&visimes=True HTTP/1.1" 500 290
19:06:16.257 - urllib3.connectionpool - DEBUG - https://mimic-api.mycroft.ai:443 "GET /synthesize?text=An%20error%20occurred%20while%20processing%20a%20request%20in%20Timer%20Skill.&visimes=True HTTP/1.1" 500 290
2020-10-23 19:06:16.260 | ERROR | 3890 | mycroft.audio.speech:mute_and_speak:131 | Backend returned HTTP status 500
2020-10-23 19:06:16.261 | DEBUG | 3890 | mycroft.audio.speech:mimic_fallback_tts:146 | Mimic fallback, utterance : An error occurred while processing a request in Timer Skill
2020-10-23 19:23:28.223 | DEBUG | 3890 | mycroft.audio.audioservice:_restore_volume_after_record:342 | No audio service to restore volume of
2020-10-23 19:23:29.250 | INFO | 3890 | mycroft.audio.speech:mute_and_speak:127 | Speak: The timer for twenty five minutes has seven minutes thirty nine seconds remaining
2020-10-23 19:23:29.251 | DEBUG | 3890 | mycroft.tts.mimic2_tts:get_tts:232 | Generating Mimic2 TSS for: The timer for twenty five minutes has seven minutes thirty nine seconds remaining.
2020-10-23 19:23:29.254 | DEBUG | 3890 | urllib3.connectionpool | Resetting dropped connection: mimic-api.mycroft.ai
19:23:29.254 - urllib3.connectionpool - DEBUG - Resetting dropped connection: mimic-api.mycroft.ai
2020-10-23 19:23:29.588 | DEBUG | 3890 | urllib3.connectionpool | https://mimic-api.mycroft.ai:443 "GET /synthesize?text=The%20timer%20for%20twenty%20five%20minutes%20has%20seven%20minutes%20thirty%20nine%20seconds%20remaining.&visimes=True HTTP/1.1" 500 290
19:23:29.588 - urllib3.connectionpool - DEBUG - https://mimic-api.mycroft.ai:443 "GET /synthesize?text=The%20timer%20for%20twenty%20five%20minutes%20has%20seven%20minutes%20thirty%20nine%20seconds%20remaining.&visimes=True HTTP/1.1" 500 290
2020-10-23 19:23:29.591 | ERROR | 3890 | mycroft.audio.speech:mute_and_speak:131 | Backend returned HTTP status 500
2020-10-23 19:23:29.592 | DEBUG | 3890 | mycroft.audio.speech:mimic_fallback_tts:146 | Mimic fallback, utterance : The timer for twenty five minutes has seven minutes thirty nine seconds remaining
1 Like
Hey there, thanks for flagging this, after some investigations my hypothesis is that it’s an issue in the cache.
I currently don’t have access to that system, but if it’s what I think it is, will hopefully have it resolved when the Americans wake up.
2 Likes
I know this is a very old thread – but for the last 2 days I am having exactly the problem described here. I tried deleting the cache as mentioned above, and had no change. The audio log shows http 500 errors, such as:
2022-01-27 19:18:09.664 | INFO | 1591 | mycroft.audio.speech:mute_and_speak:127 | Speak: It’s currently clear sky and 20 degrees fahrenheit.
Playing WAVE ‘/tmp/mycroft/cache/tts/Mimic2/a18ba8f65e41175ee80cd18448d887ec.wav’ : Signed 16 bit Little Endian, Rate 22000 Hz, Mono
2022-01-27 19:18:13.293 | INFO | 1591 | mycroft.audio.speech:mute_and_speak:127 | Speak: Today’s forecast is for a high of 20 and a low of -11.
2022-01-27 19:18:13.379 | ERROR | 1591 | mycroft.audio.speech:mute_and_speak:131 | Backend returned HTTP status 500
Playing WAVE ‘/tmp/mycroft/cache/tts/Mimic/1875b6c4b39a73a5bc04b392f045cbae.wav’ : Signed 16 bit Little Endian, Rate 44100 Hz, Mono
It’s actually a little funny sometimes – I asked for the weather in the example above and got the current info in the American voice, and the forecast in the British one. 
Just wondering is anybody has any insights as to what I can do to stop this. I don’t really want to switch to the google voice … kind of defeats the purpose of choosing Mycroft…
I seem to be having the same problem with the voice switching intermittently between the two voices. Also seeing 500 errors. Recently switched to Raspberry Pi OS 64bit as a test so I thought it was something with my setup. Didn’t happen with the original Picroft image.
When I mentioned that to @ChrisVeilleux last Friday is answered this (on the chat).
Maybe the issue is back again 
1 Like
Thanks for the info – it was still happening as of yesterday (2/1/22). I ended up setting up coqui on an old laptop last night. It’s a little slower, but at least it gives a consistent and understandable voice. I’ll keep using that.
1 Like
This has been a long-running problem and needs to be handled with a less-fragile solution.
3 Likes