I'm new to creating closed captioning in SL 360. Is it more efficient to:
Create text-to-speech audio within SL.
Export the audio for the entire course into .SRT files
Create professional narration.
Insert audio following this direction "If your caption files have the same names as your media files and are stored in the same folder with the media, they’ll automatically import into Storyline 360 when you import your media."
Do the first two steps create efficiency. Am I missing a step.
1. Text to speech is obviously quicker. I did find in testing it there are certain words you may need to "train" the system to pronounce correctly. Its pretty good though. When it generates the CCing the text blocks may need a little editing.
2. If you're still referring to Text to Speech, exporting the audio to .srt doesn't gain you anything.
3. Professional narration - you can easily take your script and copy and paste the narration into the built-in CC editor. Its actually pretty efficient to do it this way.
4. We use to create all our CCing files this way. It works fine but is time consuming. I feel its more efficient to insert your audio file and then simply copy/paste your text into Storyline's editor directly.
So, my two cents - Record your audio either professionally or in-house and then use the narration script to copy the text lines and paste it into the CCing editor caption blocks. We just did 6 courses with full narration and I can't imagine going back to generating it another way.
This is very interesting. Step four especially, just a quick clarification. If, after I have recorded my human voice over, I give the audio files the same names as the audio files for the TTS they will automatically be "seen" by Storyline and used? Am I getting this correct?
If so, that really is quite cool. I can make good use of this.
4 Replies
1. Text to speech is obviously quicker. I did find in testing it there are certain words you may need to "train" the system to pronounce correctly. Its pretty good though. When it generates the CCing the text blocks may need a little editing.
2. If you're still referring to Text to Speech, exporting the audio to .srt doesn't gain you anything.
3. Professional narration - you can easily take your script and copy and paste the narration into the built-in CC editor. Its actually pretty efficient to do it this way.
4. We use to create all our CCing files this way. It works fine but is time consuming. I feel its more efficient to insert your audio file and then simply copy/paste your text into Storyline's editor directly.
So, my two cents - Record your audio either professionally or in-house and then use the narration script to copy the text lines and paste it into the CCing editor caption blocks. We just did 6 courses with full narration and I can't imagine going back to generating it another way.
Thank you Bob! I appreciate your thorough response.
This is very interesting. Step four especially, just a quick clarification. If, after I have recorded my human voice over, I give the audio files the same names as the audio files for the TTS they will automatically be "seen" by Storyline and used? Am I getting this correct?
If so, that really is quite cool. I can make good use of this.
Hi there, John. Here's our user guide information about importing closed caption files with your media in Storyline. You'll see that you either can import captions simultaneously with your media, or you can import captions separately.
This discussion is closed. You can start a new discussion or contact Articulate Support.