Imbedding WISTIA hosted videos

I have video-intensive course for pump testing with our company.  The first draft 1s 1.4 gigabytes unpublished.


1) LOCAL DRIVE SPACE SHOULD BE IRRELEVANT, but isn't - Our network is HUGE.  My desktop is tiny.   We do all of our content creation on the the network, and publish to our Intranet and LMS from there.

When I have less than 1.4gig available on my desktop (C:) (which is frequently), this particular project won't seem to save on the NETWORK (H:).   This is a dangerous reality for me, on this one project.   No other course has come close to this level of videography.

How to get Storyline to not take the local C: drive into consideration when saving files to H:?




Our company has WISTIA for posting video-footage.  So I uploaded several of the videos from this course to there, then made a version of the project that calls those external videos into slides, it seems to be working.   The problem this introduces is that the user seems to have to specifically START the video on each slide.

This is bad since I would need to use timeline triggers to move from one slide/layer to the next, and the interactive controls and clickables inside storyline need to appear at the right moments during each clip.

In this example, after you select the DVSERVIES - 325 and below, the next slide does not start right away, and for every second the user delays, we lose that much of the video at the end since the slides auto-progress to next slide.   (this is just the first couple of slides in a lengthy video)

How do we get WISTIA slides to start immediately? Or how can I properly advance to the next slide when the WISTIA video finally concludes based on the random time the user clicks on it?   Either solution is fine...



The WISTIA approach seems awesome, the Storyline file goes from 1.4 gigs to 4megs.

10 Replies
Crystal Horn

Hi there, Jerry.  Sounds like you've definitely got a media-rich course!

We strongly recommend saving and publishing your files locally to your C: drive before copying them up to a network drive.  I understand your process is a bit different, though, and that a course of that size is problematic on your hard drive.  I'd like to consult with my team about which drives are reference when you save a project and revisit that piece.

The other issue you seem to be facing is that when you insert a video from a website, it is not synced to the timeline of your slide.  Without being able to guarantee the loading time of an embedded object, it sounds like you're open to having the user initiate the video playback, and you'll time the appearance of other slide objects from there.

Storyline won't know when the Wistia video will be complete, so getting the slide to advance automatically when an externally hosted video ends will be practically impossible.  Is it acceptable to give your learner control over advancing to the next slide, so that each segment of this video-rich course can stay in sync?

Jerry Beaucaire

Yes, but that would eliminate the feeling of watching a lengthy video which is actually "pieces" being linked together based on the clickables in the first scene.

Also, we don't want users just click-skipping the scenes, so don't even have the NEXT option available currently.

Hmm, I found this, which is javascript, and it looks like it should work to capture the "end" of a Wistia video: 

But that script isn't doing anything for me, I'll respond in that thread as well.

Jerry Beaucaire

Well, I tweaked it one more time to take out some extra stuff the Storyline seemed to have added in to make it look exactly like your original code above, and now it IS working to advance to the next slide at the end of the WISTIA imbedded videos.

<iframe src="" title="Wistia video player" allowtransparency="true" frameborder="0" scrolling="no" class="wistia_embed" name="wistia_embed" width="1280" height="720"></iframe>
<script src=""></script>

<script type="text/javascript">
wistiaEmbeds.onFind(function(video) {
video.bind("end", function() {
var player = parent.GetPlayer();
return this.unbind;
So, awesome!

Now, if I can just find a way to get each of the WISTIA video snippets to START automatically at the beginning of each slide, we're in business.

As you can see in the REVIEW link above, the first slide does start on it's own (with no sound) but all other slides require a click to start them.

Jerry Beaucaire

OK, so it appears that CHROME is the culprit for the imbedded videos not auto-starting on each slide, in IE they auto-start just fine.   *sigh*

So close, and always one more thing.

Is there a javascript solution for detecting that an imbedded object is fully loaded and force starting it?

Crystal Horn

Thanks for the updates, Jerry!  That'll be so helpful for anyone else who sees this discussion. 

I checked with my team about the saving to the H: drive issue you were experiencing when your hard drive was low on space.  Without seeing the specifics of your system or network, there maybe be some network latency that is causing issues with saving.  If possible, you may want to temporarily "offload" some of the C: drive contents to your network so you can save this project to the C: drive first and feel confident that your edits are preserved.

As for the JavaScript, I'll defer to the community for expert advice!  We don't provide support for JS coding beyond these best practices.

Jerry Beaucaire

The hard drive on my desktop is only 220gig, the day they gave it to me it only had 40gig free, before I installed my production softwares including Camtasia and Articulate.   This unit is always hovering in the 5 gig free area, I store no assets locally, all network.

It is not network latency.  Storyline is doing something in preparation for saving that seems to task the same amount of local hard drive space during the process, then frees most of it back up again.   I opened a local folder window and watched the C: free space as I was saving my  1.4gig project on the network H: drive, and it went down...down...down until the save was complete, then most of the way back up.

So Storyline needs an equal amount of free space on the root drive and the target save drive, so it seems.   :(

Ashley Terwilliger-Pollard

Hi Jerry, 

It sounds like the data processing and space you're seeing change is connected to the temporary files and the background saving Storyline does incase there is a crash or something else that could cause you to lose your files.

I do want to have our team take a look at what's going on, so I opened a case on your behalf. You'll hear from our team shortly. 

Lauren Connelly

Hi Jerry!

We still stand behind saving locally. If our team decides on a different approach, we'll keep you posted in this discussion. 

Also, I wanted to say thank you for all you do in this community! You're always sharing new ideas and guiding others to create fantastic courses. Your time and support don't go unnoticed around here. Thank you!

Jerry Beaucaire

I'm working today on another computer with multiple LOCAL drives, but the C: drive is notable short on free space.

So the request is still having the ability to set where the TEMP files are written is a blessing in a world of computers where the number of local drives available to the user is an unknown to developers.


And I'm glad to help. Years of support at my companies and being an admin on the has made this stuff a fabulous habit.