Pinned Reply
Hi, everyone!
I have some great news to share. We just released another update for Storyline 360. In Update 83, we’ve included important fixes and new features!
One enhanced feature we’ve included:
Unlock new possibilities for text-to-speech audio. Use speech synthesis markup language (SSML) to adjust the speaking rate, modify pronunciation, emphasize words, add pauses, and more.
To take advantage of this update, launch the Articulate 360 desktop app on your computer, and click the Update button next to Storyline 360. You'll find our step-by-step instructions here!
34 Replies
Hello Richard,
I'm sorry to hear that the new SSML feature isn't working properly for you.
I'd like to take a closer look at your project files to see why the tags are being read as text and not as proper SSML markups. Would you be willing to share a copy of your project files here or in private by opening a support case for testing? We'll delete it when we're done!
Hello John
The reason why the tags like <emphasis> were being read in the "modified_ssml_suppoort.story" file is because this tag only supports Standard voices while the voice used in the slide was a Neural one. You can check out this article for more information on correct usage of supported tags.
I have been using SSML tags with standard voices because I would like to apply the "whisper" effect. The standard voice, however, reads the SSML tag. I am using version V3.83.31444.0, if that helps with resolving my issue.
What am I doing wrong to get this to work? I have attached a screen capture of the text to speech window for your reference. Thank you so much!
I'm having the same issue with SSML tags as others seem to be experiencing. Suddenly the SSML tags stop being used and it reads the tags as text.
Almost as if it lost connection to the voice-servers and defaults to reading the text as-is.
Hello Meenu and Joel,
Happy to help!
Please share a copy of your project files here or in private by opening a support case so we can take a look at how you have your SSML tags and text declared. We'll share the fixes here and we'll delete the files when we're done testing!
It's really a great feature. However, I've selected a standard voice but it keeps reading the <start> text <break> more text </break></start>
what am I doing wrong?
Sorry for borrowing an "old" question to ask this new one.
The <break> tag requires a bit more help from you in that it needs a duration. For example,
<break time = ".3s"/>
For more on supported SSML tags, please see this resource:
https://docs.aws.amazon.com/polly/latest/dg/supportedtags.html
Please note - these are Amazon Polly tags which is the underlying text-to-speech service that Storyline uses.
I hope this helps!
Thor
Is there any information, timeline or future update coming out that will allow standard voices in English (US)? I understand that there are only Neutral voice but really wondering if this is in work for any future updates ? Thank you for any and all information.
Hello Cory,
We don't have any updates to share on whether the current behavior for standard voices in English (US) will be changed, but you can check our product roadmap here to know which features are in the works, and you can also share feedback with our product team through a feature request!
I'm demonstrating some of what I've learned about using SSML to some fellow Storyline developers and thought others might find the examples useful. I've posted them here: Why SSML? | Review 360 (articulate.com)