New Storyline Feature: Closed Captions

Hey folks,

We just released a new feature for Storyline 360: Closed Captions! This is one of our most requested features, and allows you to add closed captions to both video and audio (narration).

Storyline supports the standard Closed Caption formats in use today: .srt, .vtt, .sbv and .sub. These are super easy to create with a range of third party tools such as YouTube (we’ll add a simple caption editor in a future update, coming soon).

You can specify a custom font in player properties, and choose whether to use a built in player control or roll your own button with the new Player.DisplayCaptions trigger. As you’d expect, everything works seamlessly across desktop, tablets and phones.

Check out Arlyn’s video for more info:

And here's the full Closed Captions Documentation.

To get started, just update your 360 Desktop App and then update Storyline 360.

For an overview of everything in the March ’17 update, see our What’s New Page



156 Replies
Steve Covello

It would be appreciated if Articulate would explain WHY this feature has been designed not to be editable. I can only assume that it has something to with providing a caption system that is 508 compliant that cannot be changed so as to become NOT compliant.

I understand this (if true), but the current design imposes upon a LOT of screen real estate to the extent that there is often an awkward imbalance in the content design to accommodate the possibility of captions being enabled. Remember that we are not making talking head videos here -- we are designing instruction.

If, however, you designed a player where the captions appeared below the designer's designated dimensions, this would alleviate a lot of headaches. (FYI, this is a feature built into the Kaltura player system -- you can choose to place the captions as an overlay or below the the normal screen dimensions to preserve the original video's integrity).

mat corrado
Steve Covello

I have replied to this issue in another thread. Please review. This is a flawed design. I urge your design team to come up with a better way to do this.

Hi Steve,

SL360's built-in caption editor feature is in the works.  Right now, you are correct - there are limited closed caption features available.  Rest assured, all concerns you have mentioned are on our radar, and will be implemented in updates.

Amanda Allen

I definitely appreciate the added feature of a CC button in the playbar. However, the process of uploading audio files to a third-party site, generating CC files, downloading them, and then importing them into a SL project seems excessive and cumbersome. I typically have ~50 audio files per project (which I already have transcripts for in Word format) and if I want to use this feature it will add significant time to my workload. I wonder why Articulate can't just convert Notes to CC like Adobe Captivate does?

Steve Covello

Amanda - I agree. Since Articulate is on the Windows system, why can't it do speech-to-text using Window's native capabilities like Camtasia (PC)? I did a test using an audio file in Camtasia (PC only - speech-to-text is not available in the Mac version) , generated the speech-to-text, exported the SRT file, and then uploaded it into SL2. Worked perfectly fine and was done in about 5 minutes (not including corrections). If you don't have Camtasia then you'd have to do a hack workaround.

Alexander Salas

Hey guys, this is a great feature but is there a reason by the captions are eating away 10% of the slide?  There are also issues where single quotes are not picked up, I think this is because of ADA restrictions. I would recommend adding a feature like Camtasia has to remove ADA restrictions on\off. This would allow designers to use captions for purposes other than accessibility like English as a second language, etc.  There's great potential here and I have placed a feature request.

Ashley Terwilliger

Oh! One other thing Alexander - I think there is a way around your single quote issue.

First, open your .srt file in a source code editor, such as Notepad++.   Change to encode the file as UTF-8.  note, if you have opened and saved the file in a text editor such as Wordpad, the default encoding is ANSI.

Next, make sure to save the file as with the 'save as type' designation All types (*.*) and not Normal Text file (*.txt).

Finally, replace the .srt file in your .story file with your updated .srt file and you should be good to go.

Hope that helps! 

Cynthia Paré

Hi everyone!
Am I the only one experiencing problems with the font size of my captions. Captions were way too small at first, so I put 175%. Everything looks good in the preview. But once published, both web and LMS, the font size stays very small. 

I will attach 2 PNG for comparison purpose (published + preview).

Am I the only or did anyone find a solution to it?

I am using Storyline 360.

Thank you!

Cynthia Paré

With further testing, I figured out that the font size problem is with the SWF output... :/ 
The preview in Storyline seems to be the HTML5 version, which is also find, even in the published version.

Why is the flash version not taking into consideration the pourcentage I set the player to... 

Thanks in advance for the help!