You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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 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?
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: