Saving Progress of Video when Exiting Course

Feb 03, 2020

Hello, 

I am having a difficulty in saving video progress within a course in Articulate Storyline 360. I have inserted a video that is 12 minutes in length, so would like to present an option to users to exit out of the course and be able to resume the video from wherever they stopped. For example, the user exits out of the course at 6 minutes, comes back and can pick up at the 6 minute mark to complete the 12 minute video. Currently the course will resume at the proper slide, but the video starts back at the beginning.

A few things to consider:

  1. We have to have the seek bar set to "Allow drag after completion" as it is a required course and users must view the full video prior to going to the next slide.
  2. The video is currently set up to automatically play when the slide appears as to sync with the timeline. 
  3. The show video controls are set to none so the user cannot skip around the video.

I'm just stumped. Essentially - is there a way to save a progress of an mp4 file so that when the user comes back to resume the course the video would be able to pick up where it stopped? 

Any help would be appreciated, 

Alyssa 

16 Replies
Ren Gomez

Hi Alyssa,

Happy to help clarify! When a learner exits a slide that has a video on it, the default resume behavior is that the slide will reset to the beginning of the video. The only way to save video progress is by going to the next slide. 

I know you don't want to force your learners to completely restart the video when they return to the lesson, so I found a workaround that should help! While a bit older, this tutorial may point you in the right direction!

David Hansen

I really wish Articulate would address this problem.   We often have long video's incorporated into our courses and regularly have customer's that complain about having to re-watch the video upon resuming.

We've learned to try to design the courses to have smaller video segments, but this is not always possible.

The work-around of having a Save button point to a save slide is also not very practical when watching a video and then suddenly having to exit (either forced or not).   In our in-house developed SCORM player, we save the seek point into suspend_data every 1 minute, as well as the precise seek point when doing a clean exit.   I really just don't understand why Articulate can't implement a similar approach of saving a slide's current state every minute or on a clean exit.  They currently are sending session time updates every minute.   Most LMS SCORM interfaces (aka Rustici) also buffer the SCORM data on the client side of the SCORM API to minimize network traffic, so any excuse of this causing additional network overhead seems moot.

Pete Lewis

I've had this workaround in place for a series of several dozen video-based trainings for almost a year. It's not the greatest, but it is functional (when people pay attention and don't just click the course window closed.)

I now have an issue where this workaround does not work. Clicking on the on-screen button to jump to my "Your Progress has been Saved" slide only half-loads the slide (the player settings change) and no progress is saved. It is impacting new projects and projects which I published last year.  

I worked with my team internally and we were able to determine that it is related to this type of error: https://community.articulate.com/discussions/articulate-storyline/articulate-could-not-fi[…]e-and-articulate-actionator-exejavascript-is-not-defined 

Thank you in advance - I'm happy to send packages or links to these in Articulate Review. 

(EDIT: I was never able to isolate what the specific issue was, but I was able to publish functioning packages after rolling back to v3.46.23620.0 - I will submit a bug report). 

Lisa Falanga

A year later and this is still a very much needed feature.  I have tried jumping to another slide following the instructions in this thread to no avail.  I assume I am missing a command but just can't figure it out.  Very frustrating!  Beginning to wonder if Lectora offers this feature and maybe switching over to them.

Maria Costa-Stienstra

Hi, Lisa.

Thank you for reaching out!

While not currently a feature in Storyline, we have a feature request logged for the ability to resume video after exiting course.

I've added this discussion to the report, and we'll come back to update you if I have any news to share or if this request makes it to our feature roadmap. 

In the meantime, if you can share your .story file, I'm happy to take a look at why the workaround is not working for you. 

Pete Lewis

If there is a feature request for this to be a 'built-in' feature, I will add my name to the list as well! 

To update on my post from three years ago. The issue was related to a corrupted font, though the support staff and I were perplexed as to why the issue disappeared when I rolled back my version of Storyline. So the workaround I was using (to create a "Your progress has been saved" slide, and on-screen buttons to go to and from that slide) was back to working in published output once I dealt with that.

I have 176 courses loaded using this workaround and those courses have been completed almost 5300 times. Considering that it relies on end users to click somewhere other than an "X" when they want to exit, the fact that I've only had one user issue that was related to the specific wording on the button itself makes me feel pretty confident.

(I do want to note that I do not have video controls turned on for these courses. The video files are inserted into the slides and the main timeline runs the show.)

In the last week or so, I've been playing with dialog layers. I ran some quick tests to see if they would also save video progress and triggering the dialog layer (with default settings) works enough like a slide state change that the progress/bookmarking data captures it for the LMS. Since dialog layers can be designed and managed within slide masters, there should be some extra versatility when it comes to templating this mechanism across slides and across courses. 

As long as my testing keeps going as it has been, we've got two workarounds for this now!