WebM Video Format Workaround in Storyline 360?

Figured it out. After converting the output videos to webm format, the video file extension and file type in the data.js file needs to be changed to webm, then mp4 needs to be changed to webm in the app.min.js file as well.

It would be nice to be able to add a webm file to Storyline 360 without having to change code.

Quick bump. Happy Monday, everyone!

Ah, glad you were able to get that figured out Ben and I appreciate you popping back in to share the solution with the community.

Welcome to E-Learning Heroes by the way :)

Hi,

I have the exact same problem as Ben in a CBT course with lots of videos that are updated regularly, so Ben's workaround is not really a viable solution. Any chance that Storyline will support WebM files natively? Now that the HTML5 engine has been significantly updated and works very well, it would be a natural next step to support WebM.

Hello Tom!

Great question, but not one I know the answer to. I'm not familiar with WebM, but sounds like you may be.

I do know that getting that submitted to our team as a feature request is a good start :) Be sure to share the need and benefit so that we can fully understand the request.

Thanks so much!

Hi Bridgitte - Ben's post was a bit dated. You are certainly welcome to reach out to the user directly via the 'Contact Me' option on the user profile if you do not hear back soon.

Hello

I have exported project of Articulate storyline ​​by Web Publishing. All the videos are exported in MP4 format. I converted my project by HTML executable which only provides support for open-source audio and video codecs: WEBM, WEBA, OGG. The Chromium build is not enabled for the MP4 video format (H264 codec), as this format requires licensing.

 Please help how can I web publish with video file format WEBM, WEBA or OGG.

5 years after the initial discussion this has not been adressed, and I yet again find myself really needing support in Storyline for formats natively supported by the Chromium engine.

The workaround posted by Ben still works with a few changes. You have to do the following (for webm support, should work for others as well):

1. Convert the mp4 videos to webm (obviously)
2. Add webm in the slides.min.js file
   • Change video:"flv mov mp4 avi" to video:"flv mov mp4 avi webm"
3. Change the file extension for each video in the data.js file. You can also change the videoType and fileSize to match, but the videos will play without doing this
   • Change {"kind":"asset","id":38,"videoType":"mp4","width":396,"height":428,"duration":6300,"framerate":30,"fileSize":199892,"asversion":"3","url":"story_content/video_name.mp4"}
     to {"kind":"asset","id":38,"videoType":"webm","width":396,"height":428,"duration":6300,"framerate":30,"fileSize":95308,"asversion":"3","url":"story_content/video_name.webm"}

I tried posting a feature request to get native support for webm, but got a "The page you're looking for can't be found" error after submitting, so I have no idea if it went through.

Hi Tom,

Thank you for reaching out and sharing your updated workaround here for the community!

I'm sorry to hear that you received an error message after submitting your feature request. I wanted to share the feature request link with you here so you have easy access to it!

Here is our process when handling feature requests. First, we check if there’s already a way to do what you’re asking. If there is, we’ll let you know how. If not, we determine will this feature meaningfully improve the experience of working with our software? Will it benefit a majority of users? If the answer is “yes!”, we bring the request to our product development team.

The development team evaluates feature requests alongside their queue of bug fixes, new features already on the roadmap, and other projects. If a new feature makes it onto the roadmap, our team tests it, and we share the news when it’s ready.