Forum Discussion
Videos not playing in published course. HELP!!
I am working on a course with lots of videos. Originally they were really blurry and so I've been having to use the work around I learned here. //www.screenr.com/NTHH
I published the course last...
Hey folks,
Google no longer allows videos with audio to autoplay in Chrome 66+. As a result, a video on the first slide of a Storyline course might not work.
Dianne--since you're having trouble with an existing project, use this updater tool to fix the project without having to republish it.
We've also added support for Google's new autoplay policy to Storyline 2 (and Storyline 3 and 360) so any new projects you publish with the latest update will work as expected in Google.
Thanks for your response Alyssa. I'm not sure what you mean by "will work as expected in Google". I understand the concept behind what they've done to stop videos auto-playing - but if the Articulate fix is to add a play button that looks like the one above, I think I'll be opting for instructions not to play this in Chrome rather than have learners see this play button, or not have videos at the start of any projects.
I agree with other comments here that this issue exists because of Google changing how Chrome deals with media - I've skimmed through the link you put up Will - there's a lot of people not happy about this, but I'm not sure that things will change from their end.
Hi Dianne,
I believe Alyssa was sharing that the "will work as expected in Google" means that courses you've published with the latest update will follow what you're seeing with the courses modified using the Updater tool.
Since Google has required that a user interact with a site before it starts autoplaying media, that play button is what your learners will see at the start of the course. After a while, learners may stop seeing the play button as Chrome's Media Engagement Index (MEI) learns that they allowed audio to play on previous visits to the same site. When that happens, audio will automatically play as it did in earlier versions of Chrome.
Keep in mind, browsers like Safari have also started to implement similar policies and I expect other browsers to soon follow suit.
