Microsoft Is Releasing an H.264 Plugin For Firefox
ndogg writes "Microsoft has announced that it is releasing an H.264 plugin for Firefox. This plugin does not add H.264 capabilities to Firefox, but rather allows it to use the H.264 capabilities built into Windows 7. With that in mind, it sounds like it may not work on anything other than Windows 7."
Seems like a pretty reasonable solution to me.
In other news... Anonymous Coward is going for first post. It seems as if it may not work if he does not go for first post.
So in effect, to use said extension, you will need to either:
a) Upgrade your XP/Vista box to Windows 7
b) Say goodbye to your Mac
c) Ditch your *nix distro
I can't really see many people doing that. However for anybody using the operating system, it's really not such a bad idea. While the idea of Microsoft developing a Firefox extension may turn heads, they're only doing it to benefit themselves.
Open slashdot... see add... Microsoft releasing plugin for Firefox (huh?) open article, "oh only works on Win7"... look for reason to get angry at Microsoft... can't find any on this one, seems like a nice thing, hear a bird outside, sip my soda, nice day out.
Just disrupt the deflector shield with a tachyon burst.
But Microsoft could not afford to sign the add-on? I sure did not feel confident installing it given it's not open source is unsigned and comes from a non-microsoft.com domain. Also seems like it doesn't always work - not a huge surprise from Microsoft but I like their honesty in admitting it this time :)
They are either realizing that either:
1. they are becoming increasingly irrelevant on the desktop as people are using mobile devices more and more for their needs (iPad/Android for email and facebook)(and Apple computer sales have been growing handsomely), and therefore need to compete for customers for the first time in 20 years, or
2. it is a good opportunity for them to pull the old Embrace, Extend, Extinguish.
Only time will tell.
Now, off to RTFA.
If you don't know what AltaVista is (was), get off my lawn.
I have windows 7 but still need to get vlc to play h.264 movies. WHY?
(Speaking as a Linux user here)
This is probably "good enough" since it will apply enough pressure to get the rest of the userbase covered quickly enough. Competitive forces should drive similar efforts for GStreamer (and perhaps Phonon) and QuickTime (is that the right MacOS framework?) soon enough. The problem comes with the fact that it's almost guaranteed to be a closed application, so there's nothing to build atop except the interface and feature set.
The real question is what Google thinks of this; despite YouTube's H.264 ties, they've been pushing WebM (a simplified Matroska container holding VP8 video and Vorbis audio) in place of FLV (or...?) containing H.264 and MP3 (or AAC?). Google will have to react FAST if they want to push WebM. For the sake of free/open standards in HTML5 video, specifically to prevent license/royalty issues with proprietary codecs to let the little guys compete, I'm rooting for Google.
So when I say "good enough," I'm referring to what it might kick-start rather than the more immediate effects. Things should start to get interesting.
Use my userscript to add story images to Slashdot. There's no going back.
Given that Quicktime supports H.264, has anyone else looked into getting Firefox to use that for MP4/H264 playback, via a plugin in MacOS X?
BTW I am assuming we are talking about the video tag and not MP4/H264 in a embed/object tag?
Jumpstart the tartan drive.
It's not a catchy name, but at least it's descriptive.
To watch a video now I need the Flash plugin. To watch a video in HTML5 with the awesome video tags I need a FF plugin. Nothing really changed, does it? Instead they (the W3C) could have set a standard video codec so we don't need any plugins anymore and would have an addons free WWW.
http://www.mueller-public.de - My site http://www.anr-institute.com/ - Advanced Natural Research Institute
Well, I've read about half the comments, and so far the general sentiment of the FOSStard community to my understanding is this:
- Microsoft should have written an h.264 plugin for Firefox on Linux and OS-X.
- It's typical of Microsoft to do something like this and not support XP.
- Etc.
Here's the deal, guys:
H.264 support is not "built into" Windows 7. It's built into Windows Media Player 12. That version shipped with and is exclusive to Windows 7. It can't be installed to XP. Microsoft has previously released a Firefox plugin that enabled some older version of Windows Media Player to run an instance within Firefox. There are some sites out there that use old IE-only extensions to play video and they embed an instance of Windows Media Player directly into the browser window. The old Windows Media Player Firefox extension only enabled Firefox to support this garbage.
Now they have released an updated plugin based on Windows Media Player 12 that (not surprisingly) only runs on Windows 7. Since it's based on Windows Media Player 12, it supports H.264. It probably is even neater now since it interprets HTML5 tags and automatically invokes. It's not just for embedded Windows Media Player crap anymore.
Earth 0
End of first half.
"Flyin' in just a sweet place,
Never been known to fail..."
Microsoft has always pushed h.264? Ever heard of WMV?
It is my recollection that MS has "always" pushed H.264 over WebM since such a stance can only have existed after WebM's introduction, which is pretty recent. WMV uses VC-1 (a MS proprietary codec written into the BluRay standard) and so is somewhat of a contender, but it's a bit behind VP8 (used by WebM, patents released into public domain), H.264 (preferred by YouTube in FLV containers, patent-encumbered), and Dirac (a candidate for VC-2, preferred by BBC, patent-free). See also Wikipedia's Comparison of H.264 and VC-1.
Use my userscript to add story images to Slashdot. There's no going back.
No kidding?
those that are are well.....nvm....
Installed it; went to Microsoft's very own HTML 5 page; it wouldn't play (readme warned me about this) even though it could (detection failed)
Googled "h264 html5 video demo" -> absolutely nothing worked or did anything
Gave up; uninstalled it. Useless alpha technology. Thanks HTML5!
Your Slashdot User # suggests you don't know the history. You should listen to the old timers and learn something. Seriously.
Guns don't kill people; Physics kills people! - John Lithgow as Dick Solomon on Third Rock From The Sun
How many h264 videos you watching at work?
Plenty in the break room. But some companies have a policy to install the same image on the break room PC that gets loaded onto the work PCs.
Microsoft is first embracing Firefox (wait what?) then EXTENDING with extension AND NEXT THEY WILL EXTINGUISH IT!!!!ONE
?
So in effect, to use said extension, you will need to either:
a) Upgrade your XP/Vista box to Windows 7
b) Say goodbye to your Mac
c) Ditch your *nix distro
I can't really see many people doing that. However for anybody using the operating system, it's really not such a bad idea. While the idea of Microsoft developing a Firefox extension may turn heads, they're only doing it to benefit themselves. by dust11 (895301) ALIAS "CaPTaiN PaRaNoiD"
on Thursday December 16, @05:44PM (#34581092) Homepage
See subject.
Its most probably because of lawyers.
http://blogs.msdn.com/b/oldnewthing/archive/2008/05/14/8502228.aspx
Don't view the plugin as an enhancement for Firefox. View it as an extension for Windows 7 - it's increasing compatibility with a certain feature. And then, it all makes sense - it's Microsoft's business to improve Windows, and now Firefox is getting a free boost on that platform. by gman003 (1693318)
on Thursday December 16, @05:52PM (#34581222) ALIAS "CaPTaiN PaRaNoiD"
See subject.
aha... bundling windows with firefox... good idea ?
What we really wanted was a way to let video stay fullscreen on a second monitor without having to re-hexedit the flash dll every time it gets updated or overwritten.
The first browser to manage that staggeringly complex feat of engineering will be the one I'll use.
No sig today...
I am surprised at the callus disregard for what mozilla is trying to accomplish. Its like 5 years ago why did they bother with this open standard, royalty free, patent unencumbered html stuff, they should have just shipped a free Microsoft doc "reader" by default, or why bother with javascript standard, when Microsoft had perfectly good active X systems to tie into native windows apis.
Mozilla knows what they doing, yes they may lose market share, but that is the nature of taking a principled decision that many people don't understand. The web will be better by getting people used to the idea that they need to support WebM in addition to H.264. As today smart phones become tomorrows calculators we won't have to pay taxes on the math that mediates contemporary conversations. Thous removing one small barrier to entry for anyone that wants to design or create audio visual communications systems.
What really happened here: They built H.264 into the next version of the Windows Media Player plugin for Firefox.
Using Windows Media Player, back in the day, was just begging to get the virus that had cleverly disguised itself as hot_chick.mov. Using Windows Media Player is still just begging to get a virus. Granted now I have an antivirus that should catch those threats even if I’m a clueless idiot, being a clueless idiot just isn’t my thing.
I still won’t install the Windows Media Player plugin.
Distributed Denial of APK: It takes 15 seconds to reply to him anonymously, but wastes tons of his time if we all do it.
> why bother with javascript standard, when Microsoft had perfectly
> good active X systems to tie into native windows apis.
NPAPI and JavaScript beat ActiveX and VBScript to market.
Do daemons dream of electric sleep()?
I looked long and hard for the right amount of "cheesiness", and here is "CaPTaiN PaRaNoiD's" theme song (LMAO):
http://www.youtube.com/watch?v=kd85Qim_Z6A
Hahahaha!
I looked long and hard for the right amount of "cheesiness", and here is "CaPTaiN PaRaNoiD's" theme song (LMAO):
http://www.youtube.com/watch?v=kd85Qim_Z6A
Hahahahaha!
"Microsoft has announced that it is releasing an H.264 plugin for Firefox. With that in mind, it sounds like it may not work on anything other than Windows 7"
Sounds about right to me
If this doesn't become like the .NET framework plugin for Firefox...
The one that actually implemented all those nice IE vulnerabilities in Firefox. It was done through a windows update, and wasn't a true plugin, but rather an OS patch.
Sorry, ActiveX (or the technology behind it... COM/OLE) was around long before netscape was even a company.
Granted, ActiveX got a name change in 1996 from COM/OLE 2.0, which was around the same time that NPAPI became available, but many had already been using it for years in VB, Word, etc. NPAPI didn't even support access from script (javascript/vbscript) until 1997.
Are you actually trying to tell me that you really believe that microsoft was shipping a browser that could embed ActiveX controls prior to netscape shipping a browser with NPAPI?
Because I'm pretty damn sure that's not the case. ISTR ActiveX not shipping 'till the 3.0 browsers, but NPAPI shipping with Netscape 2.
Do daemons dream of electric sleep()?
No, I said ActiveX was around before NPAPI, not that Microsoft shipped a browser that supported it.
NPAPI and JavaScript beat ActiveX and VBScript to market.
That is not correct. NPAPI appeared in March 1996, however, ActiveX was around since 1990 as OLE Client 1.0. Then OLE Client 2.0 came about, then OLE Custom Controls in 1994. ActiveX was just a renaming of OLE Custom Controls with all interfaces being optional and the first IE browser to support it was 3.0. While IE 3.0 was offically released in August 1996, developers had the code for many months before then, and support was even added for NPAPI before it's offical release. IE 3.0 also added CSS, and Java Applet support, both of which arrived before the Netscape versions.
Now as for JavaScript...Of course Netscape had theirs first. It was a proprietary language written by Netscape (LiveScript). It was renamed to Javascript before the release and it was eventually submitted as ECMAScript. ECMAScript 1.0 was ratified in June 1997, by which time both browsers had support for it. IE 3.0, however, actually had support for allowing scripting languages (both JScript and VBScript) to interact with ActiveX/NPAPI controls since August 1996 while Netscape didn't add support until 1997 and even then only for NPAPI.
ffmpeg