I would like to know how to edit the published files so that they support WMV files. I'm having a hard time trying to figure out where they are being called from, so if anyone has any tips or knows how to do this, I would be very grateful!
Why are you looking to switch MP4 with WMV? You're likely to find better browser playback support for MP4 and none of the built-in events will fire (if you're able to get swapped videos to work) with WMV.
Why are you looking to switch MP4 with WMV? You're likely to find better browser playback support for MP4 and none of the built-in events will fire (if you're able to get swapped videos to work) with WMV.
Well, our client wants it to be WMV. I do not know why they want it like that, as it would indeed be rather inconvenient with browser playback and such. To be frank, I don't really care for their reasoning. I'm only told to find a way to do it.
Oh, but I am not the one who negotiates with the clients! Hah, god no. That would be hilarious. No, I was only told to find a way if it's possible, and I have found out that it isn't. I thank you for your time.
Yep. Best answer is "you can't". You may, however, import WMV's into Storyline. The only video formats exported by the tool on publish are FLV and MP4. FLV is normally only retained if you add an alpha channel and these are only viewable in the Flash version of the published output.
WMV's are fantastic for consistent playback inside of a PowerPoint presentation. But the format isn't as popular or universally supported as h.264 formats. MP4 has the best support natively in most modern browsers. And Flash based players provide a nearly universal fallback.
Hard to tell what the motivations for using WMV are. Did they offer additional details as to why? Could help to know the motivation behind it to craft a response Some folks get attached to file formats as a habit. I've been there.
9 Replies
Woop, found something interesting in the player_compiled.js! I found in there the following line of code:
case "flv":case "mov":case "mp4":case "avi":e="video";
Could this be what it supports?
Furthermore, I found the following in data.js:
|video_5okoprwuqEe_26_160_960x540|
Pretty interesting, since this is how the videos are named.
Hi Hans,
Why are you looking to switch MP4 with WMV? You're likely to find better browser playback support for MP4 and none of the built-in events will fire (if you're able to get swapped videos to work) with WMV.
+2
Well, our client wants it to be WMV. I do not know why they want it like that, as it would indeed be rather inconvenient with browser playback and such. To be frank, I don't really care for their reasoning. I'm only told to find a way to do it.
Hans...
With due respect, isn't it our job to care, advise and negotiate change with clients?
Perhaps the answer is "You cannot do this - it's not how Storyline was designed to work", but I suggest you log a support call to confirm this.
Oh, but I am not the one who negotiates with the clients! Hah, god no. That would be hilarious. No, I was only told to find a way if it's possible, and I have found out that it isn't. I thank you for your time.
Hi Hans -
Yep. Best answer is "you can't". You may, however, import WMV's into Storyline. The only video formats exported by the tool on publish are FLV and MP4. FLV is normally only retained if you add an alpha channel and these are only viewable in the Flash version of the published output.
WMV's are fantastic for consistent playback inside of a PowerPoint presentation. But the format isn't as popular or universally supported as h.264 formats. MP4 has the best support natively in most modern browsers. And Flash based players provide a nearly universal fallback.
Hard to tell what the motivations for using WMV are. Did they offer additional details as to why? Could help to know the motivation behind it to craft a response
Some folks get attached to file formats as a habit. I've been there.
I see, thank you. I sadly do not know their motivations for wanting it to be WMV. I suppose it is indeed, as you say, a force of habit.
This discussion is closed. You can start a new discussion or contact Articulate Support.