Microsoft Saves H.264 Support for Chrome

CommanderFrank

Cat Can't Scratch It
Joined
May 9, 2000
Messages
75,399
Microsoft released an extension to restore H.264 video format to Google’s Chrome Browser for Windows 7 users. Google dropped support for the format last month, upsetting many Chrome users and developers.

Microsoft’s release follows shortly on another free add-on for FireFox that enables Windows 7 users to play H.264 video using Windows 7′s built in media capabilities. Microsoft has long offered a Windows Media Player plug-in for Firefox.
 
Getting rid of one plug-in only to gain another. This was not the goal of HTML5 video.
 
Microsoft released an extension to restore H.264 video format to Google’s Chrome Browser for Windows 7 users. Google dropped support for the format last month, upsetting many Chrome users and developers.

I'm genuinely curious as to the reasoning for MS doing this. If people want their H264 video, why wouldn't MS suggest dumping chrome, and switching to IE 9? Ultimately I'd imagine MS wants people using IE over Chrome.
 
I'm genuinely curious as to the reasoning for MS doing this. If people want their H264 video, why wouldn't MS suggest dumping chrome, and switching to IE 9? Ultimately I'd imagine MS wants people using IE over Chrome.

I'd assume its the same reason they released the WMP add-on for Firefox.
 
Because it makes MS look good?

obviously if people arent using IE, it is for a reason, so why make people try to come back who likely wont and will just find some other option

MS got smart and decided to be that other option for them.,
 
I'm genuinely curious as to the reasoning for MS doing this. If people want their H264 video, why wouldn't MS suggest dumping chrome, and switching to IE 9? Ultimately I'd imagine MS wants people using IE over Chrome.

Microsoft has been pro choice for lot of things a lot longer than people give them credit. If it was 10 years ago you may have a point, but not really now. The only people going on about how oppressive and whatever are people who left them for Linux or OSX years ago.
 
It looks like apostrophes got changes to the letter "f" somehow, and some other weirdness.

Microsoft released an extension to restore H.264 video format to Googlefs Chrome Browser for Windows 7 users. Google dropped support for the format last month, upsetting many Chrome users and developers.

Microsoftfs release follows shortly on another free add-on for FireFox that enables Windows 7 users to play H.264 video using Windows 7Œs built in media capabilities. Microsoft has long offered a Windows Media Player plug-in for Firefox.
 
Its because it makes the entire Windows experience work better, and MS cares about that very much, regardless of what browser you choose to use.
 
The only people who care about which browser has what secret special feature, are the people who read forums like these. The real world people don't care, they just want something that works. So good job to Microsoft.



google = the borg
"We are the borg, we were once the cool simple indexing search engine that didn't content filter and let paid advertisers control search results. All your searches are being logged by us"
 
MS needs good PR to counter the stupidity. Windows 7, yeah it's great, windows PHONE 7? it's a complete POS.

Last time I checked IE had more holes than swiss cheese, but this *might* have changed :rolleyes:

MS realized like the poster above, people who switched to a diff browser aren't comming back, so they did the next best thing, and in the mean time push their brand into your non-MS browser (though I do feel this plugin is a good thing)

Just keep your eye on them, they're becoming a Villain With Good Publicity...
 
lol, it maybe good PR propaganda or alien exists and Google is The Borg theory, but most probably they are not suggesting IE because of all those anti-trust cases they've been having about their sh*t being bundled here and everywhere.
 
Microsoft has core patents in and is a member of the H.264 licensing pool. As long as there is a demand for H.264 encoded content, Microsoft is making money. As said above, people who use Chrome or Firefox probably aren't going to switch to IE any time soon. So MS lets them access H.264 content on the web, which drives demand and keeps the money flowing.
 
Cool. I guess the future of the default web video codec is no longer in question. The only people that are screwed are the Linux crowd.
 
Its because it makes the entire Windows experience work better, and MS cares about that very much, regardless of what browser you choose to use.
The plugin for Firefox has a memory leak bug, still haven't been fixed. It causes Firefox to behave very oddly, it's not the normal memory leak.
 
The plugin for Firefox has a memory leak bug, still haven't been fixed. It causes Firefox to behave very oddly, it's not the normal memory leak.

