I use a tool for recording desktop videos.
I use the same settings in the tool and same resolution and record two different videos.
http://www.mindmigma.com/users/fb-fac3b0ok/video3.mp4
http://www.mindmigma.com/users/fb-fac3b0ok/video4.mp4
Both of those videos can be played with Google Chrome version 31.
But only video3.mp4 can be played with Firefox version 27 and Internet Explorer 11
When i make videos it feels like a random pattern if a video will be playable or not. How can this be is the video4.mp4 damaged somehow?
It feels so wierd when you use the same settings and its an 50% chance the video will play in Firefox and IE.
Would be really glad if i could get some help.
Thanks in advance!
/Marten S
As LordNeckbeard suggested: Super User has the answer:
quick fix: Set your security level to Normal (standard is Normal-High).
for more detailed information check Super User:
https://superuser.com/questions/916958/play-mp4-video-in-internet-explorer-11-with-security-level-set-to-high
I just thought I'd share because I lost a lot of time looking for this.
Related
I have a site which has a collection of audio clips for voice actors to promote their skills and talents. Recently it has been brought to my attention that in Google Chrome some of the clips do not play. However you can download the .mp3 and it will play fine, or you can listen to it fine in Firefox, Safari, IE, etc.
So I started Googling and found this bug which was closed a couple of years ago: https://code.google.com/p/chromium/issues/detail?id=110309
I also found this page: http://cro.ma/?faqs=some-of-my-mp3-files-does-not-play-in-google-chrome-browser-but-works-fine-in-all-other-browsers
The MP3 in question is fairly short 10s in playtime, and only 168kb in size. It did have some meta information there but as recommended in the link I stripped that off, however it still doesn't play.
The only other difference I have noticed between the non-working MP3 and the working MP3s is that the non-working one has a bit rate of 112kbps, whereas the working ones are 128kbps.
The site uses MediaElement.js but even just dragging the MP3 into the browser window and using the default engine has the same outcome.
Has anyone else experienced this issue and know of a fix?
It's a problem with version 45 of Google Chrome. Joshua Moon has provided the following solution which may help you, all credits go to him. Just posting as your question was asked after his and I thought you might not have seen it.
Joshua said:
I'm not 100% on the specifics of this, however, it looks like some MP3s using older versions of Lame, or longer than a couple of minutes, or at high (300 <) or low (128 >=) bitrates seem to be affected. It appears to be webkit-related, as it also affects Safari users.
HOWEVER!
As a solution, re-encoding the MP3 files using 160Kbps bitrate, and the latest version of LAME (3.99.5) seems to have fixed this, and they now play normally across all major browsers again.
You can see the full question and answers here (on Stack Overflow): Google Chrome no longer plays certain audio files
I had this problem today on Chrome 50 and simply restarting my browser got it working again.
Based on other's comments I installed "Audio Converter" and converted my mp3 files to 128 Kbps (standard) and they now work. I don't find any loss of quality.
I have an issue at the moment where I cannot get any .mp4 videos to play on Google Chrome 28, this only happens on Windows 7 machines, but not all of them.
As it stands, I was able to replicate the issue on three Windows machines out of five.
Even if I enter the direct URL to the .mp4 file in the address bar, Chrome still won't play it.
Can anyone here replicate this issue?
I have used a few different .mp4 files to test, but here's one:
http://www.w3.org/2010/05/video/mediaevents.html
I would appreciate any help.
Note: By going Chrome Advances settings and turning off "Use hardware acceleration when available" Chrome is able to play the video, however that option is turned on by default, so not the perfect solution to the problem.
Thanks a lot.
UPDATE: updating the video drivers fixed it, but again... not the ideal solution...
we also had this problem... Both Webm and theora/ogg worked fine in chrome and the mp4 video worked fine on IE9 and in firefox. Just chrome fails.
We also manage to fix this by updating the video drivers (intel HD on a DELL PC), so looks like a problem in the H.264 acceleration used in chrome and old intel drivers
Over a year ago we added an video page on our site. At the time OGV wasn't very good, and there was no good WebM encoders available, so we decided to use HTML5 and h.264 for webkit browsers (Chrome, Safari, etc.) and then fallback to Flash for other browsers (using the same h.264 source file.)
This has been working great for a while. Recently (month or two maybe, so over multiple Chrome versions - currently Version 24.0.1312.52 m) we discovered Chrome really lagging on the playback. We thought it was a server issue, so we upgraded the server, and it is still behaving the same. I remembered reading that Google wanted to drop h.264 and move everyone to WebM, and thought this performance was part of that. We converted some videos to WebM and tested them with Chrome and they lag just as bad. Same video (WebM) streams beautifully in FireFox, and the MP4 streams great in FireFox via the Flash plug in.
I went to YouTube and turned on the HTML5 video support, and found the videos to lag in Chrome too (when running at HD) while they play fine in Flash mode. (Even when HTML5 is enabled, some videos still play via Flash.)
Tested on both Windows 8 and Mountain Lion.
I've talked to co-workers and they are seeing the same issues. So it isn't just me. So my question is:
Is this an issue with our video encoding?
Is it a bug with Chrome?
Or is it just localized to us?
Is there a way to deal with this besides switching back to Flash?
This is the flag I mean. If the flag is disabled, the browser tries to use hw-accelerated video decoding, which I can grant provokes wrong and slow video renderization in some devices. If enabled, hw-accelerated video decode is never used, but the above mentioned problems disappear. It theorically increases decoding time in devices actually able to use such acceleration, but I've been working around this field for almost a year and I still didn't realize any difference in that matter. Still didn't get to know how to identify if a device will behave properly (the availability of this feature doesn't seem to grant its proper behavior) with such acceleration without testing, though.
I have two different videos, both (as far as I know) generally captured in the same manner, that I'm trying to play using an HTML5 video tag in Chrome. Both videos open and play perfectly in VLC, so I don't think there's any issue with a corrupted file, and both are mp4's with an H.264 format, using YUV color space. However, when I try to play one in Chrome (Version 21.0.1180.89) it gives me a grayed-out play button, while the other works perfectly. For reference, my OS is Ubuntu 10.10, although I've seen the same problem in newer versions of the OS. This is whether I'm loading the video into the HTML5 tag, or navigating directly to the URL where the video is being stored. I'm somewhat at a loss here, does anyone know what direction I should go to find what the significant differences are between the two videos?
Edit:
This one works: https://dl.dropbox.com/u/100841270/1_G101_20120914_0139PM_Course_101.mp4
This one does not: https://dl.dropbox.com/u/100841270/1_G101_20120914_1156AM_Course_101.mp4
Update:
It appears to have nothing to do with OS, since I've seen the same problem in both Windows and Linux. Chrome 22 beta in Ubuntu didn't seem to work either.
We had this problem and found that encoding the files in accordance with iPhone's webview's standards created files that played fine in Chrome. Chrome and iPhone webview share the same render engine, and it appears they have similar HTML5 video requirements.
Not all H.264 encoded Mp4 files are supported by Chrome and slight differences in the encoding process can produce videos that do not work. Even if the EXACT same encoding settings were used, H.264 is a variable bit-rate encoder, so different videos may exceed bitrate limits.
The encoding settings that were successful for us were:
Only use the H.264 Baseline Profile Level 3.0
Resolution below 640 x 480 and framerate up to 30 fps
B frames are not supported in the Baseline profile.
bitrate limit of 900kb.
Here is the reference we used to arrive at those settings. Likely not all of these are required for Chrome, but we stuck to these rules and found that all videos worked on both platforms. Further research could likely determine the exact setting that is/was causing Chrome to not play the video.
I am running Windows XP, and chrome doesn't like the second one either.
My best guess of the cause is that, the working one is only 6.4 MB, but the other one is about 21.7 MB. Chrome might just be refusing to directly play a video that big. Have you tried having YouTube host it, and embedding their player into your site? That may solve the problem. (If you are worried about random strangers watching the videos, why did you post them here? Why would anybody even want to watch them? Though, you can make videos private on YouTube, in case these are just two videos that demonstrate the same problem you are facing with the real videos.)
That may also be compounded by a different problem that exists with both videos, manifested when I try to use Windows' built-in player. Both videos appear distorted when I use my computer's video player, stretched like 300% horizontally.
Are there other videos you have that fail in exactly the same way? Since these are only test videos for the real thing, if this is the only video with that problem, I would not say that it really is a problem unless it recurs. The dysfunctional video may have just run into that one-in-a-million chance that it has just the right contents for it to not work.
I have to play an ogg audio file in the background when the user hits a "Music On" button. Currently the page uses an AUDIO tag, and it works in Firefox, but not in IE (confirmed by this table).
Is there a really cross-browser way to play an ogg audio file, if possible without Flash?
I am aware of the existence of specific libraries like JPlayer or SoundManager, but do I really have to use one of them? After all, it is just to play a sound...
Forget about cross-browser. Stick with ogg. It's much better than mp3 in every way. Tell people to change their browser to one which supports ogg (e.g. Chrome, Firefox, Opera). If they don't want to change, then forget about them; they don't deserve to hear your audio. If your client doesn't understand this, leave him and let him waste money on one developer after another until he finds a "yes man" developer who will give him a terrible website that will be a nightmare to use and will need completely redeveloped in a year's time.
The Company I work for has dropped support for IE6 for apps and websites and dropped support for IE7 when it comes to apps. Personally, I don't want to be developing for IE at all until I met a friend of mine working elsewhere. She was allowed to work from home, but she had to use RDP (Remote Desktop Connection in Windows) thats supported as a web interface only via IE. Some companies use Windows Group policies to disable USB drives etc. The terminals in these companies can have IE only! So as much as I would hate to admit, cross browser compatibility is a serious issue.
Flash would be the number one choice of plugin to play ogg files. Now, the following scenarios may occur:
iOS (iPad and iPhone) : HTML5 Audio Tag
Android / Chrome / Safari : HTML5 Audio Tag
Opera
Firefox
IE
For 3, 4 and 5 it really depends on the user. Even if they have one of Real Player, QuickTime or Windows Media Player, the would be able to play ogg files. There is a case where the specific ogg codec is not installed. In this case they will get a prompt on the top of their browser, telling them to install the specific codec.
We are talking about people insisting on using IE or insisting on a really really old version of firefox and who don't have WMP (by default on Windows), RealPlayer or QuickTIme installed but have an Internet connection.
Even jQuery leaves out 0.0001% of users ! :-P
You can probably consider using a .wav file, but I'm not sure that works.
The simple answer: no, there's no way to do it without Flash. My approach: simply create a script that converts a single file to multiple encodings.