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

Reusing Polly existing file content rather than calling AWS every time? #42

Open
mikaelwozniak opened this issue Mar 30, 2021 · 4 comments

Comments

@mikaelwozniak
Copy link

mikaelwozniak commented Mar 30, 2021

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.

@jkerste
Copy link
Contributor

jkerste commented Sep 21, 2021

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:

@charles-hay
Copy link

@mikaelwozniak Any luck with this? I'm trying to do the same thing

@Krxtopher
Copy link
Contributor

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

@charles-hay
Copy link

... @mikaelwozniak oh well I wasted a lot of time 😓

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants