added .wmv video file to Story, outputs to .mp4

Mar 09, 2016

Hey, new to the product but I like what I see. Right now, I am adding a .wmv file to a Story then outputting to HTML5. When I look at the output, it has converted the video to .mp4

Normally, I would be more than fine with that, but we're hosting the content on a Windows Media Server that is specifically designed to stream .wmv files. If I have the content in .mp4 the server will instead serve the entire file which impacts performance. How can I get it to leave the .wmv format, or how can I replace the .mp4 file with the original .mwv?

5 Replies
Ashley Terwilliger-Pollard

Hi Brian,

Upon publish in Storyline videos are encoded as detailed here.  I'm not able to offer assistance in terms of editing the published output to include the original wmv file, but I know users in the past have used the method that Justin linked to here to replace the video in the published output (this is for Storyline 1, but the same concepts can apply in Storyline 2). 

Brian Brannies

Yeah, I already figured out that I could simply replace the file in the output with a different one as outlined in his tutorial. However, this is only going to work with another .mp4 file. I think what's going on here is that HTML5 supports .mp4 playback in-browser, and not .wmv files. Those will only work with a plug-in like Silverlight or Windows Media Player for IE. So I guess I answered my own question - it's really not possible to do this without some major hacking.

Brian Brannies

My organization primarily uses IE11 which is HTML5 compatible. We also use Chrome 48, also HTML5 compatible. That's exactly why I decided to use Articulate, with its HTML5 output. Flash and Silverlight are really buggy and going away and I want this content to be usable for a few years. The issue for me is the server hosting the content. I'm not sure it's robust enough to handle the loads we will be putting on it with .mp4 videos. I was hoping for a "streaming" solution for mp4 but I'm not sure that even exists. It's not a limitation with Articulate, it's a limitation with HTML5 and my organizations server infrastructure.

Ashley Terwilliger-Pollard

Hi Brian,

Sorry I should have clarified further - IE11 is not one of the browsers that Articulate offers support for in terms of HTML5 output as you'll see documented below:

Flash

Adobe Flash Player 10.3 or later, and one of the following browsers:

  • Windows: Internet Explorer 8 and later, Microsoft Edge (latest version), Google Chrome (latest version), Firefox (latest version)
  • Mac: Safari 7 and later, Google Chrome (latest version)
HTML5
  • Windows: Google Chrome (latest version)
  • Mac: Safari 7 and later, Google Chrome (latest version)
  • Mobile: Safari in Apple iOS 7 and later, Google Chrome (latest version) in Android OS 4.1 and later

  

As for how IE11 states that they support HTML5 output, I have heard from other users here that testing across browser they've found good results with IE11 or Firefox for that matter, so if you're able to properly test and it works well that's great to hear. 

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