Forum Discussion

yukataniyama's avatar
yukataniyama
Community Member
11 months ago

Insert SSML tags

Hello everyone,  TTS doesn't work correctly when I insesrt SSML tags. TTS speaks body and the tags too. I tried neulal voices, both Japnese language and English(US) language. The both language...
storyline 360
  • StevenBenassi's avatar
    StevenBenassi
    10 months ago

    Hi Everyone!

    I'm happy to share that we just released Storyline 360 (Build 3.84.31647.0) which includes the fix for the bug:

    • Storyline reads the SSML tags in the TTS script if there is a blank space or line break at the beginning/end of the code

    Now all you need to do is update Storyline 360 in your Articulate 360 desktop app to take advantage of the newest bug fixes and features!

    If you run into any issues, please don't hesitate to reach out to our team by submitting a support case.

JenniferBell901's avatar
JenniferBell901
Community Member
11 months ago

I just started at this company and am unsure of my ability to share something i am working on- but I will double check my coding and try again. I am not sure if i used a trailing white space, typically when i use HTML, i didn't think we were supposed to have spaces. Thanks. I will update this after I try that. 

  • Mike_Marcos's avatar
    Mike_Marcos
    Staff
    11 months ago

    Hi Jennifer, sorry about the confusion there. The original post talks about a different issue where a trailing white space or line break causes Storyline to read the SSML tags instead of applying the effect. 

    Your issue is different, since Storyline is showing a warning "storyline 360 can't convert this text to speech..." and not generating the TTS audio at all. This usually means there is a problem with either formatting or using a tag that the voice type doesn't support. i.e. <emphasis> isn't supported by Neural voices, so using a Standard voice should work.

    You mentioned that adding the <p> tag causes the warning to show, and one thing I can think of is if the tag isn't paired with a closing </p> as shown in this example:

    <speak> 
    <p>This is the first paragraph. There should be a pause after this text is spoken.</p> 
    <p>This is the second paragraph.</p> 
    </speak>

    If you can't share the script here, you can share the script or project file with us privately by opening up a support case instead. 

    • MaxBooher-0fbd6's avatar
      MaxBooher-0fbd6
      Community Member
      10 months ago
      Michael Marcos

      Hi Jennifer, sorry about the confusion there. The original post talks about a different issue where a trailing white space or line break causes Storyline to read the SSML tags instead of applying the effect. 

      Your issue is different, since Storyline is showing a warning "storyline 360 can't convert this text to speech..." and not generating the TTS audio at all. This usually means there is a problem with either formatting or using a tag that the voice type doesn't support. i.e. <emphasis> isn't supported by Neural voices, so using a Standard voice should work.

      You mentioned that adding the <p> tag causes the warning to show, and one thing I can think of is if the tag isn't paired with a closing </p> as shown in this example:

      <speak> 
      <p>This is the first paragraph. There should be a pause after this text is spoken.</p> 
      <p>This is the second paragraph.</p> 
      </speak>

      If you can't share the script here, you can share the script or project file with us privately by opening up a support case instead.

      This is a really important fact that should be added to the "troubleshooting tips" on this page:

      https://access.articulate.com/support/article/Storyline-360-SSML-Support

       

      Would have saved me (and others, clearly) a lot of time and frustration.

Related Content