And the plot Thickens!

MS: See how bad this thing works, you all need to come back to Internet Explorer! (implied not said)

Of course there's an equally good chance it's just sloppy code that they didn't bother to debug well... we ARE talking about the company that released Windows ME ("XP Beta") and Windows Vita ("Win 7 Beta"), after all...
 
So basically the last version of IE you used was 6?

To be brutally honesty, yeah that sounds right, I went straight Firefox (or opera on my old phone, Dolphin HD on current one --- though if FFmobile fixes its bugs I might go with it too) As of right now the only thing I've considered other than FF was Safari (nice fast webkit) but it lacked too many FF features I use regularly
 
The security with IE has improved considerably with the built-in sandboxing. The rendering now (with IE9) isn't bad either. Still just an incredibly painful browser to use, though. It's a feature-loaded, safe and attractive car that has a four foot steering wheel and a gas pedal on the roof.
 
I'm genuinely curious as to the reasoning for MS doing this. If people want their H264 video, why wouldn't MS suggest dumping chrome, and switching to IE 9? Ultimately I'd imagine MS wants people using IE over Chrome.
IE doesn't directly make MS money, windows does. MS benefits from keeping people on windows. The move towards the web and away from local applications represented and still represents a threat to the dominance of windows.

Microsoft moved to counter this by making internet explorer free and later bundling it with windows and therefore cutting off netscape's air supply by forcing them to go free too (who would pay for a browser if they can get one free? not many). This worked for many years but after winning the browser war MS got complacent and other browsers started to come back into the picture first mozilla suite, then firefox, then safari, then chrome and web developers realised that maybe relying on MS specific stuff wasn't such a good idea after all.

While I'm sure MS would preffer website developers made IE specific websites having them make websites that work on all windows browsers but not on browsers on other operating systems is far better for MS than having web developers make websites that work for everyone.

*assuming you live in a country where software patents are valid and that the patents that cover decoding hold up in court.
 
The security with IE has improved considerably with the built-in sandboxing. The rendering now (with IE9) isn't bad either. Still just an incredibly painful browser to use, though. It's a feature-loaded, safe and attractive car that has a four foot steering wheel and a gas pedal on the roof.

Lets see, we have the fast webkits with no features, Mozilla with average speed and features, or IE being slow and heavy with features... I think I'll stick with Firefox (esp since most of my machines are lower-powered (and acctually if Safari comes out with a good plugin to sync bookmarks with Firefox I might slap it on my netbook and tablet...)
 
Getting rid of one plug-in only to gain another. This was not the goal of HTML5 video.

There was no goal with HTML5 video. Hence why they never made any kind of standard for it. That's why some are going h.264, while others are going ogg.

MS is pushing h.264, so if they can make it so everyone will have h.264, regardless of browsers. It's a win for them.
 
The security with IE has improved considerably with the built-in sandboxing. The rendering now (with IE9) isn't bad either. Still just an incredibly painful browser to use, though. It's a feature-loaded, safe and attractive car that has a four foot steering wheel and a gas pedal on the roof.

Incredibly painful how? I run IE 9 Beta on just about every form factor and interface that Windows currently supports and I've just had few issues on all of these various hardware platforms. Touch is particularly good in IE 9, it's much better out of the box than Chrome and a bit better than FF 4 Beta. I don't use a lot of plug-ins and add-ons and in that department IE is well behind both FF and Chrome but for basic and reasonably safe and fast web surfing IE 9 is pretty much on par with all of the major browsers these days. By this Thursday when the IE 9 RC is released we should have a very clear picture how IE 9 really stacks up to the competition.
 
IE being slow and heavy with features
IE isn't really all that slow, just painful to use. Very bizarre layout of the chrome and behaviors when you attempt to stop a page from loading (in which it tends to have a bitch-fit).

There was no goal with HTML5 video. Hence why they never made any kind of standard for it.
The <video> element is a standard (or will be, once the spec is completed). It's right there in the draft proposal, plain as day. The lack of specificity in supported formats, however, is historically how the W3C has always done things and was intentional.

