-
Notifications
You must be signed in to change notification settings - Fork 80
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
Reusing Polly existing file content rather than calling AWS every time? #42
Comments
Hey @mikaelwozniak, this library is not currently designed to support storing and replaying audio. That said, if you wanted to achieve that you could look into creating some custom functionality with the resulting pre-signed url returned from AWS Polly: |
@mikaelwozniak Any luck with this? I'm trying to do the same thing |
@mikaelwozniak and @charles-hay, can you explain what your motivation is for wanting to use locally cached audio and viseme data? Amazon Polly automatically serves cached versions of that data when called with the same parameters (voice ID, speech text, language ID). There's no cost to you when that happens. You only pay when unique new audio is generated. So you wouldn't be saving cost. Is there some other benefit you're looking to achieve with local caching? |
... @mikaelwozniak oh well I wasted a lot of time 😓 |
If my application has a set list of hardcoded texts to be said by the virtual host, I shouldn’t need to call AWS Polly every time a new visitor comes on my webpage. I should just have the mp3/api-call-result files saved somewhere and link with those static files.
What is the easiest way to achieve this with this repo code? Many Thanks.
The text was updated successfully, but these errors were encountered: