Forum Discussion
Translating entire Storyline files with an alternative method
I am searching the "mysterious" not (???) local cache
with a normal local publish to web with storyline 360 (C:\Users\...) "articulate 360 Desktop Services" communicates with 2 amazon aws services
example
- ec2-52-45-64-241.compute-1.amazon.aws.com (Ashburn, Virginia, United States)
- ec2-44-196-72-199.compute.1.amazon.aws.com (Ashburn, Virginia, United States)
@ariculate: why are my (european) data with local publish copied to us amazon cloud ???
Hi Jürgen,
But Storyline uses AWS anyway when generating the audio from the TTS content (Amazon Polly is the name of the API)...
Still I am wondering: is this mysterious cache file that we cannot locate on a distant Amazon server? It could be the answer. To validate this hypothesis, we could try to publish again a .story file that has been already puslished and has not been changed while putting the local computer offline. Thus we could ensure no external communication is necessary, and that no external cache file is needed.
I cannot do this at the moment, but feel free to precede me if you can.