I'm have a webpage that is just a fullscreen video that I want to display on a Samsung PM32F SmartTv using the built in browser. If I have a internet connection this works fine but when I try to cache the video using a cache manifest to be able to show it offline the video will not play.
I have tried the same kind of caching with images and that works fine.
The video I'm trying to display is a mp4 file and is smaller then one of the images I have tried with so I don't think it's a size isue.
I do not have access to any kind of developer tools for the TV's browser so I can't check for any error messages.
The video is in a <video> tag.
Any kind of help would be much appriciated.
You could try the following script (I could not test it on real tv).
function handleVideo(stream) {
video.src = window.URL.createObjectURL(stream);
document.getElementById("videoElement").pause();
}
After some time I found out it was just a simple server issue with a file that had been moved.
Related
I used Simple Peer(WebRTC), ReactJS for my video call service. In the video call screen, I used 2 video tags(contact video and user video) for video playback. When the call gets started after a successful connection, only the contact video is getting played(1st video tag) and when the contact turns off their video user video is getting played(2nd video tag).
This only happens on Safari(I only tested on Mac). It works fine in other browsers(Google Chrome, Firefox).
Is there a way to fix this issue?
WebRTC depends a lot on browsers and Safari has specific requirements (like strict order of tracks). Check JS console to identify any errors.
You can experiment with a turnkey html5 videocall solution that works and try to replicate.
I am trying to play a video streamed by a third party using the HTML5 video player in Chrome Mobile, the problem I am facing is that the video can play for some time while it's minimized and after a while it decides to quit and return a MEDIA_ERR_SRC_NOT_SUPPORTED - audio/video not supported error; the problem happens much faster when I switch from minimised to maximised then back to minimised over and over again. It also seems to happen faster if I continuously tap on the video itself, I have also hidden the default controls and use my own custom ones.
What could be causing this issue ? I try the same thing in Safari with the QuickTime player and the video feed does no die
EDIT: Did some more digging around and found this:
Android HLS video mime type
I receive a playlist m3u8 file but my request link does not have m3u8 in it whatsoever but should the video even be playing if the m3u8 keyword isn't there ? I am also testing this on an android 4.4.4
Specifying the correct MIME type is worth a try. However, there's one other thing that caught me out (with iOS anyway): check that the server hosting the video supports 206 Partial Content requests correctly. I posted about debugging this issue here.
If your using FireFox and getting the SRC not supported, I went threw the codes on some of the players at sites I like to view, I found that the Adobe Flash Player will solve the Problem, FF uses the VLC plugins, but with the current updates on FF with the VLC on HTLM5 players you might get a SRC error code, you need the Adobe Flash Player.
I have searched your error code on internet and i have found this:
MEDIA_ERR_SRC_NOT_SUPPORTED (4) The media resource specified by src
was not usable. MEDIA_ERR_SRC_NOT_SUPPORTED
(5) The encrypted media
stream could not be played. This is because of one of the following
conditions: A key was not provided and a onmsneedkey handler was not
provided The provided key could not be applied. Decryption is not
supported for this media data.
Source
So I would say you initialize src wrong.
I am making a system that I run on localhost, it embeds a video player and all works fine except for webm videos on Chrome. They freeze regularly and I can only get them running again by pressing play/pause and moving to the initial phases of the video.
I have been googling for this issue and trying to solve it for some time now without success, does anybody know how to solve this?
Is your same WebM file working ok on Firefox? I assume you are using HTML5 video.
I have compiled a short check list on how to troubleshoot HTML5 video playback issue here. Try to play the videojs webm sample to see if it works.
Given the description of your issue I guess it is either a non proper WebM file or a server side tuning issue (like with mime types).
If it is a file format issue you could try re-transcoding from a known good source (ie not the problematic WebM file) with firefogg.
You can also try to set the preload attribute of your HTML5 video tag to auto.
I am using videojs to embed video on the following website: www.airfixthemovie.com. Html video has preload="none" which makes it a bit better. Any suggestion on how to make the video to work perfectly in Google Chrome? The trailer stops sometimes in Chrome and it looks like Chrome is loading or buffering. Thanks for your help.
From the network inspector it seems there's something wrong with the backend serving mp4 files. The requests are canceled and there are about 4 requests to the mp4 a second and the Content-Range header seems to throw completely random digits there.
I know this doesn't really answers your question but at least investigate the mp4 thing server side.
I'm having an issue with html5 video and safari 5. It works locally, the video pulls up and everything is fine. It will also pull up on the server if I go directly to the video path. Im just using the video tag and loading a video. It works on the server in all other browsers supporting html5 video. It works locally. It just doesn't work in safari on the server. In the network panel it shows the video trying to load but returns a null 404. The path to the video is relative. I'm very confused. Any help would be greatly appreciated. Thanks.
I had a problem very similar to yours. HTML5 video/Safari working locally but not when published on server. First check your .htaccess file. You may need to modify MIME types. Here is a very good tutorial: Dive into HTML5 Video.
Second, and this solved my problem, are you serving from a protected site? The solution for me was to move video and audio files to an unprotected folder and then use an absolute path to the specific media.