SCORM and Tin Can behaving differently

Jul 10, 2017

Hi everyone.

I have a project that includes video.  When I preview the story everything works fine and when I publish it as a Tin Can and deploy it using my LMS it still works fine.

The problem is that I am now going to need to use the project as "published for the web" and the issue is that the videos in the file no longer work correctly.   Basically the video runs automatically instead of being in a paused state awaiting the user to click on a button to start it.

So

Tin Can = Video Works Correctly

SCORM = Video Does Not Work Correctly

Published For Web = Video Does Not Work Correctly

Does anyone have any ideas as to why this should be?

Thanks in advance

Kenny 

 

4 Replies
Kenneth Park

Hi Alyssa

Thanks for your reply.

I've attached one of the files in question.  When you preview the story you'll see that it all behaves correctly (basically after the user answer a question they have to click on a button to continue viewing the video).  I saved this as a Tin Can object and it works in my compliant LMS - and that's all great.

However I'm also going to need to make this material outwith an LMS and when I publish it as output for the web and host it on Amazon you'll see that the video now advances automatically without the user clicking on the button see

http://s3.amazonaws.com/SharedCourses/The%20telephone%20interview/The%20telephone%20interview%20-%20Storyline%20output/story_html5.html 

I have around 20 different .story files where this is a problem so any help you could give me would be greatly appreciated.

Cheers

Kenny

 

Alyssa Gomez

Hi there Kenny,

I'm seeing the same thing you're seeing. It looks like the video automatically plays in HTML5 (without first clicking the button), but it works as it should in Flash. 

I'd like to have our Support Engineers take a closer look at this, so I'm going to submit a case on your behalf. Someone from the team will reach out to you shortly! 

This discussion is closed. You can start a new discussion or contact Articulate Support.