HEVC Advance Announces H.265 Royalty Rates, Raises Some Hackles 184
An anonymous reader writes: The HEVC Advance patent pool has announced the royalty rates for their patent license for HEVC (aka H.265) video. HEVC users must pay these fees in addition to the license fees payable to the competing MPEG LA HEVC patent pool. With HEVC Advance's fees targeting 0.5% of content owner revenue which could translate to licensing costs of over $100M a year for companies like Facebook and Netflix, Dan Rayburn from Streaming Media advocates that "content owners band together and agree not to license from HEVC Advance" in the hope that "HEVC Advance will fail in the market and be forced to change strategy, or change their terms to be fair and reasonable." John Carmack, Oculus VR CTO, has cited the new patent license as a reason to end his efforts to encode VR video with H.265.
How about this... (Score:5, Insightful)
Don't like the licensing terms? Don't use H.265...
Re:How about this... (Score:5, Insightful)
Better: Work together with like-minded companies to create a competing standard that is designed specifically to avoid patents, and license it royalty-free.
Obligatory xkcd [xkcd.com].
Comment removed (Score:4, Informative)
Re:How about this... (Score:5, Informative)
I'll just leave this here: https://wiki.xiph.org/Daala [xiph.org]
Re: (Score:3)
Re: (Score:2, Informative)
Except, the quality of VP9 still can't compete with aging h.264 unless the baseline profile is used. Not to mention the encoder is slow as a snail on tar. I love it when people who know nothing about encoding video get into a discussion on codecs.
Re: (Score:3)
Re: (Score:2)
Until your client is furious and wants to fire you because his grandma using IE 8 on XP can't view your videos on her internets.
Or the marketing department sends you the video file made in Adobe products which are h.265 for the website whose tools can't export to vp9.
Re: (Score:2)
Re: (Score:2)
I'll just leave this here: https://en.wikipedia.org/wiki/ [wikipedia.org]...
There is just one small problem.
Industrial giants like Mitsubishi dominate the production of video hardware in all market segments from studio production to home video.
If their UHDTV sets and other gear do not support your codec, you are dead in the water. Which is precisely what happened to the alternatives to H.264.
Re: (Score:2)
Not really. My TV takes uncompressed data. Once an encoder is available, the only things that matter these days are whether the following things support the codec:
If you cover those, all other clients of the codecs are lost in the noise, so it is probably safe to use it on your own site for your own content.
It doesn't really matter at all whether the codec used to encode the content for delivery is the same as the
Re: (Score:2)
Re: (Score:2)
Not really. Both are similar in terms of efficiency.
The advantage h.264/h.265 have is dedicated hardware, not efficiency.
Re: (Score:2)
I always think "what a waste" about dedicated hardware. A decoding module for ONE codec in your CPU? A special device for bitcoin calculations? In the future it (or its part) is just trash, when all people are using newer codecs and bitcoin is replaced by something else.
Re: (Score:2)
Play a 1080p H.265 video and look at the processor usage - not efficient, very processor intensive. Each generation of codec requires several times more processing power than the previous one.
Re: (Score:2)
This is because bandwidth is still a bigger problem then processor power overall, and at the moment we're very much in a local maxima where the situation seems slightly reversed.
Re: (Score:2)
Re: (Score:2)
The 4K h.265 file sill be half the size of the 1080p h.264 file
I'd like some of the drugs you are taking. An H.265 file will be 35-50% of the size of the same file encoded with H.264. The idea that a 4K file will be half the size of a 1080p with the two different files encoded with H.265/H.264 is absurd, and seriously outside of even the most optimistic goals of the organization at the outset. The original goal was that the same file encoded with the same visual quality would be half the size. I've never seen that happen, I've seen somewhere between 35 and 40% at best,
Re:How about this... (Score:5, Informative)
That's exactly what Xiph does with the Daala [xiph.org] project. They're trying to implement lapped transforms for video (more or less the same principle as Opus does for audio) and since it's not based on traditional block encoding, Daala should avoid most patents. Their demos are already pretty impressive.
Re: (Score:3)
Daala should avoid most patents.
*snort* Like that ever stopped patent lawyers.
Xiph and lawsuits (Score:5, Informative)
Like that ever stopped patent lawyers.
Total number of lawsuits lost by Xiph for Vorbis, Opus, FLAC, Tarkin, Theora, etc.: 0
Yes, lawyer won't stop simply because it's different. They would dream to lawsuit Xiph into the ground. But so far they haven't found anything on any of the other technologies developed or taken over by Xiph.
The people at Xiph know their shit and if they say that a codec is using a non patented alternative technique, it is non patented.
Re: (Score:2)
Total number of lawsuits lost by Xiph for Vorbis, Opus, FLAC, Tarkin, Theora, etc.: 0
Total money that could be made by winning a lawsuit against Xiph: Zero. Why would anyone take them to court, when there is no money to be made?
Now if you convinced Netflix, Google, Apple, Microsoft etc. to replace all their codecs with Xiph codecs, you would see patent lawsuits rolling in.
Vorbis in video games, etc. (Score:2)
Now if you convinced Netflix, Google, Apple, Microsoft etc. to replace all their codecs with Xiph codecs, you would see patent lawsuits rolling in.
Because they are BSD licensed, various Xiph codecs like Vorbis are popular for storing soundtracks of video games [wikipedia.org].
FLAC is a popular audio codec in high-end HD-based digital autio players aimed at audiophiles.
Google did provide Thoera variants at some point in time (I don't know if they still do).
Nobody ever lost money following suit due on thr gound of these codecs.
---
The reason that Theora isn't that popular, is that currently H264 does provide a better image quality for a given bandwith and as most of the
Re: (Score:2, Insightful)
That's exactly what Xiph does with the Daala [xiph.org] project. They're trying to implement lapped transforms for video (more or less the same principle as Opus does for audio) and since it's not based on traditional block encoding, Daala should avoid most patents. Their demos are already pretty impressive.
I do hope they have learned from Google's mistakes with VP9 and and come out early with a good specification and stable hardware reference implementation.
I work for a fairly large video oriented service, and we would love to start supporting alternative codecs (and eventually leave H264/5) but lack of full hardware support in mobile devices is an absolute blocker. Everything needs to be working well, with battery efficiency, on mobile devices at this point. I know a lot of other services currently on the f
Re: (Score:2, Informative)
Better: Work together with like-minded companies to create a competing standard that is designed specifically to avoid patents, and license it royalty-free.
And better yet, do that work in the IETF's Internet Video Codec [ietf.org] working group, which is what Xiph [xiph.org] and Cisco [slashdot.org] are doing.
Re: (Score:2)
But when you're designing your codec with one hand tied behind your back, it's not going to work as efficiently.
More than one way.... (Score:2)
More than one way to do thing with compression.
But when you're designing your codec with one hand tied behind your back, it's not going to work as efficiently.
Yup, your hand is tied behind your back, but just as you try to work anyway, standing in another corner there's this other guy with an hindu name asking you if you need a hand. or six.
It might not work as efficiently if you try to achieve the exact same thing but are restricted in the methods you use*. But you can obtain very efficient result if you try something completely different. Then the patents won't even matter.
The realm of DCT it a patent mine field? T
That may well be what happens (Score:2)
Which is why this is pretty stupid. H.264 is "good enough" for most things. Particularly as bandwidth continues to grow. A more efficient encoding scheme would be nice, but it isn't necessary. We can already do 1080p60 video over most net connections with reasonable quality.
So H.265 will have to be appealing not only in terms of bandwidth saved, but in terms of cost. Companies won't move to use it if they have to pay a bunch extra for the privilege. They'll just keep using H.264 and more bandwidth.
Re:That may well be what happens (Score:5, Informative)
I can understand why the patent holders are upset with the MPEG-LA - because the MPEG-LA mandated that patent licensees will be paid for every use up to a cap (approx $6.5M/year), streaming is free (as long as viewers can watch the stream for free), and all sorts of other things. So companies like Apple, Cisco, Netflix, etc., they pay the $6.5M license fee and go about their merry way (incidentally, Cisco's fee also pays for Firefox's license).
Which is why h.264 is the predominant codec in use today - it's relatively cheap to use, sites like YouTube and Vimeo pay $0 to host videos that anyone can watch for free (they will have to pay for those subscriber/paid videos, though, since those cannot be viewed for free) - yes, "for free" means you the viewer pays $0 to watch, not that you don't pay some other way (e.g., watching ads).
MPEG-LA, to ensure adoption of HEVC wants similar licensing terms - a cap, free streaming for free to view, etc., But some patent holders (including the likes of GE and others) balked - hence forming the HEVC alliance and getting rid of the "thorns" - no cap to the amount you pay, streams also cost money, etc.
There was a lot of derision about MPEG-LA's free stream policy, but they know that widespread adoption is a good thing, and there's a reason why everything's in h.264 format.
Sadly, the greed of a few is probably going to kill HEVC - at a time when HEVC is just coming out, the last thing you want is to stifle it. I'm sure the patent holders of h.264 will probably make way more money because people will stick with what works and is well established over moving over to something that requires paying a lot of money for continually. At the very least, big companies like Apple, Microsoft, Google, Netflix, Vimeo etc, who probably just pay the cap every year will stick with h.264 than be subject to huge licensing fees of an unlimited cap. Either that, or HEVC will remain a niche for paid subscribers.
Re: (Score:2)
But some patent holders (including the likes of GE and others)
I'm kind of surprised GE has patents on software video compression.
Re: (Score:2)
Re: (Score:2)
But it is a standard now. If you do not use it what do you propose? Flash?
VP9? Ok now your IE users will claim it doesn't work. What kind of video editing tools out there support ogg vorbis or vp9? Any adobe products that your coworkers and rest of the industry use do?
Re: (Score:2)
What kind of video editing tools out there support ogg vorbis
Well, given that very many games use ogg/vorbis for audio precisely because it's royalty free, I imagine there's a good commercial tools to deal with it. Fewer games use theora, but it's not nonzero and includes large ones like Diablo III.
But anyway what? Don't people edit in lossless then transcode to a lossy format at the end anyway?
Re: (Score:3)
Re: (Score:2, Insightful)
Honestly, for video codecs, people probably will just stop. At least for the big ones. I really don't see why they are needed, human eyes are only so good, we will NEVER have a need for 2D video that's much better. A 4K monitor is already near the visual limit of our eyes, and things like H.264 handle it just fine. If someone develops a new one in a few years how much better will it really be? We are compressing the video to fit on our computers, and the computers are getting to the point where they can dea
Re: (Score:2)
Re: (Score:2)
And H.265 is horribly cpu/gpu intensive to the point you'll need a fan to cool the processor down when decoding it or your processor won't be able to handle it (for 4k, especially 4k 60fps).
Given the amount of terawatts that could be needed to process h265 continuously worldwide, I'd rather we all stick to h264.
Re: (Score:2)
Last time I checked, there already is a fan on about every CPU. What are you running, a 486 DX?
Re: (Score:2)
Not on my core i5. And nope, no liquid cooling either.
Re: (Score:2)
Do your phone or tablet etc have a fan in?
Re: (Score:2)
That's ridiculous. I wanted to assume this was a joke but there just wasn't anything particularly funny about it.
First: computers/devices are designed to let their CPUs run at 100% with whatever cooling mechanism they have designed.
Second: PCs are a tiny minority of the devices that stream/decode video these days - especially 4K. Obviously, you don't need a 4k stream on a device that only has a 2k display or less (almost all PCs, tablets, and phones). So that leaves 4K TVs, BD players, and high end gamin
Re: (Score:2)
RTA [streamingmedia.com], They are asking for too much money and too much hassle, I don't think they'll get many users as a result.
Which requires a lot of electricity - internet streaming and hard disk space don't require a lot of electricity. So I'd prefer that H.265 doesn't make it big until most equipment has dedicated decoder silicon.
Re: (Score:3)
I don't need to RTFA (though I did). I work in the industry. H.265 is already in every 4K TV on the market. Netflix, Amazon, MGo, and others are already streaming it. It's going to be the basis of the 4K Blu-Ray successor.
Customers may not even know they are watching H.265 encoded video, but that doesn't really matter. The "users" in this case are the CE manufacturers and the content providers, who have already made the decision to adopt it.
Which requires a lot of electricity - internet streaming and hard disk space don't require a lot of electricity. So I'd prefer that H.265 doesn't make it big until most equipment has dedicated decoder silicon.
Except H.265 doesn't require that much from a decent GPU. A LOT LESS than your average 3D game that people play for hours a day. This is a silly non-issue. And as I already said most equipment already does have dedicated silicon. 4K TVs have had it for 2 years. PC GPUs accelerate most of the computationally intensive operations as well.
Oh, and all of that hard disk space and the servers that contain them requires a shitload of electricity. Do you think sever-class HDDs just spin through perpetual motion?
Re: (Score:2)
Yes, H.265 support is out there and Netflix et al are using it. The question is how long they'll keep using it now that HEVC Advance has announced they're taking 0.5% of Netflix's revenue.
Re: (Score:2)
> First: computers/devices are designed to let their CPUs run at 100% with whatever cooling mechanism they have designed. ...
No, they are not.
Maybe in the '80th
Today a CPU can power down a lot, if it's idle.
Re: (Score:2)
Not when they are running a modern 3D FPS for hours at a time, which most gaming PCs are perfectly capable of doing without catching fire.
As far as phones, etc, they do all of this in dedicated hardware, anyway. This whole thread is such FUD from people who know nothing about the actual topic (H.265 decoding hardware)...
Re: (Score:2)
Any idea why they never did that with H.264? MPEG-2 offered 10-bit color. DVD and (I think) ATSC take advantage of it, and it makes a difference in scenes with large areas of slightly changing color (like a shot of the sky). That it wasn't available in H.264 (except maybe for some craz
Re: (Score:2)
Considering H.265 taxes my intel I7 considerably, I think that more energy will be used decoding for a good few years until most hardware has dedicated decoding chips which use much less energy.
But given the way advances in silicon have almost stalled now and the royalties being demanded, I think it will be a long time before H.265 becomes standard even for piracy (look at how much XViD is still being used).
Re: (Score:2, Informative)
Re: (Score:2)
Not just bandwidth costs, but storage costs as well. B/W + storage for Netflix's entire content library is well over $100M / year (I have heard that their total for encoding+storage+streaming is closer to $500M). Cutting that in half would be huge.
Not to mention it's not just about the providers costs, but the customer's ability to stream it - high quality 1080p for 3-5Mbps means most people could stream HD now.
That said, this is not going to magically solve any of those issues - they have something like 1
Why do we need H.265? (Score:2)
Doesn't H.264 (aka MPEG4) which has much wider client support (browsers, hardware decoding, mobile etc) do a good enough job?
Comment removed (Score:5, Informative)
Re: (Score:2)
Re: (Score:2)
Re: (Score:2)
HEVC provides similar image-quality at half the bitrates as H.264
That's the goal. Reality is not there yet, at least not for most applications. Results at the moment are more like 35-40% reduction, which is still excellent.
Re: (Score:2)
MPEG-LA claims to have full H265 patent coverage, so it'll be decided in the courts if MPEG-LA can defend their H265 claims against HEVC Advance. My guess is that MPEG-LA knows what they've got and HEVC Advance is making a big show for shareholders. Technicolor already put it in their last quarterly earnings report that they had massive profit potential from their HEVC patents. To me this looks like a fake out by companies like Technicolor to trump up the value of their patents while MPEG-LA continue
Re: (Score:2)
Since the industry hasn't completely embraced HEVC yet, doesn't this level the playing field for VP9 (or any other contender).
h264 is pervasive. h265 is not. It requires a processor with "ludicrous speed" if you don't have the dedicated silicon to decode it.
Re: (Score:2)
My guess is that is exactly what this is designed for. Dedicated silicon. Think AppleTV, Fire, Chromecast (future version), or any of the other set top boxes. That's what they are targeting. This codec isn't about what consumers use on the desktop, it's about how video gets to their TV. Dedicated hardware has better copy protection (not approving just noting motive), and has the decoding power built in. So this fits right in.
Re: (Score:3)
This is the disadvantage of software patents.
Also change the rules so that if something becomes a standard you can't charge a royalty for it.
Re:Why do we need H.265? (Score:4, Interesting)
HEVC, however, is not a FRAND patent, though they would likely see much higher adoption if they were (probably similar to H.264, since they essentially used a de facto FRAND approach).
Re: Why do we need H.265? (Score:3)
Re: (Score:2)
This is the disadvantage of software patents.
What does this have to do with software patents? It's about patents. There is nothing specific to software patents here. You have several patent holders, one set of patent holders who want to license their patents for cheap, and one set of patent holders who want to charge enormous amounts.
Re: (Score:2)
H.265 is a software solution. Of course you can elect to realize that through hardware gates but you can also realize it through a FPGA or pure software so - software patent problem it is.
Re: (Score:3)
At least for physical media, this paves the way for 4K video on something not much larger than current media. Sure, physical media is dead and all that. But I still buy it. It also makes streaming 4K more feasible.
Re:Why do we need H.265? (Score:5, Interesting)
It's a better, more efficient format / encoding standard, producing similar quality at somewhere between 50-70% of the size of H.264, according to some benchmarks I've seen. Given how much bandwidth video takes, that's not a small gain in efficiency. The additional efficiency is certainly useful for reducing streaming bandwidth requirements for HD and 4K resolutions, which is growing rapidly in popularity.
However, it seems as if the patent pool group has gotten a bit too emboldened by the relative success of H.264. Using the old "the first one's... well, not free, but cheap" model, they're hoping now to cash in by jacking the price up significantly, and broadening the scope of who has to pay as well.
This may end up killing or at least severely delaying 4K TV and HEVC (H.265) adoption. It's pretty costly, and businesses may just stick with the older format. It's hard to see companies willing to give that much of a percentage, especially since they're now targeting *content providers* and not just hardware manufacturers. Then again, maybe there's enough money being made that they won't care. Smartphone manufacturers pay a huge amount in patent licensing fees.
Difficult to say what will happen here. If they do suck it up and pay, it will basically mean higher costs passed along to consumers for nearly all new digital video content. Personally, I hope this blows up in their faces and everyone refuses to use the codec until more reasonable terms are presented.
Re:Why do we need H.265? (Score:5, Interesting)
For lossy still images, JPEG2000, the successor to JPEG, is not widely used. JPEG is good enough.
For lossless still images, PNG was created to provide a free and superior replacement for the proprietary GIF format. The only reason GIF hung on was that it could do simple animations. MNG and APNG provide animations for PNG. APNG appears to have beat out MNG, but neither was soon enough to push GIF into complete oblivion. Still, PNG has mostly supplanted GIF.
Despite being the oldest and by far the worst quality of the major lossy audio formats, MP3 is still king, though Ogg Vorbis has claimed some niches. For instance, Vorbis is a popular format for sounds for computer games. One of the big problems Vorbis suffered was purely political. Microsoft went to war against the format, in part because it didn't have DRM. They would have also killed mp3 if it wasn't so popular. MS managed to squash Vorbis in the US so that it is very hard to find a music player that supports the format. For some players, I installed Rockbox to get support for Vorbis. For another, I learned that the same device was sold in the US and Europe, just with different ROMs. Flash the US device with the European ROM (which involved tricking the ROM installation program by switching ROM files after it did its check and before it did the install) and just like that the US device could play Vorbis. How MS bullied or bribed the manufacturer to omit Vorbis from the US ROM I don't know.
So, yeah, H 265 could easily fail to gain widespread adoption if the licensing terms are too onerous and greedy, no matter how much better it is compared to H.264. H.262 (MPEG-2) is still kicking around, as it's the format used for DVD video.
Re: (Score:2)
MS did try to kill MP3 - they bundled Windows with a CD-ripping capability in windows media player that was only capable of saving to WMA format. It's a powerful tactic, but in this case it failed.
Re:Why do we need H.265? (Score:4, Informative)
You're mostly right, but JPEG2000 is the format specified for digital cinema encoding. Look inside that big MXF file, and it's a bunch of JPEG2000 stills. Been to the cinema lately? You're watching x frames per second of JPEG2000.
Widely used, just not widely known.
Re: (Score:2)
You're mostly right, but JPEG2000 is the format specified for digital cinema encoding. Look inside that big MXF file, and it's a bunch of JPEG2000 stills. Been to the cinema lately? You're watching x frames per second of JPEG2000.
True, but at such massive bitrates (up to 250 Mbit/s) that pretty much anything will look good and in bandwidth-challenged areas they do physical distribution. And they only premiere a handful of movies each week, size is not a big deal. Since wavelet encoding is heavily patented I'm guessing DCI got a waterproof deal before choosing it as the digital cinema standard, with patent holders hoping this would spur adoption. Obviously it didn't and since then better formats have appeared, so it's never going mai
Vorbis vs. Licensing terms of WMA (Score:5, Informative)
Flash the US device with the European ROM (which involved tricking the ROM installation program by switching ROM files after it did its check and before it did the install) and just like that the US device could play Vorbis. How MS bullied or bribed the manufacturer to omit Vorbis from the US ROM I don't know.
The bullying was done as part of the PlaysForSure [wikipedia.org] program.
That was microsoft's attempt to counter music stores like iTunes and co. They had a platform for selling DRM-ed music in WMA format. OEMs had to undergo a certification to be able to advertise "Microsoft PlaysForSure". That mandated certain formats (support for DRM, support for WMA). It was worded in such a way that it basically forbid manufacturer to put any other codec on the device (see the "Criticisms" section. According to MS that was due to a junior employee who wrote it. Yeah. Sure.). It think the controversy was talked about back then here on /.
My opinion is that this probably started as an attempt to initially close loop-hole to avoid consumer playing non DRM-ed / unlicensed music (i.e.: pirated), but at the hand of MS executive quickly evolved as a way to attempt crushing competition.
That severly limited the spreading of non-WMA formats (free like Vorbis or FLAC. Or alternative licenses like Sony's ATRAC, etc.) because OEMs probably feared that including extra formats would exclude them from WMA certification and they would lose market share to manufacturer who didn't.
(Specially since back then, Vorbis didn't have any markets, it was mostly used for higher quality home rips. Whereas WMA had Microsoft's store and OEMs were hoping to have something against the iTunes behemoth).
Or mostly so in the US.
The rest of the world didn't give a damn fuck about microsoft's market (was is even available outside US ?) nor play for sure. People wanted mainly MP3 because that was the most widespread format, and adding extra formats was a way for OEM to put more tick box on their feature list. As such adding Vorbis was a win-win: it doesn't cost anything (and even had a BSD licensed integer implementation for embed available for free) and was one extra feature that they'll advertise to gain attraction. Every single asian no-name manufacturer did add it.
In Europe nearly every player I've seen in store did have Vorbis support.
That explains the dual ROM:
- one ROM to placate microsoft to get access to PlaysForSure in the US market.
- one ROM with as many features as possible cramed in to gain visibility everywhere else.
Re: Why do we need H.265? (Score:3)
Re: (Score:2)
Four: two different dedicated players, an Android tablet, and an Android tv box that all support vorbis.
Vorbis in Europe (Score:2)
So...How many portable music players do you own with vorbis support?
Depends, if he lives in Europe: nearly every single last one of them, specially the asian no-name brands.
The practice of Microsoft regarding PlaysForSure [wikipedia.org] in the US is an entirely different matter.
Re: (Score:2)
smartphone, tablet, old smartphone, old trekstor vibez, some other trekstor device with flash like 8 gb flash, which even plays video.
Re: (Score:2)
Re: (Score:2)
>Doesn't H.264 (aka MPEG4) which has much wider client support (browsers, hardware decoding, mobile etc) do a good enough job?
I dunno. I've seen x265 encodes of video which come out at under 150MB where the x264 encode is ~1.5GB for the same quality.
That's a huge saving in bandwidth.
How much is 0.5% of zero? (Score:2)
Revenue, not profit (Score:2)
On the Government is stupid enough to base your rates on "profit" which can be gamed to be zero or less.
No, this is revenue. The top line number. And it's a lot harder to game.
Will Drive Sites To Use VP9 (Score:2)
The big test is if the big MPAA studios using HEVC for UHD Blurays will pay this new patent pool or not. The quantity of money is large enough that they'll probably either negotiate a better deal or take it to court.
Unfortunately, if anyone pays, that'll fund them enough to be able to take everyone else to court, so the patent pool likely won't die unless there's some major court case striking down the patents. If anyone has enough sway with the US government to get software patents killed, it's the MAFIAA.
Re: (Score:2)
Re: (Score:2)
VP9 is not at all ready for prime time. It is super-slow to encode and decode, and often looks worse than VP8 at the same bitrate.
So glad its a HTML 5 standard (Score:3, Interesting)
For those who bashed Firefox and those who supported Ogg Vorbis and vp9 or whatever the hell that other codec was called ... all I can say is TOLD YA SO!
Notice how they waited until Flash was dying before this announcement?
Pretty soon they will go after Mozilla for royalities fees and if you do not want to spied upon by Google or use IE you will need to install flash back. Flash is the only recourse as horrible as this sounds agaisn't this as it is a defacto standard now to use this patented technology which will require DRM I am sure too and perhaps an anti open source license agreement too forcing developers like those who make Konqueror to either violate the GPL or not work on many websites.
So part of an open standard is owned by a monopoly and the great internet which was owned by the people is now licensed under Hollywood. Incredible!
Re: (Score:2)
You are confusing h.264 and h.265. Nothing you said makes any sense.
Re: (Score:2)
It doesn't have to make sense if you really, really believe it.
Re: (Score:2)
Sorry about that unclosed tag. I hit submit when I was reaching for preview. And there's no way to edit after submission.
Oh what the hell.. (Score:2)
Can't we just wait 20 years, and then use the codec?
Re: (Score:3)
That doesn't quite work - the patents also cover useful encoding techniques, so you have to also go through your code and make sure you aren't using any mathematical concepts discovered and patented in the last twenty years.
Re: (Score:2)
The codec only specifies how the encoded stream is formed and how it should be decoded. It does not specify how the encoder should transform raw video into encoded form, and much effort is devoted to finding new algorithms by which existing codecs may be made to perform better without alteration of the decoding side.
Re: (Score:2)
That works. It just means that your software is sub-optimal - a competitor that pays the license fee can use more up-to-date techniques. It also requires constant legal vigilance - someone has to monitor any submitted code to make sure some programmer hasn't made use of a modern method without thought to the legal implications.
Re: (Score:3)
They do it because of VR (Score:2)
VR popularity grows substantially. .
VR market is going to explode with tons of new products in Q1 2016 (an assumption based on actual product announcements)
VR movies (360 x 180) take at least x6 more than regular ones (less than 120 x 90 ).
Some VR products and solutions will have to use 265, without major improvements of the infrastructures.
Hence 265 becomes an enabler, and the license price vs. storage volume & network price begins to sound like a reasonable trade-off.
Hence the draconian licensing term
Re: (Score:2)
NetVC (Score:2)
Current contributions include Daala(https://wiki.xiph.org/Daala) from Xiph and Thor(https://github.com/cisco/thor) from Cisco, both having good performance in different metrics(FastSSIM and PSNR respectively). Combined, both could achieve higher performance than a single one alone.
If the success of the Opus cod
HW support (Score:2)
I've never understood... (Score:2)
Re: (Score:2)
...why any "standard" would include patented technology. Seems like a very stupid idea. About the same as copyrighting the spelling of words.
It's because you want a standard to include the best possible technology, and a lot of that is patented. But most of the time that's fine, because a standard only becomes a standard if everyone accepts it as a standard, and that only happens if licensing conditions are acceptable to the huge majority of players in the market. That's what happened with MP3 and h.264; they are free for small companies, cheap for medium sized companies and relatively cheap for big companies.
And that's the problem here, som
Ominous cloud on the horizon... (Score:2)
.
As we are beginning to see, once the codecs become an essential facility, patent fees will start to be extracted from the users.
Why not? (Score:2)
0.5% sounds fair. And it's especially fair, because it's gratis for non-commercial (possibly open source) products and sites.
uhh... (Score:2)
Daala is the future. (Score:3)
This article is about video encoder, not audio encoders.
Okay then...
Daala [wikipedia.org] is a lot better and free.
...fixed the original post.
Is it okay now ?