Embed Video files not found

Hello Drew!

You may want to look at the system requirements for viewing content with Storyline 2. Opera is not a supported browser and Firefox is only supported with Flash version.

How are you testing the published output? Be sure to view your content in its intended environment. If you published for Web or LMS, upload your content to a server for proper viewing. If you're viewing content locally, publish for CD, then double-click the Launch_Story.exe file. Otherwise, local security restrictions in your computer and browser will cause various features to fail.

Hi Drew,

I just reported this to our QA team yesterday based on this discussion thread. 

I'll add this thread to the existing report as well so that they're aware of another user being impacted. At this time I don't have any updates to share - but I'll post them here once available so please ensure you're subscribed to the thread. 

Just so we are clear I'm talking a Flash problem not html5 and this is loaded to a web server not a local issue.

Drew

I also seems to me the the problem is SL is putting in a backslash in the path instead of a forward slash and the other browsers cope with this but Firefox does not.

Drew

Correct Drew - and that's what I've reported to our QA team for review. 

Disappointed this was not fixed in SL 2 update 2 especially since it is something that did not happen with at least one project I did with an early version of SL 1.

Sorry that you are disappointed Drew, but this issue is in the hands of our QA Team and this thread is flagged to be updated when appropriate.

Downloaded the latest update. Now on update 4. Still not fixed.

I'm surprised getting the back/forward slashes in a path correct is proving so difficult.

Hi Drew! All the details for the updates will be found here. This issue is still with our QA Team. I can see where this thread is set to be updated when needed.

One of my problems with this is that I have project that was built with a earlier version of SL1 that the client would like updated but I have to keep saying "if we update it it will break in some browsers" The fact it is taking sooo long really makes me question my use of SL

HI Everyone in SL Land!

Just over four or so years ago Drew and I set out to promote SL as our preferred choice to deliver online training for my many clients in Adelaide, Sth Australia. We looked at all systems and being mac based I was very reluctant to go to a PC program. However, go we did.

We chose storyline because of many reasons and I am actively promoting it as a product to my clients and for prospective ones too. We have invested a lot of time and capital to make it our workflow and have big plans for the future around this product.

I have only today met with Drew and discussed this issue with Firefox and web objects and I am struggling to understand why a problem that should be fixed with a minimal code brushup has even taken so long to happen. Indeed it wasn't actually broken in earlier versions of SL.

The responses above, while clearly friendly are not responsive to the issue other than to say that is with someone to look at. If this is continued, it makes it somewhat embarrassing if a prospective client has to be told they can't use a major browser to access our training programs. 

Is it more appropriate that maybe Drew and I can get a clear answer saying, yes we will back you as loyal customers ( I own SL as well as Drew) and we will fix this in XXX days, weeks or months, or simply say sorry guys, this can't or won't be fixed and then we can make our plans accordingly.

If I had an issue like this with my clients, I would probably be copping a bit of flak by the 90 day mark or so.

So how about a bit of genuine followup for the people that are buying and promoting this platform out in the trenches on the other side of the world.

Oh and while you fix that, can you paleease make a shape have no outline by default instead of the other way around ( almost all your tutorials start with..."now turn off the shape outline".

Many thanks for your prompt action and a meaningful reply to Drew!

jon burke

www.jon-burke.com

Hi Jon,

Thanks for reaching out here and providing some honest feedback. 

I'll deal with the easy question first, in regards to shapes and their outlines. That would need to be a feature request and you're welcome to submit it here (and encourage others to do so as well). These go directly to our product development team for review as they look to what to include in the next update or versions of Articulate software.

In regards to the videos that aren't working in Firefox, I looked at the report filed with our team and it has been marked as a critical issue and is actively being investigated by our team. Unfortunately, we don't share timelines or timeframes in regards to release dates though for updates or new versions. I know that's not the answer you wanted to hear, but unfortunately it's the information I'm able to offer.

If you need anything else or have any other questions please feel free to let us know. 

It gets worse!

I had not picked this up before but the same problem occurs if the project with embedded video is run in the Articulate iPad app.

A project that has embedded video (Vimeo) will run fine on the iPad in html5 but if the app is installed and it plays in the app we get a "The requested URL was not found on this server error" which is the same as the error we get in Firefox running Flash described above.

Drew

Hi Drew,

Do you have a link to a video file we could try? I know that there have been some issues with embedded video based on some CSS styling elements within the video themselves as documented here - but typically it'll give you the error prior to publishing. 

Ok I have created a couple of test examples

Firstly a project published including html5 but not the Articulate app to prove the video works on the iPad

http://story.nilestreet.com.au/html5/story.html

Now exactly the same project but published including the Articulate app

http://story.nilestreet.com.au/app/story.html

When I view the project in the app I get exactly the same error as with Firefox described above (screenshot attached)

The iPad is IOS 8.1.3 the Articulate app version 3.2 which should be the current version

Regards

Drew

Hi Drew,

Thanks for the links to your published output. I see the same error message as you described, but I'd like to take a look at the video file and try hosting it on a different LMS or server. Could you share either the video link or just that one slide from your .story project file? 

Ashley,

http://story.nilestreet.com.au/files/telehandler_v2.0sc1+marker.story

This is the project used to create the above two tests

Drew

Thanks Drew for sharing the file. I downloaded it and just stripped it down to the video file slide to really focus in, and I also included a second slide that has the same video embedded as a web object instead of using the embed code as you currently have set up. That slide the video works as expected. You can try that one here.  (Use your "start question" button to go to the second slide). Are you able to utilize the insert web object option? If so, that seems to be the best best - as I do remember another thread now with users who were having difficulty with vimeo and the mobile player based on elements vimeo adds to their embed code. 

Thanks Ashley,

Yes this fixes the problem in the mobile app.

It also fixes the problem in Firefox running Flash.

Lets also be clear this is not specifically a Vimeo problem. We also have videos that we stream from our own server that we have had the same problem.

Inserting as a web object in the way described fixes our own videos as well although not being able to specify the size of the iframe means with our own video are going have to match the sizes a bit better than we do at present.

So overall a big win.

Thanks again.

Drew 

Hi Drew,

Glad that fixes it for you - and I've seen it before with other videos that are in their own players/iframes as you mentioned and how different browsers interact with that in Storyline. 

Hi All!

Articulate Storyline 2 Update 5 is now available for download. It includes WCAG 2.0 support, several new accessibility features, better HTML5 performance, and bug fixes. Click here for details: