-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
Activating cache for TTS services #15110
Comments
For Polly TTS, do we remove the existing cache system or do we let the user choose what cache system to be used (through a new option) ? |
Same question for Google TTS. |
Regarding Mimic and VoiceRSS TTS, it is better to wait for the enhancement of all audio sinks before merging the related PRs. |
As you saw, I forgot your question and directly provided a Google TTS PR... I have no doubt that the common cache has more functionnality than the custom google one. My last concern is : is there some remaining unseen bug in the common TTS cache ? No one is complaining in the 4.0. milestone versions, but as it is not implemented in any TTS, the opposite would be surprising ! |
In case you have time to propose the PR for Polly TTS before the 16th of July, I will take the time to review and merge it.
I made tests myself with positive results. I am running the VoiceRSS updated version since several days. |
#15228 |
Now done for all TTS services |
A LRU cache is available in core framework. The use of this cache has to be enabled for each TTS service:
An option exists to disable the cache..
The text was updated successfully, but these errors were encountered: