Closed MatthewJSalerno closed 2 years ago
Resolved due to an error in my config. Here's a working config.
{
"max_allowed_core_version": 21.2,
"hotwords": {
"hey mycroft": {
"module": "ovos-precise-lite",
"model": "~/models/precise-lite-models/wakewords/en/hey_mycroft.tflite",
"sensitivity": 0.5,
"trigger_level": 3
}
},
"tts": {
"module": "mimic3_tts_plug",
"mimic3_tts_plug": {
"voice": "en_US/vctk_low",
"speaker": "p283",
"length_scale": 1.2,
"noise_scale": 0.667,
"noise_w": 1.0
}
}
}
Awesome :+1:
I did find an issue when I restarted everything (docker-compose down/up). If the voices aren't cached the mimic3 will fail on startup.
If I log into the container and execute:
mimic3 --voice en_US/vctk_low#p283 "test" > /tmp/output.wav
it will download the voice data to /home/mycroft/.local/share/mycroft/mimic3/voices/, which gets clobbered on restart. It looks like it needs a volume like Precise-lite with a local clone of https://github.com/MycroftAI/mimic3-voices
@MatthewJSalerno thanks for flagging this, could you please open a new issue with this?
@MatthewJSalerno I created the issue and pushed a change, let me know in #30 if it fixed your issue.
I created https://github.com/smartgic/docker-mycroft/issues/31 which is pretty damn close to the latest commit. I need to clean up my system and then I'll try it out. Thanks.
Thank you for putting the effort into splitting this out.
Debian 11 64-bit Raspberry Pi 4 (8gb)
I've gotten the stack up and running but when I switch from mimic to mimic3 and any audio response gets generated, I get an error.
I've tried
$ mycroft-config set tts.module mimic3_tts_plug
As well as the example config from the mimic3 GitHub page
I've only started tinkering with this and I'll post any progress I make, I'm curious if anyone has gotten this working.
Thanks