The goal of the video element, by the way, is to eliminate the dependence of plug-ins for web video. If lack of browser support for a widespread format necessitates a plug-in, that goes against the original goal of the video element. In releasing this plug-in, Microsoft appears to be acknowledging the practical uses of HTML5 and the video element without actually acknowledging its purpose.

So, like I said, swapping one plug-in for another.
 
IE isn't really all that slow, just painful to use. Very bizarre layout of the chrome and behaviors when you attempt to stop a page from loading (in which it tends to have a bitch-fit).

I rarely do this, tough to on my faster machines as most pages load instantly even on broadband now that I'm 4G. Just tried it on a few sites that I know are very slow on my Slate 500, the pages just stopped loading. Pretty much the expected behavior.
 
The <video> element is a standard (or will be, once the spec is completed). It's right there in the draft proposal, plain as day. The lack of specificity in supported formats, however, is historically how the W3C has always done things and was intentional.

The goal of the video element, by the way, is to eliminate the dependence of plug-ins for web video. If lack of browser support for a widespread format necessitates a plug-in, that goes against the original goal of the video element. In releasing this plug-in, Microsoft appears to be acknowledging the practical uses of HTML5 and the video element without actually acknowledging its purpose.

So, like I said, swapping one plug-in for another.

How can you have a goal of eliminating plugins for web video, but then not standardize which video format to you? That's like asking the market to make plugins.

If that was their actual goal, then W3C have a bunch of morons working over there.
 
Microsoft has core patents in and is a member of the H.264 licensing pool. As long as there is a demand for H.264 encoded content, Microsoft is making money. As said above, people who use Chrome or Firefox probably aren't going to switch to IE any time soon. So MS lets them access H.264 content on the web, which drives demand and keeps the money flowing.

Technically true, however MS pays far more to the organization that controls h.264 than MS receives in royalities so it's false to say that MS supports h.264 because of the patent pay off. I know some people will never believe it, but MS wants users' computer experience to be good, and having all browsers support h.264 will make everyone's computer experience that much better. A good experience, caused in part by MS, equals more sales for them.
 
How can you have a goal of eliminating plugins for web video, but then not standardize which video format to you? That's like asking the market to make plugins.
What would be the point? Adherence to the spec is entirely optional, so browser vendors would simply opt out of supporting whatever formats they don't want to support anyway. Do you genuinely believe that Mozilla would have licensed H.264 if the W3C/WHATWG had simply suggested doing so in the spec? Do you think Apple would have implemented Theora in Safari if it were in the spec?

The specs detail how things should be implemented. They do not define what tools are used to deliver content. The W3C's interests are in avoiding any potential favoritism when it comes to format support.
 
MS needs good PR to counter the stupidity. Windows 7, yeah it's great, windows PHONE 7? it's a complete POS.
Actually I use the WP7 and I love it. So that's your opinion. However Microsoft needs to do updates more often rather than releasing it in 1 big package like they do with Windows.
 
Actually I use the WP7 and I love it. So that's your opinion. However Microsoft needs to do updates more often rather than releasing it in 1 big package like they do with Windows.

It lacks a lot of features that are expected on a smartphone including Cut+Paste, Tethering, and even full Multitasking! It's networking is crippled (cant connect to hidden APs, doesn't support a Static IP address, doesn't support many Bluetooth profiles, or use VOIP), And have fun if you decide to take out your MicroSD card, your phone will factory reset! (for a full list of missing features see: http://en.wikipedia.org/wiki/Windows_Phone_7#Features_removed_from_Windows_Mobile )

If you essentially want a MS feature phone, then it's probably great, but a real smartphone is gonna have to run Android or BBOS now (as much as I hate iPhone, even IOS has more features than WP7!)

If you like it, I'm happy for you, but personally I'm sticking with Android. (Though to be fair outside of a bug in the Ad-hoc WiFi, I loved WM6.5 just... not the neutered WP7...)
 
It lacks a lot of features that are expected on a smartphone including Cut+Paste, Tethering, and even full Multitasking! It's networking is crippled (cant connect to hidden APs, doesn't support a Static IP address, doesn't support many Bluetooth profiles, or use VOIP), And have fun if you decide to take out your MicroSD card, your phone will factory reset! (for a full list of missing features see: http://en.wikipedia.org/wiki/Windows_Phone_7#Features_removed_from_Windows_Mobile )

