Sweet 16 or so things I need to remember about Articulate Storyline

Another messy blog post that’s all about things I want/need to remember…

1) It caches like STEEL TRAP. If you make changes, you need to click Preview to see them. Just changing, saving and hitting play will not always show your new edits.
2) To bring in bullet points one by one, you need to choose an animation type in the animation tab – then select – by first level paragraph.
3) Video embedded in the slides will not provide the option to expand to full screen. If you have small details, you will need to upload your video and may be able to embed the player – YouTube works a treat. I was unable to do so using our proprietary media server Viostream as its player requires javascript be embedded in the header tags of page templates. Just trying to trigger Javascript didn’t work.
4) CTL Z doesn’t work as expected. I found I bounced back to previous slides. Not sure why this happens, but don’t assume it will work as expected.
5) Don’t assume the sound quality you hear as you edit or preview is the final version. It is a compressed preview version – you need to publish to hear the full quality.
6) Javascript doesn’t work in Preview mode. Test slides with Javascript by copying them into their own project and publishing.
7) Set text boxes to “Do Not Autofit” – this sometimes doesn’t seem to stick between computers.
8) If using a line in mic for screen captures,¬†go to screen capture mode, Turn off mic (line in won’t come up as an option anyway, I disabled my mic in Windows 7 just to be sure), select your line in as SPEAKER.
9) When timing several objects on screen to audio, where possible, record audio in chunks and match up to events.
10) Watch for events that aren’t timed to last until end of screen if you want them there. Some are set to appear for a set length of time and won’t allow you to adjust slide duration. Others cut out just before the end and disappear.
11) When shortening the length of a slide, if an event has a fixed time it will blow past its cue point so that it can stay on for its set length of time.
12) Set up a name for the variable you want to change that you’ll remember – the more generic, the more margin for error. Ensure you’re changing a T/F value or text as relevant.
13) Trigger order matters! Where possible, find a template that does what you want and backward engineer it. There are loads out there programmed by clever people.
14) To pull out MP4 vidoes when using Storyline for screen captures, you should set up a New Project first, just for your screen capture. Once a screen capture is complete, you’ll insert it into a slide – pick the single slide option – then need to go back up to screen capture, act like you want to insert it again, but this time right click on the video you see and save it as MP4.
15) If you plan on publishing Storyline as a SCORM package in an LMS, you will need to program the Next key on your last slide to Exit.
16) If you plan on publishing Storyline as a SCORM package in an LMS,the end message “The content has ended. You may close this window” isn’t useful for Moodle courses. To change it, publish it but DON’T EXIT THE PROJECT and DON’T ZIP. Go to the folder where the output was published, open the named folder, go to te LMS folder, right click on the Goodbye.html file and open in your fav editor (I use Notepad ++). Edit the message to something like “To return to the main course page, click on the course name in the horizontal text navigation at the top left of this page.” Save the file and close it. Go back to the Articulate project and THEN zip the project using the options in the publishing window there. Then, upload the zip to Moodle. You could of course get fancy and program a button or link to link directly back to the course page…