7 Replies
Peter Anderson

Hi Susan, 

After publishing, are you uploading your course to a server? Can you confirm that the server you're uploading to is configured to support MP4 mime types? If it is, and the issue still occurs, are you able to send us your .story file, along with some more information about what you recorded and what kind of browser you're using? Thanks!

Duane Knudsen

@Susan:

Hi Susan, I am experienceing the exact same thing. Publish output for web and push to server for team review. The link that Peter provided should give your IT department exactly what they need to make a very minor adjustment, and probably a 90 second task. I just requested this change for my server yesterday but we've got a major update happening this weekend so I won't be able to report back on this until probably Tuesday. But send that link/info to your IT folks.

At my last position we had to make this quick server change and in a snap everything was working fine.

Ashley Terwilliger

Hi Duane,

Thanks for the additional information - I'm not sure that Susan subscribes to this thread, but you may want to PM here. 

Glenda, it sounds like odd behavior - have you tried publishing it to see if you were able to play the video there? Additionally, you'll want to make sure that you're following these general practices while working:

  • Always save and publish to your local hard drive (typically your C: drive). Working on a network drive or an external (USB) drive can cause erratic behavior, such as file corruption, an inability to save changes, and loss of resources.
  • Be sure the file paths to your projects and published output are well under the 260-character limit imposed by Microsoft Windows.
  • Avoid using special characters, accents, or symbols in your file paths and file names. 

Have you been able to recreate the problem in another file? If not, you could try importing this .story file into a new Storyline project to see if you're able to get the screen recording to play.