I am creating an eLearning course with Spanish subtitles. I have the Closed Captioning button enabled in my Skin Editor, but I would like it if the user did not have to click the CC button to turn closed captions on. Is there a way to accomplish this with advanced actions? Thanks so much.
There is a system variable cpCmndCC, if you assign the value 1 CC will be shown. You can create a short advanced action to be triggered on entering the first slide with those statements:
However, to be safe, it is better to insert a very short first slide and execute this action on entering the second slide to give CP the time to trigger it.
One more quick question if you don't mind, I noticed that when I previewed my course in CP (and even locally previewed the published version) the Captions were in sync with my slide audio. However, I just uploaded the course to the web for my client's review and noticed that on the first slide with Closed Captions (really the third slide in the project) the Captions and audio are out of sync by a couple seconds. The Captions and audio are back in sync again when the next slide starts, and if you click the back button to return to the slide that was out of sync, it is now synced up. I tried removing the advanced action, and turning CC on manually, but I noticed that the same out of sync issue occured of the first slide that the Captions are enabled. Any idea what might be causing this?
The synchronisation issue is likely because Captivate was still getting things sorted out at runtime by the time you had specified the voiceover audio should start.
It's generally regarded as good practice to NOT put voiceover that requires synchronisation on the very first slide. I usually have an initial blank slide of a second or two duration to allow Captivate to get set, then I have a title slide with a little intro music that goes for about 7-9 seconds where I display info about the name of the course, department, module, duration etc. Then on the third slide I start my voiceover and CC text. This seems to work well and the users are getting all the info they need without synchronisation issues.
I actually do have two slides that come before my slide that triggers Closed Captions; the first slide plays for 10 seconds and the second slide play for 30 seconds. Then I trigger Closed Captioning on the third slide of my project, but this slide is the only slide that is not syncronized (the slides that follow the initial slide that triggers CC are all in sync). Any other ideas? Thanks so much,
Is there any audio (e.g. an intro music clip) on the slides before your CC slide? Try adding a short piece of music (no issue with synching CC) and see if that helps. Perhaps the synch issue will only crop up on the first slide to have audio at all. But if that slide is just music, your users will be none the wiser.
Captivate comes with a small number of intro clips in the Gallery > Sounds folder. Try the Loop Acoustic Mellow MP3 clip.
I just tested the project with audio attached to the first 2 slides and it made no difference. I think I have figured out what is causing the issue though. I am using rather large video files in my project and using edit video timing to distribute portions of the video files across multiple slides. The slide that triggers Closed Captions is also the first slide in the project with video so there is a short loading time while CP loads the video onto the slide. The Captions are not subject to this load time which causing the out of sync issue. In the slides that follow, the video has already been loaded so there are no sync issues. I tried to compensate for the loading delay by moving my CC markers ahead by several seconds but this causes the last Caption on the slide to be cut off; also when the user clicks the back button and returns to that slide (the video is now loaded so there is no delay) the Captions are out of sync due to the fact that I delayed the markers. I am guessing there isn't much I can do about this since there is no way to avoid the video load time, can you think of another way I might be able to "get around" this issue?