Overloading

I'm creating a species identification course that has about 100 species each with at least 4 slides that include video, photos, multiple layers that are triggered depending on the states of buttons and photos, and several links per slide pointing to other similar species.  It currently has 162 slides and I anticipate reaching about 400-450 when all is said and done.  I have seen a considerable increase in the time it takes for the preview to load and I'm starting to wonder if Articulate Storyline is the right tool for the job.  I love the software and it has a ton of great uses in our program already and many more that we haven't put together yet, but before putting a couple hundred additional hours into this particular identification course, I'd like to know if it's going to be able to handle the fully complete version.  The other option would be to create a website with everything and although I'm much more familiar with Articulate, I need to know if I'm wasting my time.  If Articulate is likely to bog down more as I go or if it will freeze being overwhelmed with 450 slides of photos, videos, layers, and slide-jumping triggers, then I need to know so I can find another alternative for this particular course.  

If it helps to answer this question, I'm using an Intel i5 2.7GHz processor with 8GB of RAM and plenty of space on the hard drive.

3 Replies
Stephanie Harnett

Hi Robbie. I can relate to what you are experiencing. I have seen Storyline and Studio become overloaded as projects increase in size. I too love the tool and hesitate to go for web only primarily because of the interactivity I usually require. So as a habit, I compress images and audio as much as I can before importing into Storyline so I start with smaller file sizes. Even though Storyline compresses at publish making smaller sizes at the user end, it can make for bloated production file sizes. I will also split a course into multiple courses and use a central menu. I did this with a large project that contains hundreds of video clips. Just too much to work with in a single Storyline file. Re-booting and flushing out memory often can also speed up previewing as Articulate products tend to consume more memory the longer you are working with them in a single session.

Overall, if your project doesn't require complex interactivity, you might want to consider a WordPress site as galleries and other widgets are easy to add in, design choices are abundant and administration is a breeze.

Robbie Christian

Stephanie, as a follow-up, I ended up making the whole thing without videos and then putting all the videos in as the final step before publishing.  When I originally had them in, each of them was trimmed for length.  When I brought them back, I didn't trim any of them, I had my wireless turned off, and all other programs were closed and it seemed to go much smoother.  Sure it took a while, but not as long as I thought it would have taken given its earlier pace with only a small portion of the videos included.  I'm not sure which of my methods made the biggest difference but doing all of those things certainly seemed to help.