Forum Discussion
Closed Captions no longer generated automatically?
I have noticed that when I use the AI text-to-speech tool in Storyline that even though the generate closed captions checkbox is selected, the closed captions are no longer being generated.
To get them to work I have to use the separate function to generate the CCs with AI but this is creating extra work for me as there are a lot of product names in my narration and the AI auto-generation mispells these, meaning that I have to manually adjust the captions for every bit of narration, and every time the narration is changed during a review cycle.
Is this expected behaviour following an update to Storyline, or am I encountering a bug?
Hi DavidTait and RonPrice,
I have some great news to share! We just released another update for Storyline 360. In Build 3.110.36211.0, we’ve included important fixes and new features. One of the fixes we’ve included is:
- Captions weren’t generated for text-to-speech narration created with AI Assistant.
This resolves the issue where closed captions weren’t being created automatically for AI-generated narration, even when the option was selected.
Launch the Articulate 360 desktop app on your computer to take advantage of this update, and click the Update button next to Storyline 360. You’ll find our step-by-step instructions here.
Please let me know if you need additional help.
7 Replies
There have been issues with SL generating CC even when the option was not selected. I can replicate the issue here too. Tried in Update 108 where it I know it was working and it is not working there any more either. It does work in the non AI TTS, so the issue seems to be isolated to AI Audio.
Hi DavidTait and RonPrice,
I have some great news to share! We just released another update for Storyline 360. In Build 3.110.36211.0, we’ve included important fixes and new features. One of the fixes we’ve included is:
- Captions weren’t generated for text-to-speech narration created with AI Assistant.
This resolves the issue where closed captions weren’t being created automatically for AI-generated narration, even when the option was selected.
Launch the Articulate 360 desktop app on your computer to take advantage of this update, and click the Update button next to Storyline 360. You’ll find our step-by-step instructions here.
Please let me know if you need additional help.
That's fixed it, thanks for letting me know.
I have latest version this just started happening again
I would recommend submitting a case since it is working in the latest version
Hello ryanlesperance,
Are you still experiencing this behavior? We've released a new update for Storyline 360 (Update 111) yesterday. I recommend working on the latest version of Storyline 360 to take advantage of the latest features and fixes. Here are the step-by-step instructions for your reference.
If you're still having issues generating closed captions after updating, please let us know in this thread or privately in a support case.
Updated to version a few days ago, to see how the "use AI Assistant to generate/update captions) would work with a Localization project that we are currently working on (English master to 12+ languages).
The project is a fairly simple text & images, with some text-to-speech audio for narration (sometimes several audio clips per slide).
After using the AI generate captions function (using this string for the AI Assistant, e.g.,
"Please update closed captions on all slides with audio automatically in this Storyline file. Please update existing closed captions on audio elements.")...we found that we could no longer adjust the audio clips on the timeline, in terms of where they started & finished, as though they were "locked" (yet they could still be reordered by layer).
Tried lots of workarounds, in the end (as we're on a deadline, obviously) the 'fix' was to revert to version 3.108, which releases/ frees all audio clips so they can be adjusted as normal.
I started to submit (yet another) ticket to Articulate but figured it would be more useful to post in here in case anyone else has the same issue.
To re-iterate, this bug for us was using a Storyline 360 Localization project, with version Build 3.110.36211.0 and the fix was to step back to Build 3.108.36078.0, which was our last "trusted" good version.Lastly, Articulate, please take note to properly test these new features before releasing updates, as buggy AI software has the effect of making the Storyline 360 seem "Alpha-level" in terms of stability. As well as frustrating the user base, these so-called shortcuts have actually meant much more work for us!!
