I converted a video to webm through Any Video Converter and it plays fine in Firefox. However, in Chrome it constantly resizes itself during playback and I'm not sure why.
I previously used Miro converter, but that video wouldn't play in Firefox at all for some reason. It would jump instantly to the end of the video when I pressed play. When using my custom settings, it did the weird resizing thing in Chrome, but when I exported it again using the default settings, it played normally in Chrome, but still nothing in Firefox, so I switched to using Any Video Converter and now the resizing issue is back. I didn't change anything in the settings.
Here's the link:
http://kimkellermedia.com/videoTest.html
I'm using the latest versions of both Firefox and Chrome by the way.
I never quite figured out what was causing the rapid size change during playback, but this link recommended some converters I haven't tried yet. http://www.my-html-codes.com/html5-video-converters
I used Free WebM Encoder http://webmsoft.com/free-webm-encoder.html and everything works fine now on all browsers. So, if anyone else has seen this weird issue, use this converter I guess.
It would still be nice to know what caused everything in the first place, just in case it happens again, but at least everything is fine now! By the way, I've taken down the videoTest link I provided in the original question since I don't need it anymore.
Related
I'm a little confused by this one. A similar question was posted here:
How to deal with poor HTML5 video performance in Chrome?
but no satisfactory resolution seems to have come of it.
The long and short of it is that the HTML5 video element has a very poor performance in Chrome. Every other browser I've tried (IE9/10, Opera, Firefox, Safari, Safari iOS) runs absolutely fine but Chrome (for Windows) buffers very slowly and occasionally stops buffering altogether. It seems to ignore the preload attribute, although according to this article:
http://oddlystudios.com/blog/html5-video-problems-in-chrome/
it DOES preload, just limits itself at a couple of MB. This is definitely a recent thing, probably only affecting recent versions (I'm on 26.0.1410.64 m) and it's not only affecting my projects but also other sites including YouTube. It seems to be irrespective of file format, and only seems to affect longer videos (those of 5 minutes and above).
I guess my question is, has anybody else come across this phenomenon? If so, how do you combat it? In the other thread disabling the hardware acceleration for H.264 was suggested, but not only does this not work for me, but it's impractical from a development standpoint.
Yes Chrome itself preload just few of MB's among its entire video. The only approach taken by me was, to show loading progress bar while we load the entire video at background. once fully loaded the video, remove the loading layer and show the video to play ahead.
An odd thing with firefox. This video will only play when it's seeked from ~6 seconds onwards
http://www.wealthplanning.tv/media/videos/introduction.webm
html link here too http://wealthplanning.tv/media/videos/test.html
Works fine in Chrome, and even opera when inside the video tags.
Anyone have any ideas?
Seems that it was an encoding issue. Was using Miro originally, but tried it with XMedia Recode instead and that solved it.
I had a solution to show both .MP4 and .WMV embedded in the browser. It worked fine in both IE and Chrome, but for some time ago it stopped working in Chrome. Chrome will not show any files (mp4 or wmv), but it works fine in IE. I googled it, and found several reasons to why Chromes newer version couldn't deal with this, but no solution to my problem.
The solution that worked was <object><embed>, but this only works in IE now. Then I tried to add the <video> tag and got it to work with mp4 in Chrome, but not with wmv.
So, is it anyone that have a solution to embed a wmv file that will run without problems in Chrome?
The requirements is that it should be able to play both MP4 and WMV files in Chrome and IE.
The long and short of it is that there is no solution. The <video> tag is supported by almost all browsers now, but there are different levels of support for different formats:
MP4 - Good support (noone uses Opera anyway). Works with both the browsers you mentioned.
WebM - Patchy support, definitely none on IE for the time being
WMV - I can't even find anyone giving a hard answer on this one, but I think the general concensus is that <video> is the way to go, and that to use one of the two above formats is the way to go. MP4 seems the better choice for the time being. If there are requirements to say that you must achieve the impossible/pointless, I'd suggest that your requirements-setters familiarise themselves with ffmpeg :)
I'm having some trouble with HTML5 video in IE9.
Video (MP4) is playing, but it looks like there's an encoding error as it now and then jumps and display white squares, almost like oversized pixels, in parts of the image.
I don't have this problem on my machine, in my IE, but co-workers seem to have this problem. And we have the same version of IE installed.
I tried adding codecs="avc1.42E01E, mp4a.40.2" to the code, but it did not solve the problem.
Anyone got an idea on what this might be?
This seems to be an issue in the conversion process. I tried converting the files, same settings, but in a different converter, and this seemed to solve the problem. So if you have choppy, wierd video in IE, try converting it again. :)
Trying to get html5 videos working and running into a color problem.
(For those interested, there's also this problem)
Chrome renders videos slightly differently than other browser.
On safari & firefox the background is nice and white. On chrome it's a washed off beige.
See compared screenshots:
It doesn't matter which codec is used - Chrome reads m4v, ogg and webm fine - but they all render washed off..
Can't seem to be able to correct this.
Any idea?
Ok, that's interesting.. seems to only happens on the latest dev version (10.0.648.6).
If I switch back to the current mainstream version (8.0.552.237) all the problems go away (including the cross-referenced question problem)