Text-to-speech update - voice not audible/played anymore afterwards

Mar 27, 2023

Hello, 

I am working a lot with the Text-to-speech funtionality. Often, when I am updating an already created audio file because I did a spelling mistake or want to change the phrase, and then want to listen to it again, it is not audible anymore when pressing the play button for the slide I work on, and neither when checking the preview of the slide / scene. 

Sometimes, a restart of Storyline does work, but not always, which then leads me to recreate my audio files with a new text-to-speech insert to have them audible again.  

Do you know why this is happening and how I could avoid this behavior? I am working with Articulate Storyline 360.

3 Replies
Eric Santos

Hi Anne,

Welcome to E-Learning Heroes! I'm sorry to hear you're hitting this snag with text-to-speech. We can start by checking if you're working on your local drive; working on a network drive can cause erratic behavior. If the problem still happens, try running these steps to repair Storyline.

We'd be glad to investigate further if the problem persists. You may share your Storyline project here or privately in a support case so we can take a look. We'll delete it when we're done testing.

Submit a Support Case

J-M Guillemette

I have the same problem. After working on a slide with narration that has been set and worked well to that point, the title of the narration sometimes changes on its own after a make some adjustment to the slide (not necessarily to the narration). The object title becomes an alphanumeric string that doesn't correspond to what it was. When I try running the slide from the timeline, I can't hear the narration. I've tried renaming the object and re-generating my text-to-speech without success. I can hear the narration if I preview the slide but not when I test it in the timeline. Very annoying.   

Jose Tansengco

Hello J-M,

Sorry to hear that you ran into a similar issue. 

We're not seeing a lot of users report this behavior, so this appears to be specific to certain environments. If you're already working locally, try doing a repair of your Storyline 360 installation to see if this helps. 

If the issue persists after doing a repair, would you be willing to share a copy of your project file here or in private by opening a support case so we can take a closer look at what's happening? We'll delete it when we're done testing!