My company wants us to indicate the duration for our eLearning courses in out LMS so learners are notified about the amount of time it takes to go through an eLearning course. To help address this need, I wanted to get a total run time for my Storyline files. I wanted to find a way to quickly add up the items listed below (especially items #1 and #2)
1) Total timeline for each slide
2) Total timeline for each question slide
3) total timeline for each layer on #1 and #2
Is there a way to accumulate the items listed above? If not, can code (e.g., javascript) be written to do this?
Or is there some easy manual way of doing this without having to go from slide to slide and manually adding up all the timelines?
Total timeline for each question slide? How can anyone guess how long a user will take to answer a question?
My own personal best practices:
Personally, I would never think of releasing a project without one final run-through AS A USER, to see what they see, to feel what they feel, to find the mistakes and poor design that they will experience. Of course, I may be the only designer in the world that makes mistakes, or gets tunnel vision. While I'm looking for all those other things, it's easy enough to time it.
Timing for each slide and layer? I know that sooner or later, SL, or I, or my computer is going to bargle up a presentation, and I'll be stuck recontructing at least part of it, so as I create, I keep pretty extensive notes. Recording the length of a slide and its layers would be pretty easy.
Most layers and slides that have interactions have pretty short timelines, but are designed to patiently sit and wait for the user to assimilate everything at their own pace. It;s hard to anticipate how long those will last. Naturally, linear, single-pace , non-interactive courses are easier to time.
Michael ... thanks for pointing out the time estimate number that gets calculated when you go to publish. Does anyone know how that number is determined?
It's based on a combination of slide timelines and layer timelines. We're not able to account for the time of a web object video or similar as that's external to Storyline.
Will this timing function every be updated to include the time on Layers? I use the automated voice to estimate the number of minutes that I will have to budget for 3rd party narration.
The overall duration of a Storyline file currently does not include layers, but I appreciate you letting us know you have a need for that. Our product team is always keen to hear about customer needs, so I can certainly pass along your suggestion. And feel free to share any other ideas you have here: Feature Request Form.
I have exciting news to share! We just released another update for Storyline 360. In Update 58, we've included important fixes and new features.
One of the features we've included is:
Create timed interactions and conditional triggers using built-in variables that track the total time a learner spends on a slide, a scene, or an entire course.
To take advantage of this feature, launch the Articulate 360 desktop app on your computer and click the Update button next to Storyline 360. You'll find our step-by-step instructions here.
Please let us know if you have any questions by posting here or by reaching out to our Support Engineers directly.
8 Replies
This may not be accurate enough for your needs, but in the Publish dialog you can see an estimated duration, see here under Step 2.
Total timeline for each question slide? How can anyone guess how long a user will take to answer a question?
My own personal best practices:
Personally, I would never think of releasing a project without one final run-through AS A USER, to see what they see, to feel what they feel, to find the mistakes and poor design that they will experience. Of course, I may be the only designer in the world that makes mistakes, or gets tunnel vision. While I'm looking for all those other things, it's easy enough to time it.
Timing for each slide and layer? I know that sooner or later, SL, or I, or my computer is going to bargle up a presentation, and I'll be stuck recontructing at least part of it, so as I create, I keep pretty extensive notes. Recording the length of a slide and its layers would be pretty easy.
Most layers and slides that have interactions have pretty short timelines, but are designed to patiently sit and wait for the user to assimilate everything at their own pace. It;s hard to anticipate how long those will last. Naturally, linear, single-pace , non-interactive courses are easier to time.
Michael ... thanks for pointing out the time estimate number that gets calculated when you go to publish. Does anyone know how that number is determined?
It's based on a combination of slide timelines and layer timelines. We're not able to account for the time of a web object video or similar as that's external to Storyline.
Ok, here's what I found out from testing some items in SL to systematically determine a estimated duration for learners to complete a module.
1) A few preconditions:
2)Determine the Estimated Module Duration
NOTE:
Will this timing function every be updated to include the time on Layers? I use the automated voice to estimate the number of minutes that I will have to budget for 3rd party narration.
Hi Ari,
The overall duration of a Storyline file currently does not include layers, but I appreciate you letting us know you have a need for that. Our product team is always keen to hear about customer needs, so I can certainly pass along your suggestion. And feel free to share any other ideas you have here: Feature Request Form.
Hi, everyone!
I have exciting news to share!
We just released another update for Storyline 360. In Update 58, we've included important fixes and new features.
One of the features we've included is:
Create timed interactions and conditional triggers using built-in variables that track the total time a learner spends on a slide, a scene, or an entire course.
To take advantage of this feature, launch the Articulate 360 desktop app on your computer and click the Update button next to Storyline 360. You'll find our step-by-step instructions here.
Please let us know if you have any questions by posting here or by reaching out to our Support Engineers directly.