Firefox 33 Integrates Cisco's OpenH264
NotInHere (3654617) writes As promised, version 33 of the Firefox browser will fetch the OpenH264 module from Cisco, which enables Firefox to decode and encode H.264 video, for both the <video> tag and WebRTC, which has a codec war on this matter. The module won't be a traditional NPAPI plugin, but a so-called Gecko Media Plugin (GMP), Mozilla's answer to the disliked Pepper API. Firefox had no cross-platform support for H.264 before.
Note that only the particular copy of the implementation built and blessed by Cisco is licensed to use the h.264 patents.
Even though the codec source code is available, it is compiled by Cisco and provided to Mozilla. Something in me doesn't 100% trust that Cisco won't use this as an opportunity to put hidden spyware on everyone's computers. The US gov't can force American companies to secretly implement spyware, right?
Not for long...
That is not how you use this word.
I always wanted a backdoor in my browser.
They've already destroyed FF and changed it from a browser with its own identity into Chrome's obsessed former friend who mimics her every move and style and is planning to kill her and assume her identity some day.
Honestly, there's nothing left to call Firefox now. If I want a browser like Chrome, I'll run Chrome. If I want a browser like Firefox, then I have to use an old one or a fork.
Stop punching your users in the face, and give them back the control they had over their browser.
The source is open: you can read it, you can compile it and compare binaries, etc.
In fact, it is BSD licensed.
But that only covers the copyright. The patent is not opened (nor owned by Cisco), and seem to prevent derivative works.
Cisco paid the fees to use the patent in this one application, and open-sourced it to the world. Seems like a great solution, security-wise, and clever legally.
And, it becomes just more BSD code when the patent expires in... what, a decade? Or if the new Supreme Court ruling is found to invalidate the patent.
Your ad here. Ask me how!
(reads summary)
Hum, Interesting...firefox 33 integrates, mumble, mumble...wait, something's not right with this picture.
(Scrolls back a few lines on the RSS feed)
Firefox 31 Released
Aha! I knew it. Latest version is 31! Must be a typo...
(One angry RTFA later)
Oh, hang on...They are referring to the yet unreleased, possibly future version of Firefox. With no indication whatsoever of that fact in the summary, even though a (stable?) version of Firefox was just recently released, as highlighted on this very same website less than 24 hours ago.
Would it have killed anyone to point this out somewhere? You know, for those of us at home who don't keep up with Firefox's versioning madness?
Can we finally use the tag with H.264 files and just forget about the rest?
Get free satoshi (Bitcoin) and Dogecoins
Mozilla capitulating on the tag has serious implications for web standards. By including patent-encumbered code in the browser they take the rug from under those in the www foundation that argue for free web standards. Yes, some websites wanted to use H.264 for video encoding, but Mozilla shouldn't have abetted them.
Serious question: What's the best way to handle video on the web given a few requirements? First, the content needs to be hosted on the same site as the website. Why? Because sites like Youtube and Vimeo have control over it. They can unilaterally decide to take something down. They will also present related video. For someone trying to market product, you shouldn't make it easy for a prospective customer to find your competitors. Second, the video has to work on both Macs and PCs. Third, the video has to work on Internet Explorer as early as v.8 because too many users don't know any better.
so mozilla gave up to make the web a better place?
Isn't there patents on GIF and JPEG? And the web is full of images in those two formats anyway.
Get free satoshi (Bitcoin) and Dogecoins
So, this is a software only patent... so it's not legal in Europe (or is it). Some Linux distro might consider integrating this code directly, and compile it instead of letting FF grab a blob from Cisco. Maybe distribute it in a special repository, that users would activate where it legal... Notice VideoLAN for example does play HEVC (aka H.264), and does not licence anything...
So thats whats gonna be in FF33, which is 2 versions from now.
FF31 has just been released AFAIK
So whats new (or broken) in FF31 - should I upgrade from FF30 ?
And, it becomes just more BSD code when the patent expires in... what, a decade?
A decade from now, most major web video streams will be in H.265 (HEVC), and H.266 will be the Next Big Thing(tm). By the time the patents on one codec have run out, bandwidth constraints cause providers of non-free media to switch to a new freshly patented codec. Users end up stuck on a treadmill, from H.261 to MPEG-1 to MPEG-2 to H.263 family (Sorenson Spark, DivX, Xvid) to H.264 (AVC) and so on.
So, at least on Linux this 'thing' doesn't come packaged with the browser in a package. Instead browser DOWNLOADS this crap from the net. ActiveX, anyone?
Very-very-very disappointing. Looks like Mozilla have forgotten what their mission was behind all those gay-rights fights.
Much as I hate to admit it, what I see is what I get. Kill australis and save Firefox!
Time is what keeps everything from happening all at once.
Yes, some websites wanted to use H.264 for video encoding, but Mozilla shouldn't have abetted them.
H.264 is here.
HEVC not far down the road.
The geek sees everything in terms of the "open" web.
But there is more to digital video than video distribution through the web.
Which is why the mainstream commercial codecs dominate here.
Why hardware and software support for these codecs are baked into the smartphone, tablet, PC, graphics card, HDTV, video game console, Blu-ray player. The prosumer HD camcorder, medical and industrial video systems and so on, endlessly.
Gif patents (LZW-compression part of gif) expired on 20 June 2003 (Source). JPEG only had a patent troll go after it. (Source)
Is a compression factor of 2 compared to a free codec worth the license trouble and the additional development?
Yes. This is why YouTube never implemented Theora, waiting until VP8 (which roughly compares to AVC baseline) before adding any free codecs.
What matters is that the existing standard doesn't empty the battery where a new codec wouldn't.
Why wouldn't the new codec be GPGPU-accelerated too?
I know some will mock this, but there is a heck of a lot of Flash content out there, and Firefox really should work with Adobe for an unloadable plugin for getting an up to date Flash player on all platforms. There is really far too much Flash content out there to ignore this need. Make it something that can be disabled, and unloaded as a plugin, sure. If you don't want it, you won't have to have it loaded, so it keeps everyone happy. I think that getting Ogg support into the browser and other open codecs will help us transition away from the Flash over time, which is something i support, especially with Google doing flash-free on most of its new Youtube content, for instance. But there is a lot of existing Flash content out there and its not going away any time soon, so we need the capability to view it.
This split between supported formats on various browsers is ridiculous. Embed it into the next FireFox so that video tags support H.264. Make it something you can disable if you're paranoid. There will be plenty of time to examine it and make sure there isn't a back door (which would be a stupid thing for Cisco to attempt!)
If you don't trust Cisco you better get off the internet. Seriously, if you're worried about this, a binary blob running in your web browser is the least of your problems. There's a very good chance that the network hardware at your ISP is Cisco. If it's not, it will likely be Juniper.
I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
Virtually all of the popular file formats for video are essentially containers that have mpeg4 video inside. Therefore, essentially any player can play mpeg4. The difference is which package files they can open, so just use a plain .mpg file rather than a proprietary package like .wmv.
If you want to embed the video that's fine, but also provide a link to the mpeg file itself. A plain link to a mpg file is like a plain link to an html page - it will work for anyone.
Bandwidth now is easily a couple of orders of magnitude higher than a decade ago (and moving towards gigabit)
Gigabit per second just means you blow through a month of last-mile data in 40 seconds.
>I think that getting Ogg support into the browser and other open codecs will help us transition away from the Flash over time,
Also, Flash Cc, the authoring tool, can now output HTML5 rather than SWF, so all the existing Flash projects can be recompiled to no longer require the plugin. Support isn't 100% yet, but that's the direction Adobe is going. The programming language within Flash has always been a dialect of JavaScript/Emacscript, so it is pretty simple for Adobe to start using the browser's JavaScript engine instead of one provided by Flash. Other than a cross-browser JavaScript engine, the other thing provided by the plugin is a graphics API. Now that the canvas element, there's no need for the plugin.
True, but if you save all your files in H.264, you are guaranteed an archival data format that can be read by software that won't suddenly stop working.
If you are archiving a video that you produced, what's the big advantage of H.264 over VP8? VP8 is rate-distortion comparable to H.264 baseline, and VP8 is free today. An archival copy needs to be read by software, not necessarily read by specialized hardware in a battery-constrained device.
If you are archiving a video that someone else produced, most streaming video providers have a policy of implementing technical measures to prevent just that, backed by national anticircumvention legislation.
It would be kind of ironic if it were a software-only patent, since one of the reasons H.264 is amazing is the hardware acceleration built into everything.
Your ad here. Ask me how!
Ever wondered what the "89" in GIF89a stands for? It stands for 1989. Unlike copyrights, patents encumber all implementations of a method, even those resulting from independent reinvention. To make up for this, patents last only 20 years, not 95 like a copyright.
If you have a camcorder, the license to create h.264 is present as part of the camcorder. This includes phones and everything else people submit to YouTube, for example.
It doesn't include video game footage or anything else that's edited because as I understand it, the video editing software needs to have its own licensed encoder.
Transcoding isn't fun or fast. I'd rather have my files in such a format that I can actually use instead of some format that I would need to convert before being able to play.
If you archive a 4K video, you need to scale it down anyway before it'll play efficiently on a handheld device, no matter what codecs that device accepts. Besides, if you produced video, you may want to archive the source footage in its original format and a non-destructive edit decision list.
Also, my country does not have software patents, so h.264 is (legally) free to me.
But does it have anticircumvention legislation (DMCA, EUCD, etc.)? Besides, the process of finding a country with acceptable living conditions and visa requirements, finding an employer to sponsor a work visa, and finally moving one's family isn't practical for everyone, I understand.
... all software is implemented on hardware. Even the instructions you send to your processor get translated into other software (microcode) which is what actually gets executed.
Hardware acceleration still runs software.
H.264 isn't 'amazing' because of the hardware acceleration built into everything, its extremely convenient. If OGG was built into everything, we'd be using that instead because thats what would allow us to have long battery life and lower heat dissipation.
H.264 isn't software anyway, its a collection of algorithms and protocols. There are multiple software implementations of H.264, of which cisco's is only one.
Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
sites that were built by the lowest bidder who often only work on Windows and only works on IE
All supported Windows desktop operating systems can run IE 9 or later. Besides, whether and why government employees on government equipment and government time would be watching your video still depends on what the video is of. It might be better in a specific case to download the video to watch in a native, non-web application, or to have the IT department authorize installation of a second browser for "general interest" web sites.
Actually, Firefox has one huge advantage over Chrome - their continued support of NPAPI. Chrome dropped NPAPI as of May, and along with it support for Java plugins. Like them or not, Java plugins are used in HUNDREDS OF THOUSANDS of huge enterprises for internal applications. By dropping NPAPI support, Chrome basically gave a big middle finger to all these enterprises.
I work for one of these huge companies. A bunch of our internal systems requires the use of Java plugins via NPAPI - and there is no way they are going to spend hundreds of thousands (millions?) of dollars to replace all of these internal applications, when Chrome was never an officially supported browser in the first place.
Since Chrome dropped NPAPI, I can no longer use any of these applications in it, so I am now back to Firefox for them. And if I am going to run Firefox for some things, I am going to run it for everything, because I frankly don't have the time or patience to run deal with two web browsers every day.
That seems to kill Firefox portability. For what CPU is the Cisco binary blog available? And does it depends on system-specific libraries or system calls?
Are you perhaps confusing ActionScript version numbers vs Flash Player version numbers? ActionScript was introduced in Flash 5. Adobe says they based ActionScript 1.0 on Emacscript. Of course, the first version wasn't complete. It was based on Emacscript, though, according to the people who wrote the friggin language.
Here's the third edition standard for ECMA script. Please point out any way that ActionScript 2.0 doesn't comply with the standard aside from the comparison operator.
http://www.ecma-international....
Yeah, unsurprising that restarting Firefox had no effect. Stuttering seems to be pulseaudio thrashing wildly in its buffers. I've had it happen with our game too. Can also leave application windows hanging as they wait for audio closes.
It is possible that just pulseaudio -k might have been enough without the restart, even.
-- perl -e'print pack"H*","6e656d6f406d38792e6f7267"'
screenshot from uTorrent was dismissed since uTorrent is not certified as an evidence gathering tool - like, say, a police radar
Common cameras aren't "certified as an evidence gathering tool" either. Do courts likewise reject all photos of a violent crime scene that aren't taken with a "certified" camera? The commodity home movie camera Abraham Zapruder was using wasn't "certified", but his and other films provided evidence of how Lee Harvey Oswald murdered John F. Kennedy. And did any copyright owner decide to follow up on this dismissal by modifying one of the free software BitTorrent clients to get it "certified as an evidence gathering tool"?
The camera cannot change, say, the face of the suspect.
Then perhaps you aren't aware of "fake smile" or "big eyes" gimmick effects in some modern digital cameras.
Same for a tape (or digital) recorder - it cannot alter the conversation recorded
Mind explaining what's on that 18 1/2 minute gap of the Watergate tapes? Now shorten the concept to silencing individual words, and then look at how YouTube Poop artists have perfected the art of sentence mixing.
And recently the loudest anti-piracy person (the manager of the agency) was caught with illegal drugs
What's the reason for banning drugs in the first place, other than racism?