[BUG] TTS cache
Opened this issue · 3 comments
Description
When using different TTS voices for primary and fallback, I've noticed that Neon will prefer playing back from a cached fallback response over generating a new primary response.
Steps to Reproduce
- Set up a completely different voice as fallback
- Break connection to primary server (/etc/hosts blackhole to 127.0.0.1, firewall, etc)
- Speak to Neon in a way that will get a consistent response back ("what is the mean airspeed of an unladen swallow")
- Reconnect the primary server
- Use the same utterance as two steps before
Relevant Code
No response
Other Notes
No response
Relevant Matrix chat: https://matrix.to/#/!EOygeDJPfJQOfNacqH:matrix.org/$oNUCIIX1v5EiXAg9Ud3quSByZzqSqDe3Zu3BUl67HC0?via=matrix.org&via=mozilla.org&via=studichat.de
It seems this is an OPM bug and belongs there, but I can't transfer the issue
@mikejgray was this resolved in ovos-plugin-manager or is there a relevant issue there that can be referenced as closing this one?
@mikejgray was this resolved in ovos-plugin-manager or is there a relevant issue there that can be referenced as closing this one?
Nope, this is definitely still an issue