The Looming Video Codec Fight 235
itwbennett writes "With both Apple and Microsoft promoting HTML5 standards, you'd think that there would be joy in software freedom land. But instead there's another fight brewing. 'While it is true that HTML5 video is a step in the right direction, we also have to take into consideration the underlying codecs used to deliver the video content,' says blogger Brian Proffitt. The problem, says Proffitt, is that Microsoft and Apple's browsers will be supporting only the proprietary H.264 video codec by default. But Google supports only the WebM (VP8) and Ogg Theora codecs. 'So, basically, if Ogg Theora content starts making a dent in Apple and Microsoft's bottom line, or that of the MPEG LA's, then expect to see a lawsuit or two headed Google's way after 2015,' concludes Proffitt."
Or we could just fix patents and be done with it. (Score:5, Informative)
Seriously, MPEG LA is going to create a new pool to try and kill WebM, I'm sure they're already working on it. The question is whether or not we're going to let a bunch of patent trolls control future development of the web. Standardizing around a standard that requires licensing fees is the wrong way to go.
Re:Or we could just fix patents and be done with i (Score:5, Insightful)
a standard that requires licensing fees
Only in the US. In places where software patents are a load of hogwash (e.g. europe) h.264 and VP8 are equally open.
Re: (Score:2)
Re: (Score:2)
Except for the fact that there are already websites and programs that are international that use patented software but don't pay royalties?
Re: (Score:3)
That's only Germany, and the final legality of that declaration is still unclear.
The European Patent Convention clearly excludes computer programs from patentability, as seen in Article 52 (2) c [epo.org].
However, the European Patent Office has flatly ignored this paragraph, and granted many software patents.
The debate continues.
Re: (Score:2)
Hmm... that sounds like the US: having a law on the books but blatantly ignoring it.
Re: (Score:2)
Re: (Score:2)
Oh, the situation with MPEG-LA is worse than that. If you capture video on any kind of MPEG camera, even high-end "professional" models, you've now got a video that is encumbered and you can't use it for ANY commercial purpose without a license from MPEG-LA.
Re: (Score:2, Interesting)
Normally this situation is pretty cut and dry. Unfortunately, the problem here is that H.264 is substantially better technology than WebM [multimedia.cx], it's not clear that WebM is not trampling on MPEG-LA patents, Google is not indemnifying WebM users against it, and Ogg Theora is noticeably worse than WebM.
I am obviously in favor of eliminating software patents, and thereby eliminating the problem of patent trolls like MPEG-LA. I am also obviously in favor of open standards. But this is not like most software where we
Re: (Score:3)
It'd actually be very surprising if WebM did infringe any MPEG-LA patents; it was carefully designed to avoid doing so, and this shouldn't be that hard to do because a lot of the patents in question are very narrow. The reason they're so narrow is that because of the MPEG standards body's stance of patent-neutrality, the original patent holder can submit technologies to the standard that infringe on their patents and the MPEG Group won't modify them to work around the patents no matter how trivial it is to
Re: (Score:3)
And, hopefully FUD is what it will remain. But, as long as they're unwilling to sign over royalty free use for the h.264 pool, then we need to be using something else. It's not acceptable, IMHO, for standards like this to be pay for play.
Re: (Score:2)
Kill WebM, extort money for using WebM, it goes the same way ultimately. As long as people are required to pay for the use of the codec, it can't be in Firefox or any other free browser without somebody infringing on the patent. Which is the problem.
I was referring to the patent pool that MPEG LA was trying to put together, although in retrospect that was probably not at all clear.
Re: (Score:2)
As long as people are required to pay for the use of the codec, it can't be in Firefox or any other free browser without somebody infringing on the patent. Which is the problem.
Video shouldn't have to be in the browser. Every modern OS has a perfectly usable media framework for apps to use and in the vast majority of cases it already contains an H264 codec or permits one to be obtained.
Re:Or we could just fix patents and be done with i (Score:5, Informative)
Have you any idea how these pirates work? MPEG-LA is not a charity, its a business with an extremely predatory model. Collect patents together and then try and collect rent from developers.
If WebM needs protection, google will protect it. Nobody is asking MPEG-:LA to pool patents to sieze licencing rights to something they didnt invent (They didn't invent ANYTHING they licence out by the way, MPEG-LA is not MPEG. They just exploit the fact you cant trademark acronyms).
Patent pools are incompatible with free/open source. If someone forces mozilla to licence a patent, guess what only mozilla can use that code and its not free software no more. If parents cover webkit, its not free software no more.
We might well end up with a scenario that the only browsers distributable with linux are those without video.
A world without firefox, VLC , and so on is a world without free access to user created content, and that ultimately is a spike in the heart of free speech.
Re:Or we could just fix patents and be done with i (Score:4, Insightful)
If you want to 'take the moral high ground' to the extreme, then you just have to recognize that there are going to be plenty of times when you don't get your way because no one else cares about your irrational response to what you perceive as a problem in the natural order of things.
This will not be one of those times. Also, you're wrong about everything else, particularly your attempts to redefine open and paint anyone who disagrees with you as a cult member. You're delusional if you think you're litany changes the fact that software patents are the opposite of open.
Re:Or we could just fix patents and be done with i (Score:5, Informative)
|| Patent pools are incompatible with free/open source.
|I'm sorry, thats flat out false is most ways.
Actually its very true.
You, mine friend, need to learn how patent pools work and how it stops anyone from freely distribute the code using GPL.
http://www.gnu.org/philosophy/stallman-mec-india.html [gnu.org]
Given that GPL is the most used license for open source software - patent pools are very bad.
Re: (Score:3)
I don't know where you get this impression, as the MPEG-LA isn't really even "free as in beer".... or at least you need to check the
Re:Or we could just fix patents and be done with i (Score:5, Insightful)
The Patent Pool isn't to kill WebM, it is to protect those who choose to use WebM from litigation.
Spit that cool aid out fast! They cannot possibly protect from litigation, only accept payments to not litigate themselves. Anyone who chooses not to toss their patent into the pool can still crawl out from the woodwork at any time (for mpeg, vp8, or anything else).
MPEG-LA's pool has one purpose and one purpose only. It is a desperate search for anything they can use to screw people who choose to avoid their fees on mpeg and h.264.
There are two codecs out there (theora and vp8) that are freely licensed and that pisses them off. Keep in mind that when MPEG-LA claims all codecs are covered by patents, it's a combination of propaganda and wishful thinking on their part. They have so far failed to produce one that covers theora or VP8 (and they have certainly been looking). Their stated mission is to find a way to poison the well so they can sell bottled water.
Re: (Score:2)
The Patent Pool isn't to kill WebM, it is to protect those who choose to use WebM from litigation.
Sure, but protection [wikipedia.org] from whom? From themselves [techrights.org] perhaps?
'The president of the FFII has brought to people’s attention this good report from The Prior Art blog [typepad.com], saying that “MPEG-LA’s CEO Larry Horn also heads MobileMedia, a patent troll holding no less than 122 patents bought to Nokia and Sony” '
FFMPEG To The Rescue (Score:2, Insightful)
Seriously, who gives a shit? Patents are for lawyers. FFMPEG will play just about anything.
Re: (Score:3)
FFMPEG, which works until folks get sued for infringing the patent. It doesn't really matter who is doing the infringing ultimately, if you're having to either infringe or pay a fee to use a standard. For years the main headache I had from running FreeBSD as my primary desktop was no Flash, which meant no Youtube and same for dozens of other poorly designed sites.
Which is the way that this is likely to end up.
Re: (Score:2)
Re: (Score:2)
Only if the patient are valid in your country, which i'm fairly sure is not here.
Don't know about exporting the finished product back to US though but no ones going to extradite over that.
Re: (Score:2, Informative)
Only if the patient are valid in your country, which i'm fairly sure is not here.
Don't know about exporting the finished product back to US though but no ones going to extradite over that.
Which implies that any engineering, design work, or for that matter manufacturing can't happen in America without paying off this protection racket. Yeah, that really helps promote a competitive "free market". And people wonder why manufacturing companies are leaving America?
Re: (Score:2)
I wonder if a dedicated sever would get you around this?
Can the patient make transferring a binary file illegal?
Re: (Score:2)
That is not a rescue. If you are using FFMPEG you can be sued for patent violations.
Bullshit. You can't get sued for USING ffmpeg. That's not how the law works. You can get sued for DISTRIBUTING it in the without a proper license in areas in which the software patents are in effect, but that's a completely different thing.
Re: (Score:2)
Since when? (Score:4, Informative)
But Google supports only the WebM (VP8) and Ogg Theora codecs.
Wrong. It still plays HTML5 video that is H.264.
Re:Since when? (Score:5, Informative)
But Google supports only the WebM (VP8) and Ogg Theora codecs.
Wrong. It still plays HTML5 video that is H.264.
Spot on - they only announced the intention to remove it; however H.264 HTML5 video still plays just fine in Chrome.
Additionally, they're only removing it from the desktop Chrome browser - not Android. When asked about H.264 support in Android, they specifically drew a (rather artificial IMHO) distinction between the desktop and mobile platforms.
Re: (Score:3)
Yep, they were just posturing which is why if they were really going to do it they would have already done it by now. Google was just trying to use the whole WebM vs H.264 thing to push Google TV and all that but when that fell through it's amazing how we heard no more news about H.264 support being dropped.
Re: (Score:2)
No, last January they said they were planning to drop it. But, no, they haven't done so. I just tested it by playing an H.264 video in an HTML5 player.
Re: (Score:2)
They haven't finished converting the videos. Last I heard, they hadn't managed to ad advertising to their WebM selection. But, I can attest to the fact that there are plenty of WebM videos on Youtube, they just haven't gotten around to converting the whole site.
Re: (Score:2)
Even still they won't drop H.264 then unless they are planning to fuck over people using the youtube app that gets streamed H.264 video due to the hardware accelerated playback. And I wasn't talking about Youtube when I was playing the video, anyway. The whole H.264 thing with Google is mostly posturing anyway otherwise they would have dropped it in Chrome months ago.
Re: (Score:2)
I'm not so sure, Google has to pay a licensing fee for the codecs that handle the encoding and decoding process. Also, didn't they dump the codec only to have MS provide a workaround on Windows computers?
Re: (Score:3)
I'm not so sure, Google has to pay a licensing fee for the codecs that handle the encoding and decoding process.
Yeah, at max they will pay a "whopping" $6.5 million a year which is less than a fraction of 1% of their yearly revenue. Secondly, mobile devices do not have hardware acceleration for WebM and there are no future models that list that as something to be included so are they going to force people to use a software decoder and draing their battery many times faster? Doubtful.
Also, didn't they dump the codec only to have MS provide a workaround on Windows computers?
No, they didn't dump it as I already said. Microsoft was goign to release an extension or something for Chrome if they had dropped it
Re: (Score:2)
The Rockchip RK29xx already has full hardware decoding of VP8. It also happens to be by far the most commonly used chip in upcoming media players and TVs.
Google have also provided the same VHDL or Verilog to the 20 other manufactures so it is likely all future media SoCs will support it.
Re: (Score:2)
Oh and if you still don't believe me that Google isn't dropping H.264 here [webmonkey.com]:
A Google Spokesperson tells Webmonkey that the announcement is related to "Chrome only and does not affect Android or YouTube."
H.264 is still going to live on.
H.264 isn't closed (Score:3, Informative)
I don't know what it will take to get people straight on this. H.264 is open and is a standard, but patented. WebM isn't a standard, but isn't patented.
Re: (Score:2)
Re: (Score:3)
WebM is not a documented standard; The standard is the implementation. Google can change the implementation at any time and the standard follows.
H.264 is a documented standard; anyone can write their implementation and as long as it adheres to the standard, it can be called a H.264 codec.
The problem with documented standards is their lack of flexibility. It is also their greatest advantage. That is why there are always new versions of standards: HMTL, HTML2, HTML3, xhtml, HTML4, HTML5; MPEG, MPEG2, MPEG4, e
Re: (Score:2, Informative)
I don't know what you're talking about. The VP8 bitstream is frozen. WebM and VP8 are well-documented formats. An alternative codec, libvpx, was written based on the spec alone and released over a year ago. It's actually better than Google's implementation. libvpx is a VP8 codec just as much as x264 (also by DarkShikari) is an H.264 codec.
Re: (Score:2)
If it's not a formal standard issued by a standards body, and it's not a de facto standard, what really makes it a standard? If simply publishing defined a standard, almost anybody could create a standard, and there would be nothing standard about it.
Re: (Score:2)
WebM is a standard, it just isn't standard.
In what way is it a standard? Is it an ISO standard? Is it an ECMA standard? Is it a W3C standard? Right, it's not a standard of any standards body. Just because something is open source does not make it a "standard".
Re: (Score:2)
It doesn't need a standards organisation behind it to be a standard. For instance, ed, the standard editor, is standard because it's ed!
Re: (Score:2)
And its included by default in everything UNIX install this side of the moon basically. Defacto standard.
WebM is used in ... (crickets)
See the difference?
Re: (Score:2)
Re: (Score:2)
Comment removed (Score:5, Insightful)
Re: (Score:2, Informative)
Re:H.264 isn't closed (Score:5, Insightful)
Re: (Score:2)
Re: (Score:3)
H.264 requires people to pay a licensing fee to use. They have magnanimously agreed to allow people to stream H.264 for free, knowing that they've been paid for the software to encode the stream and for the software to decode the stream. That's enough to prevent the software from being freely available and shouldn't be the case with an open standard.
Re: (Score:2)
H.264 requires people to pay a licensing fee to use.
Not true. For non-commercial streaming use it's royalty-free and if you ship an encoder and/or decoder you only pay royalties for any units over 100,000 that you ship. Outside of a Google it is pretty much free for anyone. And even for someone like Google the royalties cap out at like $6 million dollars a year which is a pittance to someone pulling in 10s of billions of dollars in revenue.
Re: (Score:2)
Decoding h.264 streams is free as long as the content in the stream is free. So you can stream and decide content without paying.
There still is a significant license fee for encoding.
Re: (Score:2)
If you use H.264, you (potentially, at least) will need to pay its owners a licensing fee.
In my mind, it's somewhat irrelevant as to whether that's regulated by copyright law, patent law, trademark law, contract law, or the laws of thermodynamics; the upshot is the same. If you are reliant on the owner's permission in order to use a piece of software, then that isn't "open".
It's a very real problem (Score:4, Interesting)
The $25-PC Raspberry Pi project is struggling about which codecs to include right. Even at a few bucks or less a codec, that's a huge cost when you try to hit $25 for a functional PC.
Re: (Score:2)
Back in the day, some Linux distro's included them in the non-free repositories maintained outside the US. Why don't we find a legal loophole like that and just let the customer (who usually doesn't have to pay for the license) decide?
Re: (Score:2)
At less than 100,000 units/year, the H.264 royalty rate is zero.
From 100,000 to 5,000,000 units/year the rate is $0.20/unit (twenty cents)
and above 5,000,000 units/year, the rate is $0.10 (ten cents), until the maximum cap amount of $6.5 million/year is paid.
Source: http://www.mpegla.com/main/programs/avc/Documents/AVC_TermsSummary.pdf [mpegla.com]
Re: (Score:2)
I have no clue which other codecs are required and not free. Probably MPEG-2, MPEG-3... I'm guessing the total quickly reaches $1-$3, which is 5-15% of $25 and is, comparatively, a lot.
No more than 100,000 people (Score:2)
Re: (Score:2, Interesting)
As a software developer, I'm generally happy when my 'problem' is that I have to start paying royalties because my software has hit 100k users.
I don't know about what sort of ultra-awesome-kickass programmer you are, but by the time most of us start selling 100k units/year we've got enough accountants involved that dealing with MPEG-LA licensing is a drop in the bucket.
Re: (Score:2)
When MPEG-LA whips the llama's ass (Score:2)
On the other hand from a practical point of view, if you don't actually sell your software (e.g, it is distributed freely like say libx264), you are likely under the radar regardless of how many copies you don't sell
Even for a product comparable to, say, Winamp?
Re: (Score:2)
What a second... (Score:2)
For shame Slashdot, for shaaaaaaame.
WAIT a second... (Score:2)
Atack early, atack often (Score:3, Insightful)
The patentability of software is basically flawed and has no place in any knowledge driven economy, but unfortunately this is the reality we're saddled with for the time being.
Nevertheless, I'm getting pretty tired of companies using software patents as a tactical weapon against competition. If I could introduce a single new law, is that any given company's patent claims would have not be valid unless they were exercised at the earliest possible opportunity. No waiting for years until your competition starts threatening your bottom line before you unleash your army of lawyers. Either they would deplete their resources against every single target out there that may or may not be a threat later on, or they would forfeit any claims they might have.
Sure, there would be loopholes, and I can think of a few right now, but it would still be fun to watch.
Re: (Score:2)
Actually patents and IP law are the basis in which a knowledge driven economy can even work.
If work you've done could be decompiled and reverse engineered and your competitors can put a product on the shelf that undercuts your price because they didn't have to pay for R&D, then why bother even going to market? That's the end of innovation.
Yes, what patent trolls like Intellectual Ventures is blatantly wrong, but that's a flaw in the system, not with the patent concept as a whole.
Re: (Score:3)
Software is already well protected by copyright.
Patents are for hardware stuff. Machines and the like. And they specifically allow for reverse engineering (figuring out how things work), as that advances the general knowledge. Then people inspired by one patented machine may design their own improved machine. With or without other patented bits. Also a patent is designed to be a full disclosure of how a particular machine works: you get your 20 or so years of protection, under condition that you fully disc
Re: (Score:2)
Re: (Score:2)
The patentability of software is basically flawed and has no place in any knowledge driven economy
Without patents, there is no knowledge driven economy. Knowledge is only power if no one else has access to it. As soon as you release software (or hardware for that matter) into the while, its no longer a secret and without patents, you have no power.
Re: (Score:2)
Most software is distributed in binary form, which is hard enough to reverse engineer that patent protection doesn't really add that much benefit.
Re: (Score:2)
There's already a legal term for this. It's called the doctrine of laches. Basically, if you sit on your rights, you lose the right to enforce them. This is designed explicitly to avoid harming others that relied on your inaction.
Shameless Ad (Score:2)
The battle between h.264 and Theora has existed for over a year and this article doesn't add any new insight to the table. The OP is full of name dropping and was submitted by someone at IT World but doesn't even throw in a "full disclosure" statement. We get it, Brian Proffitt wrote a stale article for you and your buddy Soulskill hooked you up again...
Re: (Score:2)
Frankly, I agree. What is here to talk about? It's just a rehash of the same old and tired discussion.
Old news is *SO EXCITING* (Score:2)
derp
Taking the long (long) view? (Score:2)
Sigh... I'm not very optimistic about the software patent situation. The only bright spot is the very long view. Companies are patenting absolutely anything they can get away with right now. While this poses a problem for short term software development, I wonder if this will have ramifications for long term development. That is... once all the "core technology" patents have expired, they'll be free to use henceforth.
There are likely natural limitations to how much audio or video data can be compressed
Re: (Score:2)
Wrong; they'll just patent them again with slightly different wording or "...on the latest shiny toy". Sure such patents are crap, but no one has the resources to fight them all.
Apple "only" supporting h.264? (Score:2)
According to the HTML5 test page, Safari (on OS X) supports WebM as well as H.264.
This may be different on iOS of course, due to decoding issues.
right (Score:2)
Re: (Score:2)
TFA does mention Firefox
"But Google (even though it's still listed as a licensee of H.264, right alongside Apple and Microsoft) has opted to avoid the 2016 problem altogether and support only the WebM (VP8) and Ogg Theora codecs, dropping support for H.264. Mozilla has opted for the same codecs for its Firefox browser."
Re: (Score:2)
Also, there will be plugins/hacks available in no time, officially supported or otherwise.
So what about Konqueror?
Re: (Score:2)
Konqueror can handle ogg and webM at the moment.
Re: (Score:3)
Are they assuming that Mozilla is being stupid enough to kill itself before Firefox hits version 87 (approximately 1 year from now)
I look forward to that. Then when I'm using Firefox 87, and I see someone using IE9 or IE10 (if it's out then), I can tell them they should use Firefox 87 instead. When they ask what's better about it, I can tell them "IE only goes up to 10. Firefox goes up to 87!".
Re: (Score:2)
I can tell them they should use Firefox 87 instead.
And then they'll ask, "what, like, from 1987?".
Bad idea. ~
Re:Bring it on (Score:4, Insightful)
Personally, I say bring it. If indeed WebM and/or Ogg Theora are in violation then they need to fix the violation or get out of the video business. The whole premise that this is wrong is based on the notion that patents on software is wrong which is idiotic IMHO.
You'll need to explain that in more detail. Most people that I know who are in the software industry (myself included) take a diametrically-opposed view of software patents.
... patenting the mere idea is another, and that is very wrong.
Furthermore, even if (and it's a big 'if') software patents have any real benefit to anyone but anti-competitive corporate sociopaths such as Apple Computer, the way the law and the United States Patent Office are handling them is an abomination. Inventions are an expression of an idea: patenting the expression is one thing
Re: (Score:2)
A video codec is about as close to the expression of an idea as you get get without limiting patents to actual machines (and I just have to switch around a gear or something to make my expression different than yours).
Stupid software patents like CSS tricks and one click are bad, but they're bad because they're obvious or trivial, things that are already not supposed to be patentable. Clever, nontrivial or obvious algorithms themselves should be patentable just like a clever chemical process or mechanical
Re: (Score:2)
Perhaps you might be correct here.... so far as the ideas expressed in a patentable video codec would need to be rather narrow in definition where the patent really only covers the specific approach used with a particular codec.
Sadly, particularly with software patents, they are typically interpreted very broadly where you are being held liable for infringement merely because you wrote a single line of code.... in whatever language you are writing that software.
If you could write some software completely fr
Re: (Score:2)
Absolutely. I own a software and hardware dev company. We are firmly opossed to software patents. I find the idea laughable. I know competition will try to implement the features I include, and I'll do the same. That drives innovation, and helps create both formal and ad-hoc standards. Whenever I include a feature that noone has included before, I try to make as complete as possible, and we start working on an update right on release date, knowing I still have to compete We don't own a single patent, and we
Re: (Score:2)
Patents on software is one thing, patents on standards is quite another thing. It's completely unacceptable for a standard to require a party to license the patent to use the standard. You can sort of get away with it, when it's a standard solely for interacting with a particular software package, but otherwise it's obnoxious and has no place in a standard.
Just look at the headaches with GIF and JPEG, if you don't believe me.
Re: (Score:2)
Actually, GIF wasn't an official "standard", just an image format created by Compuserve and adopted in a bunch of other places.
And JPEG was specifically designed/created to be patent royalty free:
"The JPEG committee has as one of its explicit goals that their standards (in particular their baseline methods) be implementable without payment of license fees, and they have secured appropriate license rights for their upcoming JPEG 2000 standard from over 20 large organizations."
There have been a few lawsuits o
Re:Bring it on (Score:5, Interesting)
The issue with GIF wasn't even Compuserve, but rather some patent trolls at Unisys who discovered that they held a patent on the LZW compression algorithm. Unisys went to Compuserve with a legal threat, but also a licensing scheme where they and their customers could be absolved of past and future infringement if they would submit to the license.... and they capitulated.
In fairness to Compuserve, the developers who created the GIF standard intended it to be patent and royalty free. Their mistake was picking up an ACM Journal and discovering the LZW algorithm when they were trying to establish the format, thus adopting that algorithm into the standard. Typically at the time, algorithms published in such a manner were considered "in the public domain"... or at least assumed so if you were formally publishing how they were working in an internationally recognized journal of that nature. Certainly in the article where this algorithm appeared there was no mention of intellectual property other than a copyright on the article itself. Software patents were presumed to be something you would do to something that you also protected via trade secrets and deliberately tried to keep from your competitors except for a begrudging filing with the USPTO that was usually obfuscated enough that you couldn't really figure the algorithm out from the patent application anyway.
It should be noted that IBM also seemed to have a patent on LZW algorithm, so the claim by Unisys could have been challenged from multiple fronts. The problem was that nobody wanted to take them on so it was either ignored or people capitulated to Unisys.
The largest problem with the GIF format was the issue that web browsers had adopted the GIF standard as a de facto image standard and the only universal image format across multiple operating systems and browsers that displayed images. JPEG images were starting to come into use, but there are limitations on JPEG images and it wasn't nearly so universal. Furthermore, most image editing software at the time Unisys started to demand royalty payments supported the GIF standard.... in part because it was thought to be patent and royalty free.
This stands out because it was one of the first software patents that really impacted a broad swath of software developers and pretty much hit nearly every internet user at about the same time. Few companies are willing to let such "submarine patents" languish without enforcement any more because too much money can be made through enforcement before the concept becomes essentially an international standard. Unisys got lucky after a fashion too, as they certainly didn't contribute to the development of the GIF standard.
In terms of "official standard", I guess that is in the eye of the beholder. I do believe that the W3C did archive the GIF standard and provided links to Compuseve's documents on the format as a recommended image format for web browsers before the patent issue hit the fan. It certainly was hard to avoid the use of GIFs even if you tried, and was a pretty universal image format even before web browsers were created.
Re: (Score:2)
In terms of "official standard", I guess that is in the eye of the beholder. I do believe that the W3C did archive the GIF standard and provided links to Compuseve's documents on the format as a recommended image format for web browsers before the patent issue hit the fan. It certainly was hard to avoid the use of GIFs even if you tried, and was a pretty universal image format even before web browsers were created.
Yep, everything you say is true, of course - I was just pointing out that neither GIF nor JPEG
Re: (Score:2)
At the very least, if courts recognized standards bodies and invalidated patents not disclosed for standards widely published after a certain period of time, I think that would go a long way in terms of stopping trolls. Part of the problem with a patent is that you don't have to enforce it like you do with trademarks and copyright. With copyright, if you ignore enforcement.... the infringement is held to be legal. With patent law, you can file a lawsuit decades after infringement and even seek compensati
Re: (Score:2)
Computational complexity (Score:2)
Why would anyone still use Theora? VP8 is twice as good in terms of compression : quality.
What's the relative computational complexity of decoders for the two formats? I've been told Theora is comparable to MPEG-4 Part 2 (e.g. DivX) and VP8 is comparable to H.264. When trying to play back video on existing hardware, such as a video game console, it helps to know that you can hit the 24 fps target without overheating.
Re: (Score:2)
If you don't want to worry about patents, stick with MPEG-1 video. It does a pretty good job, both software and hardware implementations are ubiquitous, and you have test data of almost anything you would like.
Ogg Theora is nearly as old as Ogg Vorbis, although its adoption has been much slower in part because MPEG-1 has been available to fill in any niche application that might have used it.
Yes, compression on MPEG-1 stinks compared to some of the newer codecs. That is what you pay for with the new fangl
Re: (Score:2)
Yea, that last line about "outdated results" really beefs up your point, there.
Re: (Score:2)
Well, theoretically, if hard/software folks didn't have to pay licenses and royalties for the tech, then they could sell the soft/hardware cheaper, for one.
Re: (Score:2)
Yea, gifs are totally dead.
senorgif.com