plays in google docs, needs Windows Media Player in Screencast

  • 1
  • Question
  • Updated 7 years ago
Archived and Closed

This conversation is no longer open for comments or replies and is no longer visible to community members. The community moderator provided the following reason for archiving: Inactive threads; archiving to prevent necroposing

We have MP4 video's loaded into our Screencast account, they are also in our GoogleDoc's account. When we click on the video link in GoogleDocs, the file starts playing right away. After uploading the MP4 videos into Screencast we are asked to install Windows Media Player. What are we doing wrong, would it help if I gave you the links for the video that is in googleDocs and then the links to the same video in Screencast? Many of the clients who view the video are not very technical and we need to minimize any tech support calls. Can you also give me a couple of the additional advantages for having the videos in Screencast vs. google Docs, i.e. more control over how the video is "wrapped" faster streaming, etc?
Photo of Paia

Paia

  • 1 Post
  • 0 Reply Likes

Posted 7 years ago

  • 1
Photo of Mike Curtis

Mike Curtis, Employee

  • 2204 Posts
  • 216 Reply Likes
Hello Pala,

We might want to get you in touch with our Support team ( http://techsmith.custhelp.com/app/uti... ) and ask that you open a case with them. They are the best for one-on-one troubleshooting, especially if it involves 3rd party stuff.

However, I'm curious why anyone would be prompted to download Windows Media player for an MP4.

For Google Docs, I'm assuming you upload the video directly (e.g. you don't host it somewhere else, and then link to it?) Is it the Google Doc word processor or one of the other tools.

Finally, how did you make the video? Camtasia Studio 8 for example?

Thanks for the example and additional details. I'll take a look to see if there are any obvious clues as a first step.

If you don't want to share the links here, you can send them to m.curtis@techsmith.com

Sincerely,
Mike Curtis

This conversation is no longer open for comments or replies.