Skip to content
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

Closed
7 tasks done
lolodomo opened this issue Jun 18, 2023 · 7 comments
Closed
7 tasks done

Activating cache for TTS services #15110

lolodomo opened this issue Jun 18, 2023 · 7 comments
Labels
enhancement An enhancement or new feature for an existing add-on

Comments

@lolodomo
Copy link
Contributor

lolodomo commented Jun 18, 2023

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..

@lolodomo lolodomo added the enhancement An enhancement or new feature for an existing add-on label Jun 18, 2023
@lolodomo
Copy link
Contributor Author

lolodomo commented Jun 19, 2023

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) ?

@lolodomo
Copy link
Contributor Author

Same question for Google TTS.

@lolodomo
Copy link
Contributor Author

lolodomo commented Jul 1, 2023

Regarding Mimic and VoiceRSS TTS, it is better to wait for the enhancement of all audio sinks before merging the related PRs.

@dalgwen
Copy link
Contributor

dalgwen commented Jul 9, 2023

Same question for Google TTS.

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.
(I didn't look at Polly TTS recently but I think it is nearly the same). I think we should make the shift, on the paper at least.

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 !

@lolodomo
Copy link
Contributor Author

lolodomo commented Jul 12, 2023

I have no doubt that the common cache has more functionnality than the custom google one. (I didn't look at Polly TTS recently but I think it is nearly the same). I think we should make the shift, on the paper at least.

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.

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 !

I made tests myself with positive results. I am running the VoiceRSS updated version since several days.

@dalgwen
Copy link
Contributor

dalgwen commented Jul 12, 2023

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.

#15228
(But I did not manage to test it, so it's a draft.)

@lolodomo
Copy link
Contributor Author

Now done for all TTS services

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement An enhancement or new feature for an existing add-on
Projects
None yet
Development

No branches or pull requests

2 participants