We currently have 36 modules we created and we embedded the mp4 video the issue we have is the end user can go in and figure out a way to download our video. DOes ARticulate have a way to protect that? or a way to start downloading the video once the modules starts. I saw a player called http://www.jwplayer.com/features/ and it takes the dynamic video HLS, HDS format does articulate have that can the player be changed? I don't want the end user to be able to download that video via the source code of the hidden URL file. Some one please help?
The JWPlayer looks nice, I like the skinnable player! With a player like this you may be able to prevent someone from downloading your videos, but that doesn't mean they are 'save'. I found a video on http://www.jwplayer.com, and while I couldn't DOWNLOAD it directly, I simply recorded it. And voila, see here. A user determined to get your content will likely get to it, in one form or another, that's the nature of web-based content.
As Michael mentioned there isn't a way to ensure users don't download or record your content, especially given the prevalence of smartphones which can record just about anything. Articulate doesn't offer a way to encrypt content either, but you may want to check in with your LMS or hosting site to see if they have any options you could investigate.
This option required us to do a little bit more work, but ultimately gave us the control we needed over the user's playback experience.
To pull this option off, you need to find an external video player. We used JWPlayer, which used to be free, but now requires payment. The player is key because it is built with the intelligence to look at a user's environment and then deliver the proper controls every time. If you are using Safari, Chrome, IE, etc, you will get a near consistent experience across platforms.
After identifying a player, you need a HTML page to combine the player with the video that you are going to playback. Usually this is as simple as copy/pasting code into a blank HTML page, pointing it to the video, and testing.
The Storyline aspect is simple, just add a WebObject to your slide and paste the URL to the HTML page.
What made this option less ideal than the option above is that I not only have to create this HTML page, but I also have to add it to Storyline, which creates an extra step. In the end, we decided that this was a trade-off we were willing to accept for the constant playback we gained.
We are still having issues with IE and playback, but that is a JWPlayer issue. The other issue that we are still working around is that when the video renders in IE (inside Storyline) scroll bars appear. I understand that you should be able to place some CSS style on the page so that this doesn't happen, but every attempt to fix it has not worked. We remain resolute.
3 Replies
The JWPlayer looks nice, I like the skinnable player! With a player like this you may be able to prevent someone from downloading your videos, but that doesn't mean they are 'save'. I found a video on http://www.jwplayer.com, and while I couldn't DOWNLOAD it directly, I simply recorded it. And voila, see here. A user determined to get your content will likely get to it, in one form or another, that's the nature of web-based content.
Hi Freddie,
As Michael mentioned there isn't a way to ensure users don't download or record your content, especially given the prevalence of smartphones which can record just about anything. Articulate doesn't offer a way to encrypt content either, but you may want to check in with your LMS or hosting site to see if they have any options you could investigate.
I spoke with Articulate Tech support today and they sent me this info from a forum:
http://community.articulate.com/forums/p/25925/156468.aspx
OPTION : Web Object
We are still having issues with IE and playback, but that is a JWPlayer issue. The other issue that we are still working around is that when the video renders in IE (inside Storyline) scroll bars appear. I understand that you should be able to place some CSS style on the page so that this doesn't happen, but every attempt to fix it has not worked. We remain resolute.
This discussion is closed. You can start a new discussion or contact Articulate Support.