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

Thanks,

Simon

156 Replies
Rob Skeet

I was about to send a nasty comment about the closed caption feature not showing special characters in French and Spanish then I read Ashley's note about saving the file as UTF-8 and it worked.

Now I have to resave 200 files and reapply them to the 200 audio files in 2 languages.

first world problems!

Thanks Ashley!

Leslie McKerchie

Great news!  Another update for Articulate 360 is now available.  It includes a few important fixes and new features that you'll see in the release notes here.  

The item you may be interested in is:  

Create and edit closed captions right in Storyline 360. Fine-tune imported captions or quickly add new ones with the help of caption placeholders that are already synced with your audio and video content.

Launch the Articulate 360 desktop app on your computer and click the Update button for each application. Details here.

Please let us know if you have any questions, either here or by reaching out to our Support Engineers directly.

Janet Chafey

The addition of the closed caption editor is a huge time-saver! I've successfully added cc to audio and videos - this is so much faster than the way we were doing it with Storyline 2.

I have noticed that if an apostrophe is used in the text and I preview that slide, everything is fine. However, once I publish, the apostrophe is turned into ' 

Ex. Let's becomes Let's

At first I though it was caused by my copying the text from a Word doc and pasting it into the editor, but it consistently happens when I type directly into the editor instead of pasting. The preview is fine, but once published all my apostrophes turn into 's! 

My workaround is to export the closed captions from Storyline, open in Notepad, correct the text, then resave with UTF-8 encoding. But this is an extra step.

Any suggestions?

Janet Chafey

Hi Magnus, I created a new file, added audio and cc then published. The problem is still there. I'm attaching the source file and the published version.

I viewed the published (SCORM 2004) project with IE, Firefox and Chrome. Though the issue with the apostrophes was visible in IE and Firefox, Chrome show the apostrophe correctly!?

Thank you!

Cynthia Paré

It's probably the same issue as what we discussed on this other thread : https://community.articulate.com/discussions/articulate-storyline/closed-captions-flash-bug

All special french characters won't show corretly in the Closed captions on the Flash output when we are using the Storyline Closed Caption editor... But when we copy/paste our text directly in a .SRT file (UTF-8) then import it in the Storyline project, we don't have this issue. 

I'm wondering if this could be the encoding of what the Closed caption editor is creating that might be incorrect...