Google to Open-source VP8 for HTML5 Video
Google will soon make its VP8 video codec open source, we’ve learned from multiple sources. The company is scheduled to officially announce the release at its Google I/O developers conference next month, a source with knowledge of the announcement said. And with that release, Mozilla — maker of the Firefox browser — and Google Chrome are expected to also announce support for HTML5 video playback using the new open codec.
Google has controlled the VP8 codec ever since it finalized the acquisition of video codec maker On2 Technologies in February. When reached for comment as to its plans, a Google spokesperson told us the company had “nothing to announce at this time.”
The move comes as online video publishers are gravitating toward standards-based HTML5 video delivery, bolstered in part by the release of the iPad. However, that acceptance has been slowed by the fact that the industry has yet to agree on a single codec for video playback, with some companies throwing support behind Ogg Theora and others hailing H.264 as the future of web video.
Google’s YouTube, Microsoft’s Internet Explorer 9 and Apple — through its iPad, iPhone and Safari browser — have all thrown their weight behind H.264, which many believe provides superior picture quality and playback to the Ogg Theora codec. However, a few organizations — including Mozilla — refuse to support H.264 due to potential licensing issues. Whereas Ogg Theora is completely open source, the H.264 codec is managed by licensing body MPEG LA. Even though MPEG LA announced in February that it was extending its royalty-free licensing for web video using H.264 through 2016, that was little consolation for Mozilla and others that are committed to supporting open standards.
The result is a divide between which video format can be viewed in which browser. H.264-encoded HTML5 video can be viewed in Apple’s Safari, Google’s Chrome and in the upcoming Internet Explorer 9 browser from Microsoft. Meanwhile, Ogg Theora playback for HTML5 video is supported by Firefox, Chrome and Opera.
Google hopes to stem that divide by making VP8 open source, providing a high-quality and open alternative to existing codecs. On2 first announced VP8 in late 2008, promising more efficient video compression than other available codecs. At launch, On2 went so far as to claim that it could provide “50 percent bandwidth savings compared to leading H.264 implementations.”
Google’s plans to open-source the codec have been widely expected ever since it announced plans to acquire On2 in August 2009, and speculation intensified after the deal closed. The acquisition even led the Free Software Foundation (FSF) to urge Google to kill Flash by open-sourcing the VP8 codec.
While an open-source VP8 could end concerns about H.264′s licensing issues and Theora’s quality, questions still remain about whether Google can provide a video standard on which everyone can agree. Microsoft only recently announced support for H.264 for HTML5 playback, and has never been quick to adopt open standards. And Apple, which has been the driving force behind HTML5 video and H.264 playback on the iPhone and iPad, might not be keen on the idea of switching up its codec support on those devices anytime soon.
Related content on NewTeeVee: Google TV: Another Reason Open Sourcing VP8 Matters
Related content on GigaOM Pro: What Does the Future Hold For Browsers? (subscription required)
Wow, that is pretty major. I did not think Google would actually go ahead with making VP8 open source, but it will surely have a big impact.
Nonetheless, major questions still remain. How good will VP8 actually prove to be in widespread application? Will MPEG-LA make good on their threats to enforce H.264 patent claims against Ogg Theora now that it could be a real contender? Can an improved Ogg Theora really do anything at this point to slow down the momentum of H.264 adoption in hardware?
It will be very interesting to see.
This seems like it’ll only be really great news if hardware acceleration, specifically for mobile, also comes with it. That seems to be where the biggest news in video is these days, and that’s where there’s a HUGE uphill struggle against h.264. Apple’s got to get on board behind this codec as much as Google may be.
If it came down to a scrap between Apple and Google, on past form I really wouldn’t fancy Apple’s chances.
Hardware acceleration is overrated, and the whole discussion about low end devices is a bit pointless, considering that each handset nowadays is a lot faster than bleeding edge PCs 10 years ago. As long as Moore’s law remains intact and batteries are advancing at same speed so far, there is no real need for hardware accelerated VP8. The Apple fanboys always tried to spread this hw accel fud in order to have an excuse for h.264…
All video decoding on consumer electronics and smart phones has got to be hardware accelerated. It’s not just a processing issue, it’s also a power consumption issue. Dedicated hardware acceleration for video is the only way to decode and encode 1080p with under 1W of power consumption, perhaps even lower than 0.5W power consumption. Which is amazing considering an Intel powered Desktop PC consumes often over 100W in power consumption.
I think Google must be planning the hardware acceleration accordingly and provide free codecs for that to all manufacturers of consumer electronics.
It actually is a big deal, because video at the quantity of Youtube can’t just be turned around and scrapped. Youtube has contractual deals to uphold H.264 videos with not only Apple and the iPhone, but also Tivo and a whole class of set top boxes. I’m sure such deals are for a reasonable lifetime of the product.
I don’t think anyone is trying to make an excuse for h.264. It’s currently the best of line codec. Outside of Apple, it’s pretty much the standard that most all professional videography toolchains are based on. It’s built into Windows 7. A vast bulk of consumer camcorders support it natively. It’s one of the premiere codecs supported in Bluray. It’s supported in Flash. And many of those devices do have hardware acceleration as a major benefit. Like it or not, the industry has settled on H.264, even if the web hasn’t.
I’ll be first in line to start supporting a royalty-free and license-free codec that’s not h.264, given that it meets or exceeds the quality bar set by h.264. I’m looking forward to it. I think that’s a powerful and wonderful incentive for an open web, and I’m thrilled at the possibility. But everyone’s got to be on board with it, including Microsoft and Apple. Otherwise, it’s not an open standard. It’s an open political grandstanding game, which is where we find ourselves now with Theora vs. H.264. Right now, H.264 happens to meet more of those needs than anything else. Time will tell what VP8 will become, and I’m excited to see it become something important.
@garbeam: You obviously don’t understand hardware acceleration and its importance for the new generation of low-end devices (netbooks, smartphones, etc.). @Charbax: CUDA and OpenCL will fill that gap real quick, trust me. @Kenneth Pardue: No one cares about Microsoft’s opinion. They only follow the current trend. Apple and MPEG-LA are the only ones that can pose a serious barrier, but 2 against the great majority of video-on-the-Web players? No royalties until 2016 vs. no royalties FOREVER? A total curbstomp.
@Kenneth, your definition of an “open standard” requires Microsoft and Apple to be in on it?? I don’t think that would fly with the ISO…
I’m not talking about ISO sanctioned standards, I’m talking about practical standards. If Apple and Microsoft aren’t on it, then it’s not standard for the web. I haven’t used Internet Explorer for nearly 6 years and rahter loathe it, but I do still recognize that they’re 60% of the market. Firefox+Chrome is what, 28%? Like it or not, that’s significant.
Ah. Then the sentence should’ve been “otherwise it’s not a de facto standard”, not “otherwise it’s not an open standard”.
It’s an important difference.
I spoke to a few of the Theora people at Libre Planet and asked them about hardware acceleration since apple/h.264 fanboys always seem to bring it up. They indicated that there’s nothing stopping someone from hardware accelerating Theora, companies just aren’t doing it.
Considering that many of the mobile devices aren’t using specific hardware and using advanced DSP’s to do the decoding (Each and every one of those iPhones and Android phones don’t HAVE dedicated h.264 hardware, they’ve got a TI DaVinci class DSP in them (Anything with an OMAP2/3 that does media has one…)) this is a specious argument. Much of the space doesn’t do dedicated h.264 or MPEG2 hardware except at the low-end of the spectrum- mainly because they’ve got so many differing tasks that it’s actually cheaper to just use a DSP on the SoC.
This is big. The release and success of this open-source codec could potentially kill Ogg Theora.
Was Ogg Theora ever alive?
It never got any major attention, and if it weren’t for Mozilla backing it, it would have remained in the dark.
This is Ogg Theora 2.0 basically. Ogg Theora is based on On2 VP5 codec, Ogg Theora 2.0 would be based on the On2 VP8 codec.
Just wanted to correct a slight error there, Charbax. Ogg Theora is based on On2 VP3 codec, not the VP5. VP3 was released to the public domain back in 2002.
I totally agree with you that the open-sourcing of VP8 won’t be the end of Theora since I’m sure they’ll take the code and build on it like the built on VP3.
Yes, implementing VP8 as Ogg Theora 2.0 would be an excellent idea.
One of the websites that use Ogg Theora the most is Wikimedia Commons. It is the only video codec allowed there.
Uh… You DO realize that this is merely the latest generation in the class of codecs that Theora came from, namely VP3?
Good. To me, this has two potential, positive outcomes for the majority of the “netizens”: killing Flash on the web-based video/audio playback scene, and making Theora useless in favor of something better (and everything is better than Theora).
Are you sure? Don’t come with your lame affirmations if you do not prove. You must be a very biased person or very frustrated. So sorry about you thinking.
Wow, you really showed him how to post a reasoned and fact-based past. It could have shortened to “So’s your face.”
MPEG2 isn’t.
“Microsoft only recently announced support for H.264 for HTML5 playback, and has never been quick to adopt open standards.”
Adopting an open standard like the HTML5 video tag is the hard part. Plugging in additional codecs is probably a breeze.
This likely doesn’t have to be an either or for any browser maker.
Flash didn’t drop Sorenson Spark (h.263) when they added VP6 and they didn’t drop VP6 when they added H.264. Flash also contains a Screenshare codec that is much lower quality than any of those others but is still extremely efficient for screencasting.
The same holds true for audio. Speex isn’t nearly as high quality as AAC, but it’s got size and latency advantages that make it kick AAC’s ass for VoIP. And guess what? Flash includes both.
Different codecs have different quality, size, and cpu features. No one codec will solve every problem and the overhead of carrying an extra “free” codec is minimal.
Microsoft should just add Theora and VP8 to their H.264 plans. Apple should follow suit.
“Plugging in additional codecs is probably a breeze.”
Technically yes. Politically ? That too a google OWNED standard ? Will Big Apple Brother ever look above the spite ?
Just because something is open source doesn’t mean it’s free from patent issues. What does the mpeg-la say about VP8?
Plus, if Apple doesn’t support it then it doesn’t really matter. Seems like everything will be h.264 no matter what anyone else tries.
Joe.
This is the key point. h.264 can be “open source” too — there are reference implementations, and of course x264. It’s the patent licensing that hinders adoption, not the unavailability of source code. With h.264, the patent costs are high but knowable (at least for the next few years). Ogg Theora may be unencumbered by patents, but until it’s adopted by someone with deep pockets who would be a good target for a patent troll or MPEG-LA, its patent status is uncertain. As far as VP8 goes, we’ll have to see how things unfold in terms of patents.
That, my friend depends on a handful of things.
VP3′s been about for a while. VP8′s not been so much so, but enough for what I’m going to get to here.
If you delay on dealing with an “obvious” infringement, you risk not being able to enforce against that specific infringer. The term in legalese is “Laches” which is latin for delay. Just because it might be covered, doesn’t mean that MPEG-LA, or the rights holders they represent, can enforce against the implementation at this time. It’s definitely too late for them on Theora’s score- years have passed and no court will buy they didn’t know about it. VP8 might have issues, but equally unlikely as the key pieces are under their OWN patents, just like VP3 was.
Out in the open and nobody’s spoke up. If it’s long enough (and it has been for Theora and most likely with VP8 as well)- that spectre has no force whatsoever.
Now, Apple can do what they so choose- but if YouTube doesn’t go with h.264 and goes with VP8/Theora, then there’s LITTLE that Apple can do about that other than cut their nose off to spite their face.
Very cool. However, it’s my understanding that it’s going to take quite a few years before hardware will provide efficient decoding for VP8 as found in H.264. Mobile devices with slow CPUs depend on using hardware accelerated video. Also HTML5 video on Safari on a Mac, HTML5 video on IE9 and Flash Player 10.1 (only on Windows right now) all get smooth HD video playback thanks to using the GPU. In all 3 cases they can use the GPU because there’s a H.264 decoder in the hardware. It could take a few years for VP8 to be offered in hardware to get that same GPU performance found with H.264 and then the wait for people to upgrade their hardware.
Much of the “hardware” decoders are DSP cores programmed to do the task. Each and every one of the “media” or “smart” phones utilize a DSP on their SoC to do the video and audio decode tasks. Ditto much of the media players. It’s cheaper and easier to support multiple codec formats (MP3, WMA, MPEG1/2, MPEG4, h.264, etc- they’re all differing in what “hardware” really means- unless you use a DSP and do the “hardware” in a specialized stream processor.) with a DSP than doing it with discrete parts. There’s component aspects that might lie within the GPUs of desktop machines, but in truth, you can just as easily (and they’re beginning to do it in the Linux space…) dedicate a GPGPU thread or two to doing DSP work- and do it there as well.
“Lack of hardware support” is more of an excuse than much of anything else- it’s not valid for a large range of devices that this would be relevant for, including all those iPhones, Droids, etc.
I did a blog post on the history of H.264 and this potential outcome.
Was this the rationale for the On2 acquisition to begin with?
Can we stop conflating IP and Open Source?
Just because a company releases the source to something doesn’t mean they have licensed all players to use the IP that protects said source code.
The problem is that this codec has the same problem as Ogg: no hardware decoder.
Without that, mobile phones have to use power hungrgy CPU, or fail due to lack of power.
Note that Google is supporting Theorarm (an ARM code optimised version of the Theora codec): http://google-opensource.blogspot.com/2010/04/interesting-times-for-video-on-web.html
Again… Most of the “hardware” decoders you see aren’t in hardware, but utilize a separate DSP dedicated to the task of handling decode. Seriously.
And it’s not hard to have “hardware” assist even from desktop GPU cards in the form of a GPGPU thread or two doing DSP stream processing.
Google have a long and stony road ahead of them. Just open sourcing VP8 isn’t all that is required, as earlier discussed in http://blog.gingertech.net/2010/02/20/googles-challenges-of-freeing-vp8/ . But they can get Apple and Microsoft behind VP8 if they approach it the right way – that’s the crux of the matter really. It will take time, though.
VP8 IS NOT ogg theora, nor an improved version of it. VP8 is a NEW codec. With google’s push on it, it’ll become number 1 codec probably in about 2 years. I’ll be good for all of us. Thank you Google. I thought you weren’t listening to your users, but i was wrong. God save the google!
Here’s a note from On2′s website:
“A major VP8 design goal was to simplify the decoding process for one of the world’s most ubiquitous microprocessors: the ARM 9. To that end, we invested considerable development effort in producing a decoder that would work well for ARM.” (http://www.on2.com/index.php?605)
So it seems that this may not need dedicated hardware decoding, as some commenters have worried above.
The link you provided mentions how great VP8′s decode is, apparently better than H.264. So it does have a hardware decoder and hardware companies need to start including the decoder in their hardware for software companies to start using hardware accelerated video. For mobile devices, it’s not just important for smooth video on low-end CPU’s but also for battery usage. For desktop machines, it means playing HD video really smoothly with very little CPU.
Thanks, that helps me understand the overall situation a bit better. So given the high turnaround rate on mobile devices (especially), could these decoders conceivably show up next year? At least, assuming that several browsers’ support can be scrounged up first..
“There is no hardware decoder”, “What does MPEG-LA has to say”. Why does MPEG-LA have to sign off on anything. Last time I checked, this was VP8 made by ON2. If MPEG-LA had an issue with VP8, it would have done something by now. The same goes for OGG/Theora. And the fact that Google is releasing the thing OSS, says a LOT. An organization with a law team the size of Texas won’t stick its neck on the line unless it was sure.
There were no h.264 hardware support when h.264 first was released. If VP8 decodes better than h.264 on a plain processor, then there is a little reason to worry about hardware support in the short term.
Mobile devices and a growing number of desktop browsers and Flash are providing better performance with H.264 using hardware decoders. Users aren’t going to want to take a step back, with choppy video on mobile devices and netbooks, while it drains their much battery faster because video is all on the CPU. Desktop users see lower CPU and great playback for wonderfully high def video files.
Also the benefit of H.264 codec is that it can be used for mobile devices supporting the HTML5 video tag and also the Flash Player, for desktop browsers, a majority of which don’t use browsers that support the HTML5 tag.
“drains their much battery faster because video is all on the CPU”
Begging the question, aren’t we?
Ahem…
All one has to do is write a decoder for the codec for the specific DSP the platform is running. There isn’t any magic special “hardware” decoding on the iPhone, Droid, etc. In the case of those specific phones there’s a TI DaVinci class DSP or Qualcomm’s equivalent in the SoC doing the task.
Please, stop using this as a line of thought- it’s NOT at all correct.
Much of the MPEG4 spec is based on Apple’s work on their current Quicktime technology. There’s a lot of work from Apple in the spec, so I don’t think Apple are anywhere near adopting another codec that’s not h264. By the other hand, ON2 was the company Sun Microsystems made a partnership with to bring a good quality video codec to JavaFX. I wonder how things are going to be now that Sun’s been absorbed by Oracle and ON2′s been absorbed by Google. Do they will honor the previous Sun/ON2 agreements? Well, if the VP8 codec is released as OSS then JavaFX is going to be quite benefited with the ARM port. Or is it Google thinking on getting JavaFX to Android? Just imagine… Android TVs (I saw one of those already), TVs with JavaFX on it (I remember Sony on the last JavaOne conference before the Oracle take over.
“Much of the MPEG4 spec is based on Apple’s work on their current Quicktime technology. There’s a lot of work from Apple in the spec…”
I would like to see a citation for that. And by “MPEG4″ do you mean MPEG-4 AVC (i.e. H.264) or do you mean all the MPEG-4 levels? I’ve never seen anything that broke down what percentage of the H.264 royalties Apple can claim.
Here you go
http://www.apple.com/quicktime/technologies/mpeg4/
The .mp4 container format is a modified version of the .mov format.
No one said anything about royalties.
The link provided by Grover Saunders does not say what you think it says. .mp4 is a container format for MPEG-4, and that is what the article claims was based on Quicktime. It makes no claim about Apples percentage of IP in the much more important MPEG-4 AVC codec. That’s what would be interesting to see.
The issue is not just what the Web or tech companies support. There is a hardware H.264 decoder in every consumer electronics device because it’s the ISO standard. Camcorders make it, iPods play it, video editors edit it, video encoders all encode it. H.264 is essentially a disc-free DVD. It is also the video that’s wrapped up in Flash. YouTube and iTunes are made out of it. It’s in PC GPU’s, it enables netbooks and set-top boxes to play HD video. Smartphones and iPods only play H.264, they do not have PC-style huge CPU’s.
It’s great that Google did this, because it means H.264 will likely remain free of charge for use on the Web after 2016 (it’s already free until then), but VP8 is not going to replace H.264.
Considering that most of that gear actually doesn’t have dedicated hardware but rather DSPs (because they need to support much more than just h.264 and it’s not the same tasks for MPEG1/2 or MPEG4 (and you’d need special silicon for each of these, and gear shifts for them to select, etc…)- it is MUCH less of a concern than you’d think. Seriously.
VP8 may be used for high resolution movies on Youtube and H264 for crappy resolutions. That means mobile phones will see an acceptable quality but the Ipad w/o VP8 will not.
Apple’s Safari is credited with 4% or 5% of the browser market as of April 2010. I don’t see why Apple’s opinion should matter that much.
85 million iPhone OS devices. Apple has over 65% of the share for mobile browser usage, and Apple won’t support a codec that doesn’t have a hardware decoder.
Considering that they don’t use a “hardware” decoder but a DSP on the iPhone…
Your numbers are WAY off. Apple may still be #1 browser usage, but that’s sitting at a whopping 42% with Android (Google) second up at 40% and gaining like a freight train running down a family of retarded gophers.
And be aware that 85 million is a very misleading number. That number includes ALL of the devices that have spontaneously self-desctructed, all warranty replacements, all devices destroyed by act of accident, worn out, owner HATED it (with good reason), obsolete, etc.
The ONLY important number is HOW MANY ARE USED REGULARLY? — and that number will be MUCH lower than 85 million.
If I were Google… at this point, I’d drop H.264 support in Chrome… then you have Firefox and Chrome ~ 31% of the browser market supporting a royalty free codec = VP8. Convert all of YouTube over to VP8… double whammy! If Google wants this to be the default codec for all of us, it WILL happen and teh microshits and fupples cant do anything about it!
31%?
Firefox is at 46.2% by itself. Combined, Firefox+Chrome make 58.5%.
http://www.w3schools.com/browsers/browsers_stats.asp
(note: you can argue against the numbers I present as much as you like. Just be aware of this: YOUR source is no more credible and therefore every argument you use against MY numbers ALSO applies against YOURS.)
Die Adobe Flash, Die !
The problem is that VP8 doesn’t look as good as H.264.
I’m also willing to bet that H.264 will be license free forever. MPEG LA should just get it over with now, and commit to it. They know they will have to at some point.
Actually, you’d lose that bet.
They’ve not done license free on anything else indefinitely- there’s always been someone come a knocking for their money on anything the MPEG group has fielded- at least as long as the patents were valid.
Yes, that is the problem. VP8 doesn’t look as good as (x.264 encoded) H.264. x.264 is just the best encoder right now, and getting better all the time. VP8 isn’t implemented in any hardware, whereas H.264 is decoded in hardware by all iPods, iPhones and many other devices.
Uh, you do realize that most of the “hardware” decode of h.264 happens to be done in DSPs?
Frank Earl: Would you please drop dead? This nonsense you are spewing is totally incorrect.
DSP is an EXTREMELY general term. IT DOES NOT INDICATE whether the device can be used for general processing, or whether it is or is not PROGRAMMABLE.
In general, the DSP used in any particular device for decoding video (like H.264) is NOT GENERIC. That means that you CAN’T REPROGRAM IT to decode a new kind of video!!!
Which IS one of the strengths of another option you have mentioned; SHADER BASED DECODE ACCELERATION (regardless of whether it is implemented directly [preferred] or through GPGPU as YOU seem to like).
HOWEVER programmable shaders are only useful for a SUBSET of video decoding stages, NOT INCLUDING THE EXTREMELY TAXING CABAC STAGE of H.264 decoding. CAN YOU SAY FOR CERTAIN that VP8 doesn’t have something like CABAC that won’t play nicely on programmable shaders?
DID YOU KNOW that programmable shaders are power hungry monsters right up there with CPUs? For example, nvidia’s latest flame thrower draws HUNDREDS OF WATTS — MORE than any CPU I’m aware of!!! Look it up if you don’t believe me.
What is your source? I can’t find any third-party quality comparisons involving VP8. The only comparison I could find was On2′s own comparison (possibly biased), where VP8 comes out ahead of x264-encoded H.264.
http://www.on2.com/index.php?603
In fact, I am unable to even find any publicly-available VP8 encoders, decoders, or videos, making me wonder what you base this on.
From what I have seen, VP7 was at least close in quality to that of H.264 to the point that differences would be barely noticeable to most people, so I would not be surprised if VP8 surpassed current implementations of H.264. (Unfortunately, I can’t find any independent comparisons involving VP7, either, despite the fact that the codec is available.)
Quite frankly, I could not be more happy about this. Anything that could bring death to Flash has me smiling broadly.
Whether the end winner will be VP8 or H.264 is not really the issue here but the fact that both will be open and free (Libre). Whichever wins, Proprietary Codecs lose and that can only be a good thing.
Will be interesting to see how this pans out and what strategies will follow to boost the respective market share of these two. As long as the consumer wins, I will be happy.
I’ll take the option that flies in the face of MS any day. If THEY like it, there MUST be a REASON, and you can bet that it will limit your freedom since that is the MS way.
Amazing. However, I think the critical point will be whether they switch YouTube over to VP8. Apple/MS may be reluctant to adopt open codecs, but if the primary video site on the web uses it, they’ll have to support it.
I have to say — if they switch OFF flash support on youtube, causing millions of 15 year old boys using IE to go nuts because IE7 and IE8 don’t support HTML5 and IE9 doesn’t support any decoder other than h.264, then by god, all they have to do is put a link to google chrome or firefox and bam! the userbase of these browsers should skyrocket (faster than it already is).
Uh, no.
Millions would simply tune out of YouTube because it no longer works.
There are simply too many options on the web.
So in the (near) future if we want to publish video on the web without using Flash we would need to encode two files: one H.264 and one VP8. Then using detection we could switch the url depending on the browser, but the UI/player can remain the same.
It’s two steps forward (no more Flash, jay) and one step back (two codecs remain).
I say let’s go for it!
No, all you would need to do is support STRICTLY VP8! If the user’s browser can’t deal with it, tell them their browser maker is wrong and is intentionally limiting their rights, and refer them to a REAL browser (and give more than one option so that you don’t appear to be taking favorites).
The “die Flash” comments don’t seem appropriate – especially in this context. If you want almost everyone to be able to view VP8 encoded video in the near term, the best way to accomplish that would be to ask Adobe to build it into the Flash player. In little over a year it would be available to almost everyone. We’ll see what Google announces at Google I/O.
Yup, logically Adobe will include VP8 “Ogg Theora 2.0″ in Flash, just as they include VP6 in Flash at the moment.
Definitely NOT a good idea to use flash.
First off, you will note that flash is NOT a video player. It is a CPU hungry murderer of small children and furry animals. Videos to be handled by flashplugin are NOT just video files — they have to be packaged SPECIFICALLY FOR flash.
A more intelligent method of distributing videos is DIRECTLY IN THE EMBED TAGS.
EMBED SRC=”path/to/videofile.extension” HEIGHT=heightpx WIDTH=widthpx
And that’s all it takes. ANY video player plugin (like mplayerplug-in) will be able to handle ANY video in ANY package embedded in ANY HTML like that.
It is just as easy to add a browser plugin that handles strictly embedded videos as to install a flash player.
It is also much more freeing to use a generic video player plugin. For example, you can use the mplayer-plugin with a mozilla browser to provide H.264 AND VP8 embedded video support RIGHT NOW!!!!
Just drop your video file (literally ANY kind of video file) into an embed tag RIGHT NOW, and the mplayer-plugin will handle it. No need for messy CPU and MEMORY hungry and crash prone adobe garbage.
The objective of this video tag is to build STANDARDIZATION into the BROWSER’s ability to play videos.
That means DITCH the adobe!
In the spirit of Apple’s latest licensing decisions, I think Google should explicitly prevent Apple from making use of VP8. It’s not evil if they hold Apple to their own standards, and as Apple pointed out – all the brouhaha surrounding them recently is strictly about standards.
If Opera, Firefox and Chrome all went VP8, and Youtube went that way too, then Safari and IE would have no choice but to adopt it.
There is no doubt about Opera, Firefox and Chrome including VP8 if it is opened. The true question here is Youtube. Is Google dedicated enough to this opening to transcode their petabytes of H.264 videos ?
You don’t think that google has enough processing power? You don’t think that google transcodes ON THE FLY? You aren’t actually of the opinion that the various “quality” settings refer to distinct files stored on their servers, do you?
No, of course not.
Google very likely stores their videos RAW and transcodes them to whatever format they need at the moment.
“The result is a divide between which video format can be viewed in which browser. H.264-encoded HTML5 video can be viewed in Apple’s Safari, Google’s Chrome and in the upcoming Internet Explorer 9 browser from Microsoft. Meanwhile, Ogg Theora playback for HTML5 video is supported by Firefox, Chrome and Opera.”
Guess what? Google wins in any case. :) :)
I think that HTML5 video will win because it is both for browsers and mobile. I agree with Mark that if this new Open Source Codec allows cost savings for youtube, Google will push it and make de facto a standard.
Cost savings for youtube must be a great issue when you think about the TB they stream every single day !
can you reveal your “multiple sources” of this news?
No. Then they wouldn’t be sources.
This is terrible news from the content providers perspective. All we need is another CODEC to deal with! Pick one for the love of god! I am inclined to go with an ISO standard owned by a consortium as opposed to an open source product that is owned by 1 company. Plus H264 has a lot of traction not just in the web browser sphere, but also in mobile and the entertainment industry. (Blu-ray Disc, HD, iTunes video, IPTV, etc)
Now if browsers supported more than one CODEC through HTML5 THAT would be awesome.
The problem is that they WON’T. They WILL NOT be able to agree on a standard. MS will ALWAYS be the problem (apple isn’t big enough to worry about). Even if the standard is defined, MS will NOT ACCEPT IT unless THEY were the ones to “decide” (aka IMPOSE) the “standard”.
What this basically means is this: everyone will decide on VP8, but MS will use H.264 despite this.
This would have been a problem a few years ago, but MS doesn’t have the sway they used to have. Google is stronger than MS now. At least in terms of the web.
Take my word for it: If GOOGLE decided to force VP8, they COULD.
The only problem is that they may not be willing to force it. It would be a SERIOUS gamble for them. Not regarding whether or not the COULD force it, but what it would mean in terms of public perception of google — “don’t be evil”. And although it would most definitely NOT be evil to force people NOT to use H.264, the big question is whether the really really REALLY stupid people who live on this planet would be capable of understanding this, or whether they will buy into the MS-lies.
I believe that google will most likely NOT force it.
Which is why VP8. If the IP is licensed under the same terms of VP3 used in THEORA, then it will satisfy MOZILLA while being able to COUNTER the complaints about THEORA.
Previously, it was H.264 against THEORA — they both had points in their favor: H.264 had quality in its favor, THEORA had IP in its favor. Neither was able to win out. If VP8 has H.264 quality with THEORA IP…. then that would be a hard one for MS to counter with any kind of logical argument. Which will hopefully make them look real stupid when they ultimately insist on H.264 despite having NO supporting logic.
Please come check out some of my recipes and story @ http://www.mogarlic.worldpress.com
This is GREAT news. Finally, we can get beyond the ripoff pricing (if you are anyone but a nobody, it’s expensive as hell) and MPEG-LA death-grip control on H.264, and the “meh” quality of Theora. Since the Android/iPhone type of device turnover rate is under 2 years of use average, it’s laughable to hear people suggest hardware decoding is even in issue. This isn’t system-on-chip stuff folks, but simple programmable DSP’s that could easily add VP8 decoding….we could see VP8 take flight in a couple of months if done right, and pushed by Google.
Man, there sure seems to be a lot of armchair quarterbacking in these comments. Here’s one thing: if anyone tries to force any codec, it’s going to make the web a worse place. Just because a codec is open source doesn’t make it any more right for one company to force it down anyone’s throats, regardless of its quality. And it sure doesn’t make it right for a company to deny another maker access to the codec. That would put us right back in the land of Windows Media and Quicktime in the first place. If any one vendor, regardless if it’s Apple, Google, Mozilla, Microsoft, or Opera, regardless of market share, decides to not be on board with a given codec, that’s enough to make it unacceptable. The web is not a zero sum game.
The best course of action is to wait until Google themselves announces their intent for VP8. It’s probably too far along in the development cycle for any of the major browsers to incorporate support for it in the upcoming versions anyway, even if they wanted to.
http://veritastoday.wordpress.com/
YouTube is the potential stick. Imagine if Google announced that it was going to phase out support for Flash and H.264 on YouTube.
Google does not have to force anybody to do anything.
Browsers should use codecs installed on the users machine if the browser doesn’t support it natively. Although, people might abuse that by using all sorts of other formats.
I hope Google Merge the VP8 into MKV !!! Thats the best Container yet for making the best viewing experience…
Thanks Google I Love YOU
With so many codec available in the Internet, I’m not sure how VP8 is able to take over some of them. For example DivX is unique in its own way, but VP8 is just another video codec, which is not going to make much of a difference, except that 1) it is developed by Google, and 2) the name sounds good.
One important question for the adoption of VP8 is still open, the question of licensing intellectual property (IP) related to the codec:
Would Google agree to royalty free (RF) licensing of related IP they obtained with this acquisition to all browser and tool manufacturers, whom they want to include the codec? Would they agree to RF terms also for content producers?
Would any third party owning related IP agree to the same?
How to ensure all the owners of related IP and their terms are know? With other words, how to calm the fear of submarine patents?
As long as it works in IE6 I am all for it.
You got youtube. And open source vp8. Put them together. Win the h.264
guys, the vid codec battle was decided long ago. h.264 is the winner. although i support open standards, audio+video on the desktop and the cloud is dominated by encumbered codecs. the inertia is already very high and cannot be tamed – it’s too late.
It’s scary to think this issue even existed in the first place. The root problem is that proprietary codecs were going to be part of web standards, something that should be prohibited by policy. The very foundation of the web is based on free and open standards, and policy should shape industry, not vice versa.
:):):)
This VP8 story is already old. Remember the claims in terms of Video Quality vs H.264, that no one has EVER been able to checkin dependantly. Second this MPEG-LA discussion which seems to be settled until 2016 for web (free) content. Then there is this $130M acquisition from Google, everyone was puzzled, and we start to see some more clarity. BTW there are good blogs on the subject, check this one : http://www.zeropaid.com/news/88655/google-providing-focus-to-future-of-video-online/ Google is clearly looking at several things : secure its encoding future and cut the cord with the Adobe/H.264 technology. This is what they have achieved with HTML5/VP8. Now in addition to that On2 had acquired Hantro an embedded Mobile phone codec company. On the desktop side Google will challenge Microsoft/Silverlight and Adobe/Flash with their HTML5/VP8 pair. Of course this has to be supported by the 2 enemys’ browser, if not go and download the Chrome one! As always if content is worth, people will download a new (Chrome) browswer, so expect Google to make soon a move on attractive content. On the TV side, we have read this Google TV rumor where Google is working with Sony on an Intel CE chip set that can decode VP8. The problem is this type of technology is (still) costly and can not compete with Roku type of device (based on H.264…. Google anyway needs this CPU power to run its SW stack, so cost is already justified. Will this fly, well this is actually an Apple TV + apps, so I tend to think there is some value. If you put boxee SW stack on top of it, you might be close to the TV 2.0 galaxy…. Last but not the least, the Mobile space. VP8 has been designed with ARM in mind, but more of power efficient implementations on Mobile phone use native HW acc (for H.264 for instance), so who is interested by a VP8 SW implementation, if it consumes more than an H.264 HW implentation?
Overall, this VP8 story is for me a mixed bag, will roll out in the PC space to start with, next will be Google TV, and long term it might play on Mobile.
When do the H.264 patents expire?
I tend to believe that Ogg (basically VP3 donated by On2 ) is dead meat.
VP8 (by the same On2 folks) is vastly superior , and from what I’ve seen it certainly matches H.264 in quality and in some cases makes H.264 look really weak.
Probably what will happen is that H.264 and VP8 will co-exist for some time and provided that Google gives it proper care and feeding, H.264 will slowly fade but never actually go away.
A large part of the issue has nothing to do with the Internet and much to do with various hardware devices , including set top boxes and hand held video recorders.
We’ll here a lot about submarine patents and such ,and maybe a few bogus court cases, but that will pass , as the H.264 crowd would cite submarine patents on a cheese sandwich if they thought it would keep hardware vendors from jumping ship.
I’ve been working with computers since before Apple or IBM made PC’s so I’ve watched a lot of these soap operas and the plots are hardly ever original.
The Internet was designed to survive a nuclear war, and is itself a global power. Unlike radio or TV , the Internet belongs to everyone and we should take care never to allow folks like Adobe, MPEG-LA or even back in the day Unisys to try and privatize any portion of it.
!ɯopǝǝɹɟ ʇǝuɹǝʇuı ǝʌıן ƃuoן puɐ ɥsɐןɟ oʇ ɥʇɐǝp
–Doc
makes sense, another play to secure mind share over buy in.
anyone know how in bed apple is with the MPEG LA group? must be a major stakeholder i’m thinking, otherwise he wouldn’t let them play in his walled garden.
The real problem is dinosaurs like ITU/ISO (the antiquated standards bodies of past centuries that glacially grind out telecom and broadcast standards like H.264) don’t require patent assignment or royalty-free licensing for their proposed standards like IETF/W3C (the modern standards bodies that govern the internet). Google should do more than just open VP8, they should push for video codec innovation to happen in IETF/W3C (or the open internet in general) rather than ITU/ISO.
Google I/O is almost here. Better this rumour is true, otherwise your credibility will be significantly affected.
Credibility = intact!
[...] http://newteevee.com/2010/04/12/google-to-open-source-vp8-for-html5-video/ April 12th, 2010 | Tags: Google, On2, opencu, opensource, VP8 | Category: streaming [...]
[...] Google to Open-source VP8 for HTML5 Video Google will soon make its VP8 video codec open source, we’ve learned from multiple sources. The company is scheduled to officially announce the release at its Google I/O developers conference next month, a source with knowledge of the announcement said. And with that release, Mozilla — maker of the Firefox browser — and Google Chrome are expected to also announce support for HTML5 video playback using the new open codec. [...]
[...] full post on Hacker News If you enjoyed this article, please consider sharing it! Tagged with: Google • [...]
[...] of course, Google has an altogether different idea. Share and [...]
[...] TV: Another Reason Open Sourcing VP8 Matters Google’s decision to open source On2 Technology’s VP8 video codec at its Google I/O developer conference next month is not only a huge boon for HTML5 web video and a [...]
[...] – CNET Japannewsing:1 Google to Open-source VP8 for HTML5 Video はてブ:8 Opera Mini Web browser – iTunes Storeはてブ:6 [...]
[...] a fan of all things open-source, I was happy to hear that Google is releasing their recently acquired VP8 codec as open-source. Even better, two of the most bitchin’ browsers around (Firefox and Chrome), are expected to [...]
[...] by WP Greet Box WordPress PluginSeveral reader noted Google’s reported intention to open source the VP8 codec it acquired with On2 last February — as the FSF had urged. “HTML5 has the potential to [...]
[...] Original source : http://newteevee.com/2010/04/12/google-to-open-sou…; [...]
[...] has up a posting announcing they have “learned from multiple sources” that Google will indeed be Open Source-ing [...]
[...] Read more Share and Enjoy: [...]
[...] es al menos lo que indican en NewTeeVee, donde han recibido la confirmación de varias fuentes, lo que sin duda parece revelar que [...]
[...] Google to Open-source VP8 for HTML5 Video [...]
[...] schönes Gerücht: Google to Open-source VP8 for HTML5 Video. Hoffen wir, daß es wahr [...]
[...] Laut dem Blog Newteevee plant das Unternehmen Google nach der Übernahme von On2 die Veröffentlichung des Codes VP8 unter einer Open-Source-Lizenz. Google hat dieses Gerücht jedoch nicht bestätigt und die Quellen dieser Information werden nicht benannt, sodass auch Zweifel an dieser Meldung bestehen. Auf der Entwicklerkonferenz Google I/O gegen Ende Mai 2010 wird die Entscheidung angeblich veröffentlicht. [...]
[...] Google liberara VP8 para HTML5 newteevee.com/2010/04/12/google-to-open-source-vp8-for-html5… por antxon.urrutia hace 3 segundos [...]
[...] heeft Google nu bekendgemaakt dat het de VP8 codec die het onlangs van On2 Technologies aankocht, opensource gaat maken. VP8 heeft net als H.264 een veel betere compressie dan [...]
[...] Google to Open-source VP8 for HTML5 Video [...]
[...] to this article on NewTeevee.com, they have learned from multiple sources, that Google will release the VP8 [...]
[...] Vía [...]
[...] decision to open source On2 Technology’s VP8 video codec at its Google I/O developer conference next month is not only a huge boon for HTML5 web video and a [...]
[...] While an open-source VP8 could end concerns about H.264’s licensing issues and Theora’s quality, questions still remain about whether Google can provide a video standard on which everyone can agree. Microsoft only recently announced support for H.264 for HTML5 playback, and has never been quick to adopt open standards. And Apple, which has been the driving force behind HTML5 video and H.264 playback on the iPhone and iPad, might not be keen on the idea of switching up its codec support on those devices anytime soon. via newteevee.com [...]
[...] On2 Technologies erhalten hat, soll von Google als Open Source freigeben werden. Dies berichtet das Blog NewTeeVee unter Berufung auf gut informierte Kreise. Google selbst liess bisher lediglich [...]
[...] it is now clear : google will open source the VP8 codec [...]
[...] is reporting that Google will make their plans for VP8 official at a developer’s conference next [...]
[...] on web-based computing and even traditional applications using web technology. NewTeeVee is reporting that Google will make their plans for VP8 official at a developer's conference next month. This [...]
[...] Source : NewTeeVee [...]
[...] Chrome are expected to also announce support for HTML5 video playback using the new open codec. Google to Open-source VP8 for HTML5 Video Bravo Google Sponsored Links: innity_pub = "0aa1883c6411f7873cb83dacb17b0afc"; innity_zone = [...]
[...] Newteevee.com is reporting that Google plans to announce VP8 video codec for HTML5 at next month’s Google I/O conference in San Francisco. [...]
[...] but extremely important movement to get an open video format into HTML 5. With Google’s recent move to open source VP8 this now looks like a reality and Flash’s dominance in web video looks certain to end soon [...]
[...] Google to Open-source VP8 for HTML5 Video Kevin: Interesting move by Google. They acquired the VP8 video codec with their acquistion of On2 Technologies in February, and now they plan to release it as open-source. Good post looking at new video codec issues around HTML5 and H.264 versus completely open-source Ogg Theora. (tags: 2010 adobe apple opensource html5 video web google flash h.264 codec) [...]
[...] because it would provide a codec that meets all the interested party's requirements. Just yesterday newteevee reports this might actually come to happen, and it should be announced at Google's I/O conference. [...]
[...] to Open Source VP8 Codec Posted April 13, 2010 By collin If Google goes through with taking the VP8 codec open source, it will almost certainly replace Flash for online video, as well as supplant Ogg Theora and quite [...]
[...] неофициальному сообщению от одного из работников Google, компания намерена [...]
[...] Simultaneously taking Ogg out back and putting one it’s ear and making the streaming video wars much more interesting. Gruber’s questions are my own: Will Apple or Microsoft support VP8? And will Google support it at YouTube? [...]
[...] [...]
[...] 我们之前报道过自由软件基金会催促Google如果能以不可撤销的买断免费授权来发布VP8编码并将其部署到YouTube的话，就可以结束互联网对flash的依赖。现在，Newteevee编辑从多个渠道了解到Google已经有计划要在下个月举办的Google I/O开发者大会上宣布开源VP8视频编码技术。届时，Firefox和Chrome浏览器都会同时宣布支持VP8编码的HTML 5视频回放。 [...]
[...] to a report at NewTeeVee, inside sources have confirmed that Google will be open-sourcing the VP8 codec next month at the [...]
[...] to a report at NewTeeVee, inside sources have confirmed that Google will be open-sourcing the VP8 codec next month at the [...]
[...] to NewTeeVee, Google will open the source code of On2 VP8, the capable video compression format, on the upcoming [...]
[...] to NewTeeVee, Google is stepping up to the plate. Google will soon make its VP8 video codec open source, we’ve learned from multiple sources. The [...]
[...] es al menos lo que indican en NewTeeVee, donde han recibido la confirmación de varias fuentes, lo que sin duda parece revelar que [...]
[...] Google appears to be open-sourcing the VP8 video codec. [...]
[...] Vía | NewTeeVee [...]
[...] Vía | NewTeeVee [...]
[...] to a report at NewTeeVee, inside sources have confirmed that Google will be open-sourcing the VP8 codec next month at the [...]
[...] article: Google to Open-source VP8 for HTML5 Video. This entry was posted in Required Reading. Bookmark the permalink. Post a comment or leave a [...]
[...] is breaking the news that Google will be officially announcing that it intends to open source the advanced VP8 codec [...]
[...] por medio de diferentes códecs. Y otra cosa, que en este juego, Google tiene la clave.Vía | NewTeeVeeEn Genbeta | Comparando el rendimiento de HTML5 y FlashLeer más aquí:Google liberará el código [...]
[...] Opera Mini for iPhone is Here Cyberspace Embassador Needed? Google Acquires Plink Google Open Source VP8 for HTML5 End for Microsoft Vista Facebook Safety Center Home Automation Using Apple Phantom Flex Camera [...]
[...] NewTeeVee reports that Google will soon open source VP8, the latest video codec released by On2, a company acquired by Google for $133 million. [...]
[...] Vía: NewTeeVee [...]
[...] para CPUs ARM del codec Theora. que se comentó ayer.» Como también comentaba wfox en su envío se hará publico en mayo en la conferencia de desarrolladores Google I/O y se espera que tanto Mozilla como Google anuncien [...]
[...] Google to Open-source VP8 for HTML5 Video Google (s GOOG) will soon make its VP8 video codec open source, we’ve learned from multiple sources. The company [...] [...]
[...] Google to Open-source VP8 for HTML5 Video – While an open-source VP8 could end concerns about H.264’s licensing issues and Theora’s quality, questions still remain about whether Google can provide a video standard on which everyone can agree [...]
[...] Google to Open-source VP8 for HTML5 Video (tags: codec video opensource) Leave a Comment [...]
[...] Nuevo pelotazo: fuentes cercanas a Google aseguran que estos liberarán finalmente su códec de vídeo VP8, desarrollado por la empresa On2 a quienes se lo compraron no hace mucho. “Bo, pues ya ves tú” estarán pensando algunos. Esperar que sigo. [...]
[...] Google to open-source VP8 for HTML5 Video >> newteevee.comWhich would mean you have H.264 (paid-for, widely supported), Ogg Theora (free, not widely supported) and VP8 (free, used by Google). And, of course, Flash. [...]
[...] Lawler at NewTeeVee.com gives a background on the politics and fights behind video codecs. He says “Google will soon make its VP8 video codec open source, we’ve learned from multiple [...]
[...] Éppen pár napja döntöttek úgy, hogy támogatják a Theora fejlesztését most pedig a hírek szerint úgy tervezik, hogy megnyitják a VP8 codec-et. [...]
[...] | NewTeeVee En Genbeta | Comparando el rendimiento de HTML5 y [...]
[...] more details at newteevee.com Tags: Google, HTML5 Video, News, Open Source, VP8 for HTML5 Video previous [...]
[...] Google to Open-source VP8 for HTML5 Video (tags: article technology google editorial) [...]
[...] On2, makers of a third, competing video codec. As NewTeeVee reported Monday, Google has plans to release On2’s VP8 video codec under an open source license soon. Both Theora and VP8 are promising, but it will be years before [...]
[...] appears that Google will open source VP8, the On2 codec at the event. Video has been painful for the Open Web crew. Many bash Theora on the grounds of [...]
[...] » Google to Open-source VP8 for HTML5 Video [...]
[...] Google to Open-source VP8 for HTML5 Video (tags: HTML5 opensource google VP8) [...]
[...] Mitte Mai ein großes Geschenk machen und damit gleichzeitig ein großes Problem lösen helfen: Nach Angaben von NewTeeVee will Google auf der Entwickler-Konferenz Google I/O den Video Codec VP8 als Open Source freigeben. [...]
[...] NewTeeVee Tags: Google | HTML 5 | On2 | [...]
[...] READ MORE… Comments (0) Trackbacks (0) Leave a comment Trackback [...]
[...] Google to Open-source VP8 for HTML5 Video By ericrycuny Google to Open-source VP8 for HTML5 Video [...]
[...] Ryan Lawler at Newteeve writes, The move comes as online video publishers are gravitating toward standards-based HTML5 video delivery, bolstered in part by the release of the iPad. However, that acceptance has been slowed by the fact that the industry has yet to agree on a single codec for video playback, with some companies throwing support behind Ogg Theora and others hailing H.264 as the future of web video. [...]
[...] Google to Open-source VP8 for HTML5 VideoAn open source, patent clean video codec would do a lot for the HTML [...]
[...] Google to Open-source VP8 for HTML5 Video – [...]
[...] newteevee se ha extendido la noticia de que Google liberará el codec de vídeo VP8 el próximo mes de Mayo. [...]
[...] via Google to Open-source VP8 for HTML5 Video. [...]
[...] Codec VP8, se espera que google libere el codigo fuente. [...]
[...] NewTeeVee, Google abrirá el código fuente de On2 VP8, el formato de compresión de vídeo, en el próximo [...]
[...] Via: NewTeeVee. Random Posts: New York City Gears up to Receive Tourists Nokia Cuts Jobs Coke and Pepsi Following Each Other on Twitter! Spotify Looking For A Spot In Apple Apps Store Keep your Brand Alive When Bosses Use Technology to Spy on their Employees Group Dynamics: Convergence + Resolution Advertisement Rates Soar as IPL approaches the Finals Counterfeiting of High-Tech Products Mc Donalds Japan Removes Brand Name from Menu! Consumers Greet Windows 7 With Jubiliation & Open Arms Twitter Finally Introduces Its Business Model In The Form Of ‘Promoted Tweets’ RSS Feed Subscribe by Email : [...]
[...] Google Just Kill Ogg Theora? Ever since we broke the news earlier this week that Google is going to open source its VP8 video codec at its Google i/O event next month, speculations have been abounded as to what this means for Ogg [...]
[...] Mai stattfindenden Entwickler-Konferenz Google I/O will der Suchmaschinenriese das VP8-Formt laut New TeeVee als Open Source freigeben. Gerüchten nach wollen Mozilla und Google den VP8 Codec in ihre [...]
[...] Lawler / NewTeeVee: Google to Open-source VP8 for HTML5 Video — Google will soon make its VP8 video codec open source, we’ve learned from [...]
[...] http://newteevee.com/2010/04/12/google-to-open-source-vp8-for-html5-video/ [...]
[...] Google to open-source VP8 for HTML5 Video >> newteevee.comWhich would mean you have H.264 (paid-for, widely supported), Ogg Theora (free, not widely supported) and VP8 (free, used by Google). And, of course, Flash. [...]
[...] since we broke the news earlier this week that Google is going to open source its VP8 video codec at its Google i/O event next month, speculations have been abounded as to what this means for Ogg [...]
[...] Google to open source VP8 for HTML5 video Let me see if I can break down why this is so big. Essentially all the videos we watch online right now have been created using a codec that is privately owned. A codec just encodes and decodes the video so we can watch it streaming beautifully online. Since it is privately owned, everyone was worried the company that owns it (even though they have provided a free license through 2016) might start charging to use it. So Google, having acquired another company with another nice video codec that could work on the web, decided to release it for free forever. This is big. [...]
[...] rumores do site NewTeeVee, provavelmente a gigante das buscas irá disponibilizar o codec VP8 sob uma licença Open-source no [...]
[...] but perhaps not surprising news that Google will make the VP8 video codec open source. You can read in more detail by following the link but here’s a quick rundown: Many [...]
[...] para CPUs ARM del codec Theora. que se comentó ayer.»Como también comentaba wfox en su envío se hará publico en mayo en la conferencia de desarrolladores Google I/O y se espera que tanto Mozilla como Google anuncien [...]
[...] other words, Google’s just leaked decision to release VP8 as open source and royalty free, in combination with YouTube’s more tentative [...]
[...] donosi serwis NewTeeVee, Google planuje wydać na wolnej licencji zaawansowany kodek wideo Truemotion [...]
[...] since we broke the news earlier this week that Google is going to open source its VP8 video codec at its Google i/O event next month, speculations have been abounded as to what this means for Ogg [...]
[...] NewTeeVee is reporting that Google is preparing to make an announcement concerning the VP8 video codec they recently acquired as part of the On2 technologies acquisition. NewTeeVee reports that according to multiple sources Google will make the announcement at next months developers conference, Google I/O. [...]
[...] On2. Eles são os responsáveis pelos codecs de vídeo que hoje estão no Flash e no JavaFX. O artigo cita fontes de que o Google I/O 2010 em Maio será o palco do anúncio: codec VP8 licenciado como [...]
[...] put a question mark there since this story currently does not cite any named sources, but NewTeeVee certainly seems convinced that Google will open source the VP8 codec, and will announce this at [...]
[...] Google to Open-source VP8?: http://newteevee.com/2010/04/12/google-to-open-source-vp8-for-html5-video/ [...]
[...] For Twitter” – Microsoft Visual Studio 2010 en Microsoft .NET Framework 4 beschikbaar – Google zal VP8 voor HTML5 Video Open-source maken – Nieuwe combo organ VSTi – Apple iAds mogelijk gevaarlijke tolboom mobiele adverteren Log in om [...]
[...] may be open-sourcing the VP8 video codec. Internet video is about to get a lot more complicated. Ryan Lawler reported in NewTeeVee that multiple sources have told him Google will be open-sourcing its VP8 video codec. This is a [...]
[...] an Open Source VP8 Overtake H.264? With the news that Google plans to open source On2’s VP8 codec next month, there’s been a lot of talk about whether or not it can emerge as the “one [...]
[...] Newteevee has shed light on the possible open-sourcing of the On2 video codec Google acquired earlier this year. Currently, H.264 and Ogg Theora are fighting to get the open-web standard. If this goes through, Google will introduce an unbeatable contender in the video codec race. Read more here. [...]
[...] Newteevee has shed light on the possible open-sourcing of the On2 video codec Google acquired earlier this year. Currently, H.264 and Ogg Theora are fighting to get the open-web standard. If this goes through, Google will introduce an unbeatable contender in the video codec race. Read more here. [...]
[...] past week, the internet picked up — and subsequently sprinted like a cheetah with — an unsourced and highly unsubstantiated rumor that Google will open source the VP8 video codec, recently procured through their On2 acquisition. I wager that the FSF is already working on their [...]
[...] Did Google Just Kill Ogg Theora?Google to Open-source VP8 for HTML5 VideoWhere to Watch the 2010 Coachella Music Festival OnlineTen Sites for Free and Legal TorrentsThe [...]
[...] http://newteevee.com/2010/04/12/google-to-open-source-vp8-for-html5-video/ [...]
[...] Video Stuff: H.264; patent licensors (i.e., owners); good explanation of H.264 by Apple; nice overview of the issues of HTML5 video over Flash and the possibilities if Google does toss VP8 in to open [...]
[...] selon le site NewTeeVee, Google envisagerait de rendre son codec vidéo Open Source à l’occasion de sa conférence [...]
[...] especula que Google podría anunciar pronto la liberación de los codecs VP8 bajo una licencia open-source. [...]
[...] “game” for Dev Mindshare/PR that includes Adobe and Apple… and Google… and NewTeeVee and ElReg reported that Google was going to OpenSource VP8, which I think will be a move very [...]
[...] Google to Open-source VP8 for HTML5 Video [...]
[...] Google liberará el códec VP8… ¿Hacia la desaparición de Flash? [...]
[...] Apr, 2010 Yahoo NewTeeVee reports that Google will soon open source VP8, the latest video codec released by On2, a company acquired [...]
[...] to a report at NewTeeVee, inside sources have confirmed that Google will be open-sourcing the VP8 codec next month at the [...]
[...] (not my sources, but NewTeeVee’s) say that Google is going to announce that they are making the VP8 codec, part of the On2 [...]
[...] NewTeeVee reports that Google will soon open source VP8, the latest video codec released by On2, a company acquired by Google for $133 million. [...]
[...] http://newteevee.com/2010/04/12/google-to-open-source-vp8-for-html5-video/ [...]
[...] Newteevee.com is reporting that Google plans to announce VP8 video codec for HTML5 at next month’s Google I/O [...]
[...] it seems like this part of his rant is really written with someone else in mind: Google is going to open source its VP8 video codec at its Google I/O event next month, and Jobs just let them know that he won’t accept a new [...]
[...] Group and the browser vendors will come together on a codec everyone will support. The rumor that Google will open source the excellent VP8 codec is potentially welcome news on that [...]
[...] instructions needed to turn a binary file into the moving images you see), such as the one Google recently announced will spur adoption rates and eventually push Flash off this hill. A number of major media players, [...]
[...] it seems like this part of his rant is really written with someone else in mind: Google is going to open source its VP8 video codec at its Google I/O event next month, and Jobs just let them know that he won’t accept a new [...]
[...] is also expected to use its I/O event to open source its VP8 video codec, and we shouldn’t be too surprised to see Google TV utilize VP8 as [...]
[...] it seems like this part of his rant is really written with someone else in mind: Google is going to open source its VP8 video codec at its Google I/O event next month, and Jobs just let them know that he won’t accept a new [...]
[...] flash successor called VP8. Faster Forward – Microsoft endorses a Flash video replacement Google to Open-source VP8 for HTML5 Video Reply With Quote [...]
[...] Theora and other open source codecs. That news comes just a few weeks before Google is expected to release its VP8 codec as open source, and could come as a big blow to the search giant’s plans to offer an [...]
[...] trouble for Mozilla and Google, which supports both h.264 and Ogg Theora in its Chrome browser and is expected in May to announce plans to open-source the VP8 codec it acquired from On2 Technologies. Opera, the other [...]
[...] Theora and other open source codecs. That news comes just a few weeks before Google is expected to release its VP8 codec as open source, and could come as a big blow to the search giant’s plans to offer an [...]
[...] Theora and other open source codecs. That news comes just a few weeks before Google is expected to release its VP8 codec as open source, and could come as a big blow to the search giant’s plans to offer an [...]
[...] Theora and other open source codecs. That news comes just a few weeks before Google is expected to release its VP8 codec as open source, and could come as a big blow to the search giant’s plans to offer an [...]
[...] Link:http://newteevee.com/2010/04/12/… [...]
[...] earlier this year, there’s a bit of excitement and worry about the future of VP8 and whether it will become open-source and what will happen to h264 or Theora (a derivative of On2 VP3 which On2 [...]
[...] con más calidad incluso que H.264 y que puede acabar con esta guerra si finalmente Google decide liberarlo para que su uso sea [...]
[...] for the efficient, high-quality VP8 video compression codec. And this month, Google announced that it would open source that VP8 technology, meaning that anyone could use the tech to implement web [...]
[...] a clear message to Google, which will open-source its VP8 video codec later this month, as well as Apple, which has been publicly throwing its support behind H.264 in [...]
[...] är Google som innehar rättigheterna på VP8. Här kan du läsa en [...]
[...] there are indications that more complexity is on its way: Google is expected to open source its VP8 video codec later this month, providing an alternative to H.264 and the open source Ogg Theora codec. With [...]
[...] WHOIS record, Sorenson purchased the domain on April 16, about a month before Google is expected to open source the codec it picked up through the acquisition of On2 Technologies earlier this [...]
[...] Theora and other open source codecs. That news comes just a few weeks before Google is expected to release its VP8 codec as open source, and could come as a big blow to the search giant’s plans to offer an [...]
[...] It promises to put a lot of emphasis on the future of TV and online video this time around, as Google is expected to introduce its Google TV platform in cooperation with Intel and Sony as well as open source its VP8 codec. [...]
[...] 0 Zencoder Co-founder Steve Heffernan is excited about the prospects of Google open sourcing its VP8 video codec this week, but he’s also cautioning that it could take a while before VP8 is widely [...]
[...] Gay is skeptical that Google’s plans to open source its VP8 video codec will be able to fundamentally change this situation, cautioning that it may be impossible to build [...]
[...] an open media format for the web based on VP8, the codec it acquired along with On2. NewTeeVee had scooped this news more than a month ago, and has the full story today. Mozilla and Opera are on board to [...]
[...] in August 2009, and speculation intensified after the deal closed. NewTeeeVee broke the story of Google’s plans to open source VP8 at Google i/O a month ago. Google also released WebM software development kits (SDKs) to make it [...]
[...] from On2 last February, the format is backed by fellow browser makers Mozilla and Opera.In April, rumors about the open sourcing of VP8 started to take off, but the implications of what VP8 — and now WebM — might mean has [...]
[...] to acquire On2 Technologies in August 2009, and speculation intensified after the deal closed. We first reported Google’s plans a month ago, which were confirmed with the open source release of the VP8 codec at the developers [...]
[...] April, rumors about the open sourcing of VP8 started to take off, but the implications of what VP8 — and now WebM — might mean has [...]
[...] April, rumors about the open sourcing of VP8 started to take off, but the implications of what VP8 — and now WebM — might mean has been [...]
[...] from On2 last February, the format is backed by fellow browser makers Mozilla and Opera.In April, rumors about the open sourcing of VP8 started to take off, but the implications of what VP8 — and now WebM — might mean has [...]
[...] follows Google buying and deciding to open source the VP8 video codec. WebM is a file format that combines VP8 video with open source Orbis [...]
[...] from On2 last February, the format is backed by fellow browser makers Mozilla and Opera. In April, rumors about the open sourcing of VP8 started to take off, but the implications of what VP8 — and now WebM — might mean has been [...]
[...] Google to Open-source VP8 for HTML5 Video. [...]
[...] April, rumors about the open sourcing of VP8 started to take off, but the implications of what VP8 — and now WebM — might mean has [...]
[...] aprilie, Google dadea de inteles ca ar fi vrut sa treaca VP8, ultimul video codec de la On2, in sistem open source pentru [...]
[...] NewTeeVee: Tons of great articles about the newest happenings in tech, as well as smart analysis of trends and programs. Recommended posts: 10 More Sites for Free and Legal Torrents and Google to Open-Source VP8 for HTML5 Video. [...]
[...] NewTeeVee reports that Google will soon open source VP8, the latest video codec released by On2, a company acquired by Google for $133 million. [...]