Forum Discussion

marcr's avatar
marcr
Community Member
13 hours ago

Storyline 360 - Converting AI Voiceover to Text-to-Speech bug?

We are in a situation where we need to convert AI Voiceovers to Text-to-Speech so that we can better control pronunciation of a word. All of these voiceovers already have the Closed Captions in place and in an effort not to duplicate work, it was suggested to use this process:

  • Right click on AI voiceover in timeline
  • Select Text-to-Speech from hovering menu
  • In the Insert Text-to-Speech modal, uncheck "Generate Closed Captions"
  • Click "Update"

While showing a coworker this process, I was able to do this once. However, on subsequent attempts to complete the same process, nothing happens when Update is clicked (other than the Text-to-Speech modal closes). No progress bar is displayed, no Text-to-Speech object is created.  I've restarted Storyline, restarted my PC, and have had coworkers reproduce the same issue. 

Can anyone else confirm this and/or offer advice? Thanks in advance.

 

2 Replies

  • marcr's avatar
    marcr
    Community Member

    jimmyadne, thanks for the reply and suggestion. I, along with two others did the following:

    • Created a brand new SL file
    • Added AI Voiceover to a slide
    • Under Manage Closed Captions, created AI CC and saved
    • Selected the AI Voiceover on timeline and right clicked
    • Choose Text-to-Speech from menu
    • In modal, unchecked "generate closed captions"
    • Clicked update

    We did this on two slides. On the first slide the conversion to Text-to-Speech worked. On the second slide, and any subsequent attempt, the conversion does not happen.

    So basically, it works once in a file and never again. I'm fairly sure this is a bug. Hopefully someone outside our organization can repeat the issue.

  • jimmyadne's avatar
    jimmyadne
    Community Member

    That definitely sounds unexpected, especially if the workflow succeeded once and then consistently stopped creating the Text-to-Speech object afterward. Since multiple people can reproduce it, it seems less likely to be a project-specific issue. I'd be curious whether it happens in a brand-new Storyline file with a simple AI voiceover as well, as that could help narrow down whether it's related to the conversion process itself or something specific to existing captions and project settings.