6 ms·
Whether it's better or not in some aspects, in practice patent encumbrance makes such decoders non redistributable, therefore open source browsers can never nor
by shmerl 13y ago
Whether it's better or not in some aspects, in practice patent encumbrance makes such decoders non redistributable, therefore open source browsers can never normally adapt such codecs, and it makes sense for W3C/IETF to choose mandatory codecs only from explicitly open (i.e. free and non patent encumbered). The best course of action is not to bow to codec cartels like MPEG-LA, but to fight against current closed codecs domination and to advance open ones by improving and creating new better codecs.
There is a greater risk of people popping up with claims against VP8 or VP9 as they are newer and less prominent. The MPEG-LA's call for a pool of patents has helped draw out those patent owners and many have joined the pool and reached terms with Google (although Nokia and maybe others haven't.
This is common FUD. Whatever was in that "pool" - the end result no one attempted to attack VP8 with patent claims, except for Nokia. The strange counterexample to the claim that "prominence" guarantees safety is Google, who used H.264 against Microsoft themselves. Nothing is protected against sudden patent attacks. But if there are no known patents - then paranoia won't help anything.
- josephlord 13y agoI don't claim that W3C or IETF should standardise on H.264. I think it is perfectly sensible for them to hold the line but the practical reality for implementers is that H.264 is a commercial requirement. Note that I said "greater risk" not that there was no risk for H.264 or that it is a massive showstopper for VP8. I stand by my statement although this really isn't critical EXCEPT for the fact that due to FRAND commitments potential claims are limited (as the Motorola/Google case is showing). If you have made no FRAND commitments you can get injunctions or ask for outrageous (hundreds of millions of dollars or even billions) licensing fees but if FRAND commitments have been made you cannot do this as the courts are educating Google/Motorola. The obvious baseline for W3C to adopt would in my view be MPEG1 allowing a fallback to a safe free codec and modern non free codecs to be used otherwise.
- shmerl 13y agoQuality is important. Using poor quality common denominator is a bad idea. Once Nokia attack is cleared, VPx would be good to use again as a base available open codec. FRAND or non FRAND can affect damages, but as I said above it doesn't change the non redistributable nature of anything that depends on it.
- josephlord 13y agoI'm not convinced Nokia will lose. Even if Nokia lose and no-one else comes forward the Google licence is non-redistributable anyway so for many purposes is no better than the AVC one. Freedom, zero cost, quality, low legal risk. Choose two.
- shmerl 13y agoAnything can happen, but On2 was diligent in evaluating public patents related to video. So it looks like Nokia is spoofing things up. Time will tell of course. One of the benefits of the IETF process is the requirement to disclose all the patents, so they can be evaluated and refuted if possible. I'm sure WebM project is busy with reviewing this. Freedom, zero cost, quality, low legal risk. Where did you find freedom and zero cost there? Low legal risk is a myth in the land of patent minefields. the Google license is non-redistributable anyway Again wrong. VPx content as well as encoders and decoders are redistributable under the current license which is fully open source compatible.
- josephlord 13y ago>> Freedom, zero cost, quality, low legal risk. > Where did you find freedom and zero cost there? Low legal risk is a myth in the land of patent minefields. I made it up, couldn't narrow it down to three. MPEG1 is low risk, free and Free now. AVC is low risk now it has been a juicy target for long enough to draw out trolls and it is high quality. VP8 is high quality and zero cost. The license that Google has from the MPEG-LA doesn't seem to allow for those who accept the license to sub license. If this is incorrect please send a reference. You seem to be of the view that the pool contents are either invalid or non-essential. Until I see a detailed study of them that indicates this with claim by claim explanations I will assume that at least some may be valid. Now Google has taken the license it is highly unlikely they will challenge the pool patents (and they may be contractually obliged not to). This means there is no big player likely to fight the patents and make the status clearly open source compatible.
- 13y ago
- wmf 13y agoYou might want to be more precise about what you mean by "non redistributable", because licensed binaries are redistributable if they either phone home to track the number of copies or if the vendor pays the cap. Mozilla got all bothered about downstream source redistribution which affects approximately zero of their users.
- shmerl 13y agoYes, I mean downstream redistribution. Mozilla stands for open source licensing which allows downstream redistribution and they aren't going to change that. Whether it's used in practice or not is secondary, since that's what the license allows. If they change it, they have to change their license altogether.
- wmf 13y agoOr they could just not include the H.264 decoder in the source code and leave the license the same, like they did with a few other components back in the day.