If you essentially want a MS feature phone, then it's probably great, but a real smartphone is gonna have to run Android or BBOS now (as much as I hate iPhone, even IOS has more features than WP7!)

If you like it, I'm happy for you, but personally I'm sticking with Android. (Though to be fair outside of a bug in the Ad-hoc WiFi, I loved WM6.5 just... not the neutered WP7...)
I'm aware of what they lack so you don't need to post an entire paragraph detailing what is missing. I own the phone so I'm just saying it is your opinion. It is still a relatively new operating system that was started from scratch based on the Zune interface rather than continuing the 6.5 line.
 
How can you have a goal of eliminating plugins for web video, but then not standardize which video format to you?
In early drafts (remember html 5 is still a draft standard) they did specify theora.

Unfortunately it became clear that there was no format that was acceptable to all the browser vendors. H.264 has patent license issues that make it impossible to implement it while following the spirit of free software (mozilla could buy a license for their own binaries but anyone modifying them would not be covered) and apple were openly refusing to implement vorbis/theora (claiming it was a submarine patent risk). The maintainers of html 5 decided it was better to sacrifice a standard format for the video tag than have vendors refuse to implement html 5 as a whole.
 
I just switched to chrome yesterday and there is something to be said for syncing all my bookmarks between my work pc, home pc, macbook and bootcamp easily... if IE did that and had an add block + add in i dont know if id keep chrome but happy with it so far
 
It lacks a lot of features that are expected on a smartphone including Cut+Paste, Tethering, and even full Multitasking! It's networking is crippled (cant connect to hidden APs, doesn't support a Static IP address, doesn't support many Bluetooth profiles, or use VOIP), And have fun if you decide to take out your MicroSD card, your phone will factory reset! (for a full list of missing features see: http://en.wikipedia.org/wiki/Windows_Phone_7#Features_removed_from_Windows_Mobile )

If you essentially want a MS feature phone, then it's probably great, but a real smartphone is gonna have to run Android or BBOS now (as much as I hate iPhone, even IOS has more features than WP7!)

If you like it, I'm happy for you, but personally I'm sticking with Android. (Though to be fair outside of a bug in the Ad-hoc WiFi, I loved WM6.5 just... not the neutered WP7...)

Most of this stuff isn't important to most users. The idea behind WP7 wasn't to recreate Android, it was to create a simple and straightforward device. Yes it would be nice to have a lot of these features but given that WP7 has been on the market all of 3 months its feature set ain't bad compared to other phones in the same point in their lifecycle.

This is just the first step for WP7. Its got a ways to go but Microsoft is in this for the long haul. Microsoft concentrated first on the UI and in that department WP7 is extremely good. And the app market is growing at a decent clip, there should be 10,000 apps in it in the next month.

If Microsoft continues to take it a step at a time, focuses on the basics and not try to overwhealm the device with tons of features that are half-baked and creates simple and compelling experiences this platform is going to be very competitive. No it won't overtake Android or the iPhone, that's not what Microsoft is trying to do at this stage.
 
So what everyone is telling me is that W3C made a goal, then just abandoned it. In other words, lack of goal.
 
The goal hasn't been abandoned. The goal still is, and always has been, about removing the dependence of plug-ins for playing back video and audio on the web. I don't understand what would lead you to the conclusion that this goal has been abandoned.
 
Cause it's apparently a goal they don't seem to care about. As they aren't doing anything about it.
 
Pick a format, call it a day. Hell, I would have just went with h.264, simply cause MS and Apple already chose it. It's easier to make Mozilla and the other browsers swap to it, than MS and Apple to swap off it.
 
You don't seem to understand. Conformance to the HTML5 specification is optional. If the draft had specified H.264 for the video element, Mozilla would have still chosen not to license it for Firefox (because they have a reason for not doing so) and Google would have still removed H.264 support in Chrome (because they have a reason for doing so). Meanwhile, all the other browser vendors who simply cannot afford to license an H.264 decoder or can't license one due to other restrictions would have shrugged their shoulders and said "okay, whatever" and implemented support for whatever formats they felt were appropriate.

Just because the W3C says "jump" doesn't mean anyone has to follow.
 
Back
Top