Slashdot Mirror


HEVC Advance Announces H.265 Royalty Rates, Raises Some Hackles

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.

184 comments

  1. How about this... by Frosty+Piss · · Score: 5, Insightful

    Don't like the licensing terms? Don't use H.265...

    --
    If you want news from today, you have to come back tomorrow.
    1. Re:How about this... by Anonymous Coward · · Score: 1

      Change patent law. Without government protection will ppl just not develop any codecs anymore?

    2. Re:How about this... by dgatwood · · Score: 5, Insightful

      Don't like the licensing terms? Don't use H.265...

      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.

      --

      Check out my sci-fi/humor trilogy at PatriotsBooks.

    3. Re:How about this... by Gaygirlie · · Score: 4, Informative

      create a competing standard that is designed specifically to avoid patents, and license it royalty-free.

      I'll just leave this here: https://en.wikipedia.org/wiki/...

    4. Re:How about this... by ptaff · · Score: 5, Informative

      create a competing standard that is designed specifically to avoid patents, and license it royalty-free

      That's exactly what Xiph does with the Daala 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.

    5. Re:How about this... by Billly+Gates · · Score: 1

      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?

    6. Re:How about this... by Anonymous Coward · · 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 deal with less compression, so why do we spend so much getting more compression that we don't actually need? I think in the future more and more people will just say H.264 with low compression and high quality is just fine, in the same way they did it with JPG, JPG and PNG are good enough, there are plenty of other formats that are better in many ways, but people want support first, and if the thing with the best support works in your application you use it.

    7. Re:How about this... by Anonymous Coward · · 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 working group, which is what Xiph and Cisco are doing.

    8. Re:How about this... by Anonymous Coward · · Score: 0

      VP9 is aimed at a different target than H264 and H265 though.

    9. Re:How about this... by Anonymous Coward · · Score: 5, Informative

      I'll just leave this here: https://wiki.xiph.org/Daala

    10. Re:How about this... by SuricouRaven · · Score: 1

      But when you're designing your codec with one hand tied behind your back, it's not going to work as efficiently.

    11. Re:How about this... by Anonymous Coward · · 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.

    12. Re:How about this... by Billly+Gates · · Score: 1

      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.

    13. Re:How about this... by Anonymous Coward · · Score: 0

      So explain the situation to your clients and bosses. Ask them if they're willing to pay H.265 patent license royalties.

    14. Re:How about this... by Anonymous Coward · · Score: 0

      How do you do that with retroactive billing
      "Making matters worse, HEVC Advance says their licensing terms [listed in detail here] are “retroactive to date of 1st sale”, so companies would be required to make payments on content they have already distributed using HEVC."

      The only thing I can think to do is what's good for the Goose is good for the Gander.

      I will stop using it retroactive to the date of the first sale. Should take care of the retroactive bill.

    15. Re:How about this... by Anonymous Coward · · Score: 0

      But when you're designing your codec with one hand tied behind your back, it's not going to work as efficiently.

      Unless someone like Cisco offers their IPR under royalty-free terms in new video codec. Then you can experiment with those techniques in your codec and working together develop a codec which combines best features of both, similar to how OPUS was developed.

    16. Re:How about this... by Anonymous Coward · · Score: 1

      Nope this is just dumb.

      Do we need h.265? Did we need h.264? The problem is not the visual fidelity but rather the bandwidth. Netflix, Youtube, etc will be switching to h.265 come hell or high water because it will cut their costs in HALF. Even if they own crappy alternatives, unless the web browser or underlying hardware/OS support it naively (which all hardware will) they will be required to find a way to playback h265 even to just transcode it back to h264 or whatever crappy codec they can license.

      The comparison with GIF/PNG and JPG/Jpeg2000 isn't honest. We replaced GIF with PNG because of patents and there was a need for lossless alpha-blended graphics, which is something that GIF and JPEG could not do. There isn't a need to replace JPEG with JPEG2000 because the increase in screen resolution has reduced the ability to see the artifacts, and people who use JPEG's generally leave the compression in the 80-90 range instead of back in the dialup days where we'd push it down to the 60's just to make sure a web page would load on dialup in less than 3 minutes.

      But with h265, h264, h263 (AKA DivX) we never had the intent of downloading an entire video before playing it. We've been doing this ever since "Realvideo" and "Vivo" (Remember that before RealMedia acquired it?) Just wait out the patent time and say screw it to h265 until there is some fundamental reason to.

      Right now h264 (AVC) is in everything, and we saw how much the patent licensing held back DVD and Blueray players... (Hint, no version of Windows came with MPEG-2 or H264 playback, so you had to buy a 200$ drive and 100$ software product to be able to play them,)

      Making the players have to pay to use it, is a non-starter, every time. Who should pay? The people who benefit the most from it, Youtube, Netflix, Facebook, etc. But since they control the distribution platform, they could always prevent h265 from becoming standard until the patents die off or they negotiate better terms.

    17. Re:How about this... by Anonymous Coward · · Score: 1

      No it isn't. All three are "video compression". Unless you mean that VP9 isn't meant to stifle the industry with rent seeking payments.

    18. Re:How about this... by Anonymous Coward · · Score: 0

      >and license it royalty-free

      LOL

    19. Re:How about this... by Anonymous Coward · · Score: 0

      Nope this is just dumb.

      Do we need h.265? Did we need h.264? The problem is not the visual fidelity but rather the bandwidth. Netflix, Youtube, etc will be switching to h.265 come hell or high water because it will cut their costs in HALF.

      They might cut their bandwidth cost in half. Computational cost for each video will possibly increase. (Although that is a one time cost per video.)
      Costs for running the server halls and administer them will probably not change.
      The summary claims that a target of 0.5% of the revenue.
      So the question that remains is if the bandwidth cost for streaming is more than 1% of the revenue. Otherwise it's not worth it in the hope that the bandwidth will be halved.
      I have no idea how much of the operational costs the bandwidth is for a company focused at streaming. In the projects I worked at where it was of interest to reduce bandwidth the savings would typically have been swallowed by the cost of implementing the improvements but I suspect that my experiences doesn't apply to this situation.

    20. Re:How about this... by Skapare · · Score: 2

      I'll just leave another one here: https://en.wikipedia.org/wiki/...

      --
      now we need to go OSS in diesel cars
    21. Re:How about this... by Dutch+Gun · · Score: 2

      Daala should avoid most patents.

      *snort* Like that ever stopped patent lawyers.

      --
      Irony: Agile development has too much intertia to be abandoned now.
    22. Re: How about this... by Anonymous Coward · · Score: 0

      Haha how about use it and don't pay the licensing! Fucking stupid capitalist cocksuckers ... Go off yourselves you fucking pieces of shit! Lol

    23. Re:How about this... by bloodhawk · · Score: 1

      surely there must be a 3rd option? being screwed by H.265 patents or getting a subpar VP9 codec controlled by google that is less efficient and MUCH slower to encode with seems to be asking which would you like to be stabbed with the rusted razor blade or the filleting knife. Either way you lose.

    24. Re:How about this... by Anonymous Coward · · Score: 0

      as much as the patenting suck on H.265/264 they are aimed at being efficient, especially important for low powered devices. VP9 is in incredibly inefficient (i.e. slow at encoding, larger file size, more resources). VP9 would be fine for web, but the target audience for H265 is devices, VP9 sucks balls for devices, it is not even close fight, VP9's only hope there is that devices get powerful enough so that its poor efficiency doesn't matter.

    25. Re:How about this... by serviscope_minor · · Score: 1

      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?

      --
      SJW n. One who posts facts.
    26. Re:How about this... by Anonymous Coward · · Score: 2, Insightful

      create a competing standard that is designed specifically to avoid patents, and license it royalty-free

      That's exactly what Xiph does with the Daala 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 fence about VP9 have similar views.

      Google have been approaching video codecs as they approach online services - betas in production, frequent revisions, not a stable spec (or spec at all). Not a good approach to get the chip makers onboard.

    27. Re:How about this... by squiggleslash · · Score: 2

      ...yeah, I don't know if you missed the TFS, but the summary is actually about the fact that people are deciding not to use H.265, because they don't like the licensing terms...

      --
      You are not alone. This is not normal. None of this is normal.
    28. Re:How about this... by Rockoon · · Score: 2

      I did a little comparison myself a few months back because I was backing up a bunch of DVD's .. VP9 was on par with H.264 for targeting 1GB filesizes, but H.265 was miles ahead .. targeted 600MB/movie and it was still better than either.

      --
      "His name was James Damore."
    29. Re:How about this... by squiggleslash · · Score: 1

      Google has gone out of their way to invest in video codecs to ensure there are non-encumbered standards that are in the same ballpark as H.264. There will always be incentive to improve bandwidth by producing better codecs.

      I suspect actually that patents are holding back codecs, not helping. Who wants to innovate in that space if you know that whatever you end up with is likely going to be crippled with other people's patents given you'll have to build on the work of others to make something affective?

      --
      You are not alone. This is not normal. None of this is normal.
    30. Re:How about this... by Goaway · · Score: 1

      Not really. Both are similar in terms of efficiency.

      The advantage h.264/h.265 have is dedicated hardware, not efficiency.

    31. Re:How about this... by squiggleslash · · Score: 1, Informative

      They might cut their bandwidth cost in half. Computational cost for each video will possibly increase

      You'll be surprised what can be done with a codec like MPEG-1 if you have unlimited computational power. Much of the point of better codecs is to reduce the computational power needed to achieve a substantial reduction in bandwidth for a given level of quality. So while it'll likely increase, the amount is unlikely to be substantial, not even a doubling of processing power.

      --
      You are not alone. This is not normal. None of this is normal.
    32. Re:How about this... by MrL0G1C · · Score: 1

      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.

      --
      Waterfox - a Firefox fork with legacy extension support, security updates and better privacy by default.
    33. Re:How about this... by MrL0G1C · · Score: 1

      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.

      --
      Waterfox - a Firefox fork with legacy extension support, security updates and better privacy by default.
    34. Re:How about this... by Electricity+Likes+Me · · Score: 1

      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.

    35. Re:How about this... by Anonymous Coward · · Score: 0

      They are not even close to being similar. VP9 takes nearly double the power to encode, VP9 is also around 10% larger file size for the same quality (less quality when comparing similar sizes). This is a killer when selling to dedicated hardware market.

    36. Re:How about this... by Anonymous Coward · · Score: 0

      yep, now try the dog that is VP9 and you will see why it isn't a viable alternative, especially when it comes to encoding. H.265 is also likely to get the builtin hardware support (well it would have if they hadn't fucked up the licensing), making it exponentially better.

    37. Re:How about this... by Anonymous Coward · · Score: 0

      About the elephant: But how easy is it to decode?

    38. Re:How about this... by Kokuyo · · Score: 1

      Last time I checked, there already is a fan on about every CPU. What are you running, a 486 DX?

    39. Re:How about this... by Anonymous Coward · · Score: 0

      Hey Piss Face, you have no choice when the applications you buy use it, and when it's built into your SoC devices. Mr Piss, we all pay for this stuff when we buy product and software, whether we actually use it or not. This is hidden fee is merely a hidden patent tax hundreds of millions or people pay each year without knowing it. So why do you do $NAME off!

    40. Re: How about this... by Anonymous Coward · · Score: 0

      Raspberry pi 2? The future is small, fanless media boxes, probably built into the TV. No fan required there.

    41. Re:How about this... by dunkelfalke · · Score: 1

      Not on my core i5. And nope, no liquid cooling either.

      --
      "It's such a fine line between stupid and clever" -- David St. Hubbins, Spinal Tap
    42. Re: How about this... by Anonymous Coward · · Score: 0

      Yes. It would be interesting to breakdown the bandwidth AND energy cost change for transmitting say a million streams vs decoding those million streams.

    43. Re:How about this... by Anonymous Coward · · Score: 0

      you are thinking of h.264, h.265 is the next generation successor that hasn't even gotten off the ground yet. The licensing terms between h.264 and the new terms of h.265 are miles apart. Why incentive do people have to adopt the new standard with such a high cost even if it is better?

    44. Re:How about this... by Twinbee · · Score: 1

      You're right. One is for people who don't care about efficiency, quality or speed.

      --
      Why OpalCalc is the best Windows calc
    45. Re:How about this... by Anonymous Coward · · Score: 0

      So one company creates good tech useful for everyone and blackmails us to pay whatever they want?

    46. Re:How about this... by MrL0G1C · · Score: 1

      Do your phone or tablet etc have a fan in?

      --
      Waterfox - a Firefox fork with legacy extension support, security updates and better privacy by default.
    47. Re:How about this... by Anonymous Coward · · Score: 0

      newer GPUs and even android sticks or phones contain the h265 codec and can decode it via hardware with far less CPU/GPU time

    48. Re:How about this... by Anonymous Coward · · Score: 0

      >buying software
      HAhaha... he buys software what a loser !

    49. Re: How about this... by Anonymous Coward · · Score: 0

      Obvious you don't rip videos as an improvement of nearly 50% in compression over H264 there are good reasons for the advancement. But if you don't believe that advancements are a good thing, go back to your Democrat party poo poo party and have a good scream.

    50. Re:How about this... by Dahamma · · Score: 1

      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 gaming-type PCs to do HEVC 4K. On the first two in that list, these days it's all done on a dedicated chip (or really, an SoC - system on a chip - that contains most of the functionality of the device. On the gaming PC, it's done on the GPU and is TRIVIAL compared to running a modern 3D game.

      H.265 is going to become the standard in the near future - not just for 4K (in which is will pretty much be the only solution) but for 1080p as well, since you get significantly higher quality (including 10 or 12 bit color, BT2020 colorspace, high dynamic range, etc) for about 1/2 the bandwidth. Basically 5 Mbps to stream near Blu-ray quality 1080p movies, and even at 3Mbps 1080p looks decent. That will put HD streaming in the homes of about 90% of the US population. And that's just the first generation HEVC encoders - like X264 has over the years, they will continue to improve...

    51. Re:How about this... by Dahamma · · Score: 1

      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 10-15 streaming formats to support various devices. But I'm pretty sure their 4K is all HEVC over MPEG-DASH.

    52. Re: How about this... by Anonymous Coward · · Score: 0

      Cell phone, roku and chromecast don't have any fans...

    53. Re:How about this... by MrL0G1C · · Score: 1

      H.265 is going to become the standard in the near future

      RTA, They are asking for too much money and too much hassle, I don't think they'll get many users as a result.

      First: computers/devices are designed to let their CPUs run at 100% with whatever cooling mechanism they have designed.

      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.

      --
      Waterfox - a Firefox fork with legacy extension support, security updates and better privacy by default.
    54. Re: How about this... by MrL0G1C · · Score: 1

      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).

      --
      Waterfox - a Firefox fork with legacy extension support, security updates and better privacy by default.
    55. Re:How about this... by hairyfeet · · Score: 1

      Yeah....tell that to the owner of that sleek new phone when it dies after 30 minutes because H.26X sucked its battery like a fucking vampire why don't ya?

      This is why I've been saying we do NOT need to kills flash for H.264, and sure as fuck not for H.265 because they both suck hairy nuts when it comes to how much power they waste for a given video! If you don't believe me? Encode the same video twice, do one in H.264 and the other in VP8 or VP9, run 'em both while having the PC on a kill-a-watt and look for yourself. the H.264 only APPEARS to work well to the end user because its crapping all over the GPU but all those GPU cycles don't grow on trees, they lead to lousy battery life, increased heat as well, and when so many are using phones and tablets that run on ever thinner batteries? I'm sorry but that shit just doesn't cut it! And try loading a page with HTML V5 H.264 vids and look at the power suckage, again worse in every way than Flash with VP8/9.

      Lets face it folks, H.26X is just not a good format, its patent encumbered up the ass, sucks more CPU and GPU than competing formats, its just not the best choice when we have multiple free alternatives that if the resources were instead devoted to making them better would end up with a much better experience for everybody....but then we'd be ignoring the rotting elephant in the room, which is that Apple,Google, and MSFT all WANT a format that is encumbered up the ass, it makes a really nice high barrier for entry that gives them the market to themselves.

      --
      ACs don't waste your time replying, your posts are never seen by me.
    56. Re:How about this... by allo · · Score: 1

      > 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.

    57. Re:How about this... by allo · · Score: 1

      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.

    58. Re: How about this... by Anonymous Coward · · Score: 1

      Ha. A right winger considers the 1/2 percent H265 income tax to be a good thing. Income taxes are only acceptable to a wingnut if they are imposed by corporations.

    59. Re:How about this... by Anonymous Coward · · Score: 0

      First: computers/devices are designed to let their CPUs run at 100% with whatever cooling mechanism they have designed.

      Well, no. There are many laptops that have insufficient cooling and drop clock speed when they get too warm.

    60. Re: How about this... by Anonymous Coward · · Score: 0

      $60 android players from China for half a year or more.

      I don't think you know what you're talking about.

    61. Re:How about this... by Ducho_CWB · · Score: 1

      I am sure that my Macbook Pro i5 was not designed to be 100% CPU all the time. Or maybe it was however Apple's marketing forgot to tell us to use it as a stove top too.

    62. Re:How about this... by Dahamma · · Score: 2

      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?

    63. Re:How about this... by Dahamma · · Score: 1

      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)...

    64. Re:How about this... by westlake · · Score: 1

      I'll just leave this here: https://en.wikipedia.org/wiki/...

      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.

    65. Re:How about this... by ncc74656 · · Score: 1

      H.265 is going to become the standard in the near future - not just for 4K (in which is will pretty much be the only solution) but for 1080p as well, since you get significantly higher quality (including 10 or 12 bit color

      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 crazy-high profiles or levels not in regular use?) always seemed like a step back.

      --
      20 January 2017: the End of an Error.
    66. Re:How about this... by Anonymous Coward · · Score: 0

      Any idea why they never did that with H.264?

      They did. See the table at the end of the H.264 features section on the Wikipedia page for the profiles that support it. And here's a paper on using 10-bit color H.264 for broadcast applications.

    67. Re:How about this... by dgatwood · · Score: 1

      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:

      • Chrome
      • Safari
      • Firefox
      • iOS
      • Android
      • YouTube
      • to a lesser extent, OS X, Windows, and Internet Explorer

      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 codec used to encode it during production. In fact, I would seriously hope that 100% of video production is being done with a higher quality codec than the low-bitrate crap that is being used to deliver content over the 'net. Therefore, whether Mitsubishi et al choose to support a codec or not is mostly irrelevant.

      In practice, only three companies actually need to work together to make such a patent-free codec happen: Apple, Microsoft, and Google. Firefox would quickly adopt any patent-free codec that those three got behind. That makes the entire rest of the industry pretty much completely irrelevant. Those three companies could mandate a transition to a new, patent-free codec, and the entire world would practically trip over themselves to make it happen.

      So no, those industrial giants aren't really a problem. In fact, they aren't even relevant in the grand scheme of codecs except to the extent that the big three graciously allow them to be.

      --

      Check out my sci-fi/humor trilogy at PatriotsBooks.

    68. Re:How about this... by roca · · Score: 1

      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.

    69. Re:How about this... by allo · · Score: 1

      And where is your argument?

      He said, "you will drain your battery", you said "the cpu uses 100% anyway", now you say "... when gaming". So, now i am watching a movie with 20% cpu instead of 100% and do not thing about your games. I can see the credits, while your tablet already shut down.

    70. Re:How about this... by Shirley+Marquez · · Score: 1

      People's internet connections are already straining to stream 1080p video. And even so, the quality of existing 1080p streams is mediocre; visual artifacts are often easy to spot. It is possible to get better looking 1080p video by using more bits; broadcast HD and Blu-Ray both do that. Blu-Ray and streams are mostly encoded with H.264; broadcast digital TV in the US is at a disadvantage because it uses MPEG-2 but it uses enough bits to more than overcome the disadvantage relative to streamed video.

      4K ups the ante. For a given level of freedom from artifacts you need about four times as many bits; the exact ratio depends on the content and how well it compresses. The majority of home internet connections aren't up to the challenge of carrying even one 4K stream, let alone multiple streams as you might have in a family or a group household; nor is the rest of the infrastructure of a typical ISP. Using a better codec decreases the number of bits that need to be sent.

      And 4K is not the end point. That level of resolution may be adequate for content that you only view at a typical screen distance (as we look at a movie screen, TV set, or computer monitor), but more immersive forms of video such as video walls, where we might look closely at a small part of the picture, will require even higher levels of resolution.

    71. Re: How about this... by Anonymous Coward · · Score: 0

      Eventually h.265 will be hardware decoded, just like h.264. No fans needed there.

    72. Re:How about this... by Anonymous Coward · · Score: 0

      You really don;t understand the advantages of doing the encode in HW. Power. Encoding on a general purpose CPU takes a LOT more power than encoding in dedicated HW. For example, the Videocore4 as used in the Raspberry Pi uses 75mA at 3.3v to encode 1080p30 video. That is WAY less than a general purpose CPU. Using the GPU for work like this is MUCH more efficient that using the CPU. It also means the main CPU can be off doing other things rather than flogging its nuts off encoding or decoding.

      You also seem to misunderstand the processing requirements as a whole. Improving compression from H264 to H265 (or any similar jump) takes a LOT more processing power, simply because the algorithms are a lot more complicated, and require huge amounts of computation to produce the very high compression rates. There is no magic to get improve compression rates by 50% - it's just more cycles.

    73. Re:How about this... by Anonymous Coward · · Score: 0

      Because the decoder bandwidth requirements double for only a 2 bit increase in colour depth. In general the device doing the decoder doesn't like working with 10 bit values, it wants 8 or 16. So moving from 8 to 10 bit actually means you start working in 16 bit values. It also requires a complete rework of the decoder HW to work in 16 bits, which increases silicon area. It's all a big price increase for very limited benefit.

    74. Re: How about this... by Anonymous Coward · · Score: 0

      Yes, if I don't pay my H265 tax I get thrown in jail...

      Dumbass libtard.

    75. Re:How about this... by Dahamma · · Score: 1

      They can TRY. But there is no way this happens without a massive legal fight...

    76. Re:How about this... by Dahamma · · Score: 1

      No, your reading comprehension is lacking. Nothing in the post I replied to mentioned ANYTHING about battery. He only mentioned that devices would have to add CPU fans (where I assume they didn't already have one).

      The fact is *tablets* will support H.265 when they have hardware decoders to support H.265. At which point the power usage will be close to H.264.

      Don't even know why I am bothering to continue this silly thread with non-engineers pretending to know how video decoding works in HW/GPU/SW/etc. If your ridiculous point made any sense we'd still be watching VHS-quality MPEG-1 video.

    77. Re:How about this... by allo · · Score: 1

      please read the thread instead of flaming.

      > 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

      Here we get a battery problem on your mobile device

      > First: computers/devices are designed to let their CPUs run at 100% with whatever cooling mechanism they have designed.

      And that's the stupid reaction.

  2. Why do we need H.265? by jonwil · · Score: 1

    Doesn't H.264 (aka MPEG4) which has much wider client support (browsers, hardware decoding, mobile etc) do a good enough job?

    1. Re:Why do we need H.265? by Gaygirlie · · Score: 5, Informative

      No. HEVC provides similar image-quality at half the bitrates as H.264, so that'd automatically make it much more appealing for e.g. streaming-services -- think of Netflix, YouTube, Twitch, Justin.tv and so on and so forth. On the other hand, HEVC would provide much higher image-quality if you used the same bitrates as for H.264, which would make such content much more appealing to end-users. I, for example, am often annoyed by the banding and compression-artifacting with e.g. Netflix, but if they switched over to HEVC and just used otherwise the same bitrates I'd be getting much clearer picture. Basically, HEVC allows you to save in bandwidth or storage or allows you to improve quality. All of these are very good reasons to upgrade from H.264.

      Now, VP9 is similar to HEVC in that that it'd also allow for saving in bandwidth or storage or to improve quality of video, but support for VP9 is pretty much non-existent.

    2. Re:Why do we need H.265? by Z00L00K · · Score: 2

      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.

      --
      If builders built buildings the way programmers wrote programs, then the first woodpecker would destroy civilization.
    3. Re:Why do we need H.265? by omnichad · · Score: 2

      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.

    4. Re:Why do we need H.265? by Anonymous Coward · · Score: 0

      Also change the rules so that if something becomes a standard you can't charge a royalty for it.

      Best way to ensure good stuff doesn't make it into standards.

    5. Re:Why do we need H.265? by Dutch+Gun · · Score: 4, 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.

      --
      Irony: Agile development has too much intertia to be abandoned now.
    6. Re:Why do we need H.265? by Anonymous Coward · · Score: 1

      but support for VP9 is pretty much non-existent.

      I wouldn't say that's the case. Even just looking at YouTube, already by April this year more than 25 billion hours of VP9 encoded video had been watched by YouTube users.

    7. Re:Why do we need H.265? by Anonymous Coward · · Score: 0

      support for VP9 is pretty much non-existent.

      Youtube uses it. Firefox and Chrome can play it (and IE with a plugin).

      OTOH, support for HEVC on the web is non-existent right now.

    8. Re:Why do we need H.265? by bzipitidoo · · 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.

      --
      Intellectual Property is a monopolistic, selfish, and defective concept. It is "tyranny over the mind of man"
    9. Re:Why do we need H.265? by SuricouRaven · · Score: 1

      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.

    10. Re:Why do we need H.265? by Anonymous Coward · · Score: 0

      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.

      This is pure bullshit. Might you be trolling? I've been a diehard Vorbis user since the beginning. Microsoft has never prevented me from encoding or decoding Vorbis files. If they wanted to squash anything it would have been MP3, which you could say they tried to do with WMA.

    11. Re:Why do we need H.265? by stevedog · · Score: 3, Interesting

      IANAL, but that's essentially the idea behind FRAND patents (i.e., those which the inventors have agreed to license for "fair, reasonable, and non-discriminatory" terms). When you chooses to license using that model, it basically means that you can get a nominal reimbursement (because, after all, you did have to do some work to develop it) for each license, but that is pretty much it. Also, what is considered "nominal" is pretty low (as far as intellectual property goes, anyway) and strongly enforced by the courts. Furthermore, once you go FRAND with a patent, you usually can't really go back, so licensees have a guarantee that they aren't going to get it at a reasonable rate today during the adoption phase, but then see the price go up 500% when some contract runs out.

      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).

    12. Re:Why do we need H.265? by gnasher719 · · Score: 1

      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.

    13. Re:Why do we need H.265? by dwywit · · Score: 3, 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.

      --
      They sentenced me to twenty years of boredom
    14. Re:Why do we need H.265? by a_n_d_e_r_s · · Score: 0

      No thats the idea behind ZRAND patents. That is patent that is free to use without any compensation.

      FRAND can be very expensive. For example MPEG4 patent pool, for a small company 6.5 million are very expensiv.

      --
      Just saying it like it are.
    15. Re:Why do we need H.265? by Dutch+Gun · · Score: 0

      The only reason GIF hung on was that it could do simple animations.

      That, and the fact that the major browsers took YEARS to properly implement PNG support (particularly IE). Until that happened, no one could use it on the web. It gained popularity as a standalone format regardless because it was a sane, well-designed image format.

      It was the same story with Vorbis - Microsoft's Windows Media Player still to this day doesn't play Vorbis without a plugin. There's no way in hell it's anything but a political issue, as it would be *trivial* to add support for it (I've added Vorbis support for my own games - it takes a couple of days of work). For whatever reason, MS just seems to pretend that it doesn't exist.

      --
      Irony: Agile development has too much intertia to be abandoned now.
    16. Re:Why do we need H.265? by Anonymous Coward · · Score: 0

      So...How many portable music players do you own with vorbis support?

    17. Re:Why do we need H.265? by Anonymous Coward · · Score: 0

      One. My mobile phone supports Vorbis as do all Android devices.

    18. Re: Why do we need H.265? by jrumney · · Score: 2

      $6.5M is the cap. At $0.20 per device, that is a lot of devices for a small company to be selling without growing into a big company.

    19. Re:Why do we need H.265? by Xiaran · · Score: 1

      Hate to break it to you. Justin.tv is gone.

    20. Re:Why do we need H.265? by Z00L00K · · Score: 1

      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.

      --
      If builders built buildings the way programmers wrote programs, then the first woodpecker would destroy civilization.
    21. Re: Why do we need H.265? by jrumney · · Score: 2

      WMA was invented because of the patent demands surrounding MP3, not to kill off Vorbis. Microsoft licenses WMA out to hardware vendors at 0.10 per decoder, compared with 1.35 for a stereo MP3 decoder, and 0.98 for AAC. Probably we have Microsoft to thank for the more reasonable licensing fee structure adopted by MPEG-LA for their patent pools for H.264 and H.265.

    22. Re:Why do we need H.265? by Anonymous Coward · · Score: 0

      That's now. The reason you have it now is because M$ lost that war back in the olden days.

    23. Re:Why do we need H.265? by Anonymous Coward · · Score: 1

      support for VP9 is pretty much non-existent.

      Youtube uses it. Firefox and Chrome can play it (and IE with a plugin).

      OTOH, support for HEVC on the web is non-existent right now.

      Problem with VP9 is lack of hardware support on mobile devices. On desktop you can just pour CPU power at it, on mobile this drains the battery really quickly. The service I work for (and many others) would love to leave H264/5 license hell if mobile devices started supporting VP9. In my view Google has done a terrible job in that area. They thought their web and browser dominance was enough, and have really missed the ball on hardware support.

    24. Re:Why do we need H.265? by Kjella · · Score: 1

      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 mainstream. Right now BGP seems to be the superior choice and since it's a subset of HEVC if you license it for video the photo format should be "safe" to implement, which means it might get camera support. Having "native" support without going via RAW would be a big deal.

      --
      Live today, because you never know what tomorrow brings
    25. Re: Why do we need H.265? by Anonymous Coward · · Score: 1

      WMA was invented because of the patent demands surrounding MP3, not to kill off Vorbis. Microsoft licenses WMA out to hardware vendors at 0.10 per decoder, compared with 1.35 for a stereo MP3 decoder, and 0.98 for AAC. Probably we have Microsoft to thank for the more reasonable licensing fee structure adopted by MPEG-LA for their patent pools for H.264 and H.265.

      Also, it would be a quite feat to invent WMA to kill of Vorbis given that initial 1999 release of WMA was a year before initial 2000 release of Vorbis. Both the Vorbis project and WMA project was prompted by the 1998 announcement to start charging significant licensing fees for MP3. As you correctly imply.

    26. Re:Why do we need H.265? by Anonymous Coward · · Score: 0

      What they never mention in the marketing material about H.265 and VP9 is that the halved bitrate comes at the expense of 2-4x the encode and decode computational cost. They are basically unusable without a hardware decoder, and are not fundamentally more efficient with respect to quality than H.264 and VP8, they've just made different compromises now that faster hardware exists. No miracle discovery in encoding tech has occurred here.

    27. Re:Why do we need H.265? by jedidiah · · Score: 1

      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.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    28. Re:Why do we need H.265? by sshir · · Score: 1

      On VP9 hardware support: many "smart" TVs have it. Google uses YouTube as a battering ram.

    29. Re:Why do we need H.265? by techt · · Score: 1

      Four: two different dedicated players, an Android tablet, and an Android tv box that all support vorbis.

    30. Re:Why do we need H.265? by Anonymous Coward · · Score: 1

      As you said it depends on the industry and silicon support. In the tv/set top industry h265 is pervasive among the chip vendors at this point. So at least for that sector HEVC is becoming the standard for 4k and future transmissions. I can tell you they arent happy about it though mainly because of this licensing hell. I know our encoding guys at the office have tried every other codec they possibly could including VP9 and nothing works as well.

      Also despite VP9's insistence on having simple licensing and being worry free, it really isnt, there are many holes in their licensing. From their past experiences with mpeg4 which also had alot of these holes which required you to go to 2,3,4 entities to actually get complete licensing VP9 really doesnt look any different and still had the encoders worried

    31. Re:Why do we need H.265? by Blue+Stone · · Score: 1

      >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.

      --
      Corporation, n. An ingenious device for obtaining individual profit without individual responsibility. - Ambrose Bierce
    32. Re:Why do we need H.265? by I+prefer+not+to+say · · Score: 0

      No. HEVC provides similar image-quality at half the bitrates as H.264, so that'd automatically make it much more appealing for e.g. streaming-services -- think of Netflix, YouTube, Twitch, Justin.tv and so on and so forth. On the other hand, HEVC would provide much higher image-quality if you used the same bitrates as for H.264, which would make such content much more appealing to end-users. I, for example, am often annoyed by the banding and compression-artifacting with e.g. Netflix, but if they switched over to HEVC and just used otherwise the same bitrates I'd be getting much clearer picture. Basically, HEVC allows you to save in bandwidth or storage or allows you to improve quality. All of these are very good reasons to upgrade from H.264

      Most people have hardware where you can't tell the difference between HD and Full HD video. If you want to save bandwidth you watch the lower resolution version. H264 has become the MP3 of video. Only cinephiles and audiophiles will know the difference.

    33. Re:Why do we need H.265? by 605dave · · Score: 1

      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.

      --
      Be kind, for everyone you meet is fighting a difficult battle. - Plato
    34. Re:Why do we need H.265? by Anonymous Coward · · Score: 0

      ...but support for VP9 is pretty much non-existent

      There is this unknown youtube named service by a tiny tiny small company (Google) which already provides VP9 versions of videos. Under my experience uploading stuff, and getting stuff from other people, what happens is that if you upload crappy/heavily encoded mp4 (h264) videos, the vp9 version will suck tremendously, either by being larger than the h264 stream or by having horrible visual artefacts. No surprise here, everybody knows what happens when you recompress a JPG.

      However, if you upload a really high bitrate version, or essentially upload a 4k version and whatch the generated fullhd, vp9 always beats the mp4 generated by Google, either in size or in quality (I've seen terrible terrible mushed up faces look good in vp9). Also, when comparing h265 offline against vp9 I've found that of course h265 beats it in size, but requires much more higher decompression efficient hardware. vp9 chugs along fine, while h265 may skip frames (using vlc at least).

      So, is this a conspiracy by Google against h265? No idea. But at least at the moment the world is probably watching more vp9 streams than h265 already.

    35. Re:Why do we need H.265? by Anonymous Coward · · Score: 0

      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.

      In hardware H265 is already well on the way to becoming pervasive, much more so than VP9. Maybe this new licensing issue will cause some to re-evaluate alternatives, but then Google really need to improve their game on this - solid stable specification, easy licensing and patent guarantees, active support for HW implementations. Or Xiph Daala might do it right.

    36. Re:Why do we need H.265? by Anonymous Coward · · Score: 0

      Considering how cinephiles and autdiophiles have been proven to be full of shit time and time again with double blind testing, it is safe to say that nobody will know the difference.

    37. Re:Why do we need H.265? by allo · · Score: 1

      smartphone, tablet, old smartphone, old trekstor vibez, some other trekstor device with flash like 8 gb flash, which even plays video.

    38. Re:Why do we need H.265? by terjeber · · Score: 1

      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.

    39. Re:Why do we need H.265? by Bengie · · Score: 1

      MP3 causes me physical pain in my ears for certain types of music that OGG does just fine. Feels like I have an ear ache with a bunch of pressure that eventually turns into a migraine if continued. MP3 is crap.

    40. Re:Why do we need H.265? by im_thatoneguy · · Score: 1

      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 continues to do real business with reasonable terms. By the time Technicolor et-all's stock holders realize that they aren't making anything off of their ludicrous terms they'll have moved on to the next scam.

    41. Re:Why do we need H.265? by bzipitidoo · · Score: 1

      Never ceases to amaze me how much influence ideology has on technical matters. Some people behave as if ownership and proprietary licensing sanctifies a product. They really believe that the profit motive guarantees that quality is better and trustiness is higher. They feel comforted when there is a big organization backing the product. And not just any organization, but a for profit corporation that appears to hold the same values as they do. Non-profits are suspect. They wish to peddle their own products, grow their market, and increase market share and stock valuation, in a similar matter. That many customers might have different ideas is dismissed and ignored, or treated with suspicion and fear accompanied by shrill cries of theft, socialism, and treason against the American way. These feelings and motives trump mere technical merits as reason for choosing one product over another.

      Unintentionally, MS has done much to disabuse people who hold such notions.

      --
      Intellectual Property is a monopolistic, selfish, and defective concept. It is "tyranny over the mind of man"
    42. Re:Why do we need H.265? by StreamingEagle · · Score: 1

      HEVC / H.265 was developed by the Joint Collaborative Team on Video Coding, a combination of ISO's MPEG and ITU's VCEG. The contributors to the HEVC standard agreed to license their technology on FRAND terms, just as all ISO and ITU standards developers do.

  3. HTML 5 by Anonymous Coward · · Score: 0

    Good thing they kept this out of the HTML spec...oh wait...

  4. Yep, like JPEG2000 by Anonymous Coward · · Score: 0

    Yep, and it works well.

    Really this should hopefully go the same way of JPEG2000. JPEG is good enough and more compatible and so people simply didn't want to pay for it.

  5. How much is 0.5% of zero? by JoeyRox · · Score: 1

    Because that's exactly what HEVC is going to get if they pursue this.

    1. Re:How much is 0.5% of zero? by Anonymous Coward · · Score: 0

      They will just raise the rate to 100%.

      100% of 0 must be more than 0.5% of zero.....

  6. Will Drive Sites To Use VP9 by mentil · · Score: 1

    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.
    Smaller sites can use HEVC and noone will care to collect, larger sites will use VP9 or AVC.

    --
    Corruption is convincing someone that the selfless ideal is the same as their selfish ideal.
    1. Re:Will Drive Sites To Use VP9 by stevedog · · Score: 1

      You know, that actually sounds halfway plausible. Wouldn't it be crazy if the entity who finally got the US patent system reformed ended up being RIAA/MPAA? Of course, in that scenario, "reformed" would probably end up meaning some scheme where any digital file produced or consumed within the US or any country that has an internet connection to the US has to pay them a fee...

    2. Re:Will Drive Sites To Use VP9 by Dwedit · · Score: 1

      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.

  7. That may well be what happens by Sycraft-fu · · Score: 1

    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.

    1. Re:That may well be what happens by maorb · · Score: 1

      Remember that some people (myself NOT included thankfully) have to deal with data caps. Companies have to factor in the potential loss of users who can't cope with the large video sizes this solution results in. Until data caps are gone from the majority of connections they could be a major deciding point for what video formats end up most popular in the long run.

    2. Re:That may well be what happens by tlhIngan · · Score: 4, Informative

      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.

      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.

    3. Re:That may well be what happens by Skapare · · Score: 1

      eventually the data caps will go up ... along with the royalties and fees on the captive technology we got stuck with early on.

      --
      now we need to go OSS in diesel cars
    4. Re:That may well be what happens by phantomfive · · Score: 1

      But some patent holders (including the likes of GE and others)

      I'm kind of surprised GE has patents on software video compression.

      --
      "First they came for the slanderers and i said nothing."
  8. So glad its a HTML 5 standard by Billly+Gates · · Score: 2, 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!

    1. Re:So glad its a HTML 5 standard by HiThere · · Score: 0

      ??? Only recourse??

      FWIW, I don't have flash installed AND,/B> I don't have html5. And most places I don't have javascript. (Actually, I may have some parts of HTML5, but not most of it.)

      What recourses you have depends on what services you consider essential, and I don't consider playing videos to be essential, and even consider it detrimental.

      --

      I think we've pushed this "anyone can grow up to be president" thing too far.
    2. Re:So glad its a HTML 5 standard by Anonymous Coward · · Score: 0

      The correct answer is not to go back to Flash, it's to use H264 until the license terms are fair.

    3. Re:So glad its a HTML 5 standard by Goaway · · Score: 1

      You are confusing h.264 and h.265. Nothing you said makes any sense.

    4. Re:So glad its a HTML 5 standard by Anonymous Coward · · Score: 0

      You are confusing h.264 and h.265. Nothing you said makes any sense.

      It's the same patent holders using the same ruse to squeeze more money from everyone. Even if you do not pay it directly yourself, you're paying them fees for it with every device you buy that supports them. This is the singular reason why these company bandied together, it creates a barrier to entry if you're not part of the club, and it generates tens of millions per month just for a few algorithms they've blocked from anyone else implementing, even via a cleanroom.

      Now look at what mega corporations are behind it. Ooh, you say, are those the same that do the double irish dance to avoid paying taxes? Indeed they are!

    5. Re:So glad its a HTML 5 standard by 605dave · · Score: 1

      It doesn't have to make sense if you really, really believe it.

      --
      Be kind, for everyone you meet is fighting a difficult battle. - Plato
    6. Re:So glad its a HTML 5 standard by HiThere · · Score: 1

      Sorry about that unclosed tag. I hit submit when I was reaching for preview. And there's no way to edit after submission.

      --

      I think we've pushed this "anyone can grow up to be president" thing too far.
    7. Re:So glad its a HTML 5 standard by Anonymous Coward · · Score: 0

      i'm standing on your lawn.

  9. Oh what the hell.. by fustakrakich · · Score: 2

    Can't we just wait 20 years, and then use the codec?

    --
    “He’s not deformed, he’s just drunk!”
    1. Re:Oh what the hell.. by SuricouRaven · · Score: 2

      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.

    2. Re:Oh what the hell.. by stevedog · · Score: 2

      Of course! Then, when that day comes, we can all go listen to all our public domain Beatles music to celebrate.

    3. Re:Oh what the hell.. by fustakrakich · · Score: 1

      The old codec cannot use new encoding techniques, unless a time machine is involved somehow. For H.264, it looks like 2028 is the year to celebrate its freedom from human bondage, so unfortunately there is still a lot of time left. If governments are going to issues patents, they also have an obligation to control licensing and pricing to avoid this kind of abuse.

      --
      “He’s not deformed, he’s just drunk!”
    4. Re:Oh what the hell.. by fustakrakich · · Score: 1

      What makes you think the Beatles will ever be public domain? We're still waiting for Steamboat Willie... Copyright has become indefinite.

      --
      “He’s not deformed, he’s just drunk!”
    5. Re:Oh what the hell.. by SuricouRaven · · Score: 1

      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.

    6. Re:Oh what the hell.. by fustakrakich · · Score: 1

      Right, so use the old algorithm when the patent runs out. A new algorithm based on the old one does not 'revive' the old patent, does it? That would suck.

      --
      “He’s not deformed, he’s just drunk!”
    7. Re:Oh what the hell.. by SuricouRaven · · Score: 1

      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.

  10. Who would use this... by Anonymous Coward · · Score: 0

    Over free and open source ones...

  11. Error 500 repeatedly by Anonymous Coward · · Score: 0

    Who the hell is administering this website - a circus clown?

  12. OPUS is the future. by thexfile · · Score: 1

    OPUS is a lot better and free.

    1. Re:OPUS is the future. by Anonymous Coward · · Score: 0

      OPUS is a lot better and free.

      This article is about video encoder, not audio encoders.

  13. There is no future for patented codecs by Anonymous Coward · · Score: 0

    Open source drives all the innovation, these days. If patents are not compliant with the licenses under which most software is released, it will pretty much cause the technology to fade into irrelevance. Issuing patents for ridiculous and esoteric things, that are little more than optimisations or minor tweaks, and then making the core specification dependent on these patents is nothing short of racketeering, and is pure huckterism at its worst.

    1. Re:There is no future for patented codecs by Anonymous Coward · · Score: 0

      I think you're conflating the patents themselves with the licensing. Many royalty-free licensed codecs are covered by patents such as, for example, baseline JPEG, VP8 and VP9. Cisco's new Thor video codec for netvc is covered by patents Cisco owns and has chosen to license under royalty-free terms.

      Patents and the terms patents are licensed under are separate issues.

  14. They do it because of VR by Begemot · · Score: 1

    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 terms.
    Just because they can.

    1. Re:They do it because of VR by squiggleslash · · Score: 1

      I get the impression H.265 isn't good enough given what you suggest it needs to do. It's only a 50% reduction in bandwidth compared to H.264. The fact Carmack can just casually announce he's dropping support suggests that the industry itself didn't see it as much more than a convenience.

      --
      You are not alone. This is not normal. None of this is normal.
  15. Xiph and lawsuits by DrYak · · 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.

    --
    "Sufficiently advanced satire is indistinguishable from reality." - [Tips: 1DrYakQDKCQ6y52z6QbnkxHXAocMZJE61o ]
    1. Re:Xiph and lawsuits by gnasher719 · · Score: 1

      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.

  16. NetVC by bstrobl · · Score: 2

    The netvc Project (https://datatracker.ietf.org/wg/netvc/charter/) aims to create a video codec that is royalty free and better than current codecs using technologies from multiple contributors.

    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 codec is any indication, this should work out quite nicely :)

  17. More than one way.... by DrYak · · Score: 1

    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? Try something else.

    Dirac/Schroedinger by BBC has show that you can use wavelets instead.

    Daala by Xiph is on the way of showing that lapped transforms + perceptual vectors + range coding work too.

    ----
    *:And even then in that situation, there might be efficient way to do the same thing while doing it differently enough to not be patented.
    On2/Google/Xiph have repeatedly shown that with the various VPn codecs being close to the MPEG/H26x, with the patended bit swapped out.

    --
    "Sufficiently advanced satire is indistinguishable from reality." - [Tips: 1DrYakQDKCQ6y52z6QbnkxHXAocMZJE61o ]
  18. Only if the cost justify it by Anonymous Coward · · Score: 0

    If the cost saved in bandwidth is above 0.5% of profit, yeah sure that is worth it. but I get the feeling it isn't the case, otherwise so many firms would not protest and adoption brake with 4 hooves.

    1. Re: Only if the cost justify it by Anonymous Coward · · Score: 0

      Is the cost creating silicon for VP9 to put in android devices, the licence across the device industry cheaply, less the googles savings on bandwidth? Bandwidth prices good down all the time, but content price is not expected to. So a saving today is not the same saving in 10 years time, but by ensuring there is hardware support for VP9 in portable devices. Everyone who is not the MPEG group stands to gain.

  19. HW support by sanf780 · · Score: 2

    From what I gather, H264 and H265 may be supported by hardware (HW) today, and their HW decoders can be pretty efficient on portable devices. If you look at recent Apple devices, their main chips do support both decoding and encoding of both video formats. VP9 HW support is championed by Google, as far as I can see from an advert / white paper on www.deepchip.com . I assume Google will try to make all Android phones VP9 friendly, but I am not so sure what is the status right now. I suppose that VP9 is probably used by YouTube when you use Chrome as a web browser.
    Anyone else does know better than me?

  20. Revenue, not profit by Overzeetop · · Score: 1

    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.

    --
    Is it just my observation, or are there way too many stupid people in the world?
  21. Whatever codec NVidia and AMD will support in HW by Anonymous Coward · · Score: 0

    is the one that will win in the end. This also means that whatever favors American corporations, will usually win.

  22. I've never understood... by FrozenGeek · · Score: 1

    ...why any "standard" would include patented technology. Seems like a very stupid idea. About the same as copyrighting the spelling of words.

    --
    linquendum tondere
    1. Re:I've never understood... by gnasher719 · · Score: 1

      ...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, some guys with patents wanting unacceptable amounts of money. So the expectation is that the potential licensors will say "f*** that, we stay with h.264" and the standard is dead in the water, until these patent holders irrevocably agree to cut down their license fee demands. And make more money by getting a small amount of money from everybody rather than getting a huge amount from nobody.

  23. Ominous cloud on the horizon... by QuietLagoon · · Score: 1
    The increasing use of the proprietary video codecs in everyday software and devices is not a good trend for consumers.

    .
    As we are beginning to see, once the codecs become an essential facility, patent fees will start to be extracted from the users.

  24. Vorbis vs. Licensing terms of WMA by DrYak · · 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 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.

    --
    "Sufficiently advanced satire is indistinguishable from reality." - [Tips: 1DrYakQDKCQ6y52z6QbnkxHXAocMZJE61o ]
  25. Vorbis in Europe by DrYak · · Score: 1

    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 in the US is an entirely different matter.

    --
    "Sufficiently advanced satire is indistinguishable from reality." - [Tips: 1DrYakQDKCQ6y52z6QbnkxHXAocMZJE61o ]
  26. Daala is the future. by DrYak · · Score: 2

    This article is about video encoder, not audio encoders.

    Okay then...

    Daala is a lot better and free.

    ...fixed the original post.

    Is it okay now ?

    --
    "Sufficiently advanced satire is indistinguishable from reality." - [Tips: 1DrYakQDKCQ6y52z6QbnkxHXAocMZJE61o ]
  27. File size and Transfer Are Important by Anonymous Coward · · Score: 0

    Look at the file size of the same video at 4K resolution. The 4K h.265 file sill be half the size of the 1080p h.264 file. Now look at 8K.

    I don't like working with h.265. It's a ridiculously slow encoding process. But the ability to transfer and store the video is important. CPU utilization is not the only factor.

    one, the less, I agree that CPU utilization is far too high on h.265

    1. Re:File size and Transfer Are Important by terjeber · · Score: 1

      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, but the implementations are still improving.

  28. 4K & 8K by Anonymous Coward · · Score: 0

    Video resolution is increasing and h.264 doesn't fit the requirements anymore.

  29. why bother? by Pharago · · Score: 1

    lets all use libvpx and be done with it

  30. Why not? by allo · · Score: 1

    0.5% sounds fair. And it's especially fair, because it's gratis for non-commercial (possibly open source) products and sites.

  31. uhh... by SuperDre · · Score: 1

    in what way has HEVC advanced any patents on h.265 that isn't already covered in the LAMPEG HEVC license for h.265? One problem though, the 'open source' VP9 (which still is being debated if it really isn't using any patented technology) isn't nearly as good as h.265 (unless you really don't give a damn about real quality)..

    1. Re:uhh... by Anonymous Coward · · Score: 1

      which still is being debated if it really isn't using any patented technology

      VP8 and VP9 do use patented technology, which is why they come with a patent license. The patented technology is licensed under royalty-free terms. The issue of whether or not H.264 patents apply to VP8 or VP9 was resolved with the royalty-free cross licensing agreement Google struck with a number of organisations, including the MPEG LA.

  32. Vorbis in video games, etc. by DrYak · · Score: 1

    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.

    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 target audience already have a hardware chip supporting decoding (e.g.: in the tablet they use to watch Netflix) licensing doesn't matter much for them.

    By asking for more money, H265 / HEVC is losing part of its attractiveness to H264. It compresses video better / gives more quality for the same compression. BUT costs more money.

    On the long term all these are argument in favour of Daala : not only will it eventually produce even better compression (simply on the ground of being based on technology even more advanced), but is not covered by patents.

    --
    "Sufficiently advanced satire is indistinguishable from reality." - [Tips: 1DrYakQDKCQ6y52z6QbnkxHXAocMZJE61o ]