Slashdot Mirror


An Open Source, Royalty-Free AV1 Codec Has Been Released (aomedia.org)

Artem Tashkinov writes: After three years in development the Alliance for Open Media is releasing the royalty-free AOMedia Video Codec 1.0 (AV1) specification. The AV1 codec promises an average of 30 percent greater compression over competing codecs according to independent member tests.
The release of AV1 includes:
  • Bitstream specification to enable the next-generation of silicon
  • Unoptimized, experimental software decoder and encoder to create and consume the bitstream
  • Reference streams for product validation
  • Binding specifications to allow content creation and streaming tools for user-generated and commercial video

104 comments

  1. So, how long before... by Sebby · · Score: 0

    some obscure company (patent troll) claims this violates all their patents?

    --

    AC comments get piped to /dev/null
    1. Re:So, how long before... by Anonymous Coward · · Score: 5, Informative

      There are all SORTS of patents on this codec. But everyone patent owner has agreed (and signed) to make those patents available royalty-free to the AV1 group.

    2. Re:So, how long before... by Anonymous Coward · · Score: 0

      I'm sure MPEG-LA will add some FUD to the mix here.

    3. Re:So, how long before... by Anonymous Coward · · Score: 2, Informative

      They can try. But with 30 companies doing IP Review, I doubt they will.

    4. Re:So, how long before... by TheRaven64 · · Score: 4, Insightful

      Every disclosed patent owner has agreed to make their patents available royalty free. There may be other patent holders who have not disclosed their patent. Patents are not mutually exclusive, if I hold a patent for doing X then you may hold a patent for doing X with Y, so just because my patent is in the pool doesn't mean that AV1 doesn't infringe yours. Expect to see patent trolls with overly broad patents that may or may not actually either apply to AV1 or be valid at all go after smallish (large enough to be worth suing, small enough not to be able to afford a good defence) users of AV1. This has happened with MPEG patents, even though they provide a financial incentive to disclose valid patents that are infringed (anyone with patents in the pool gets a share of the royalties).

      --
      I am TheRaven on Soylent News
    5. Re:So, how long before... by darkain · · Score: 2

      You've got the 1st (Apple), 2nd (Alphabet/Google), 3rd (Microsoft), 4th (Amazon), and 6th (Facebook) most valuable company in the world on the list, plus countless others in the top-50 list. Their lawyers are plentiful to support AV1. (note this list was quickly pulled from a source that is about a year old, I know their rankings have slightly shifted since then, but the main fact still remains that they're the powerhouses of the entire world now)

    6. Re:So, how long before... by Anonymous Coward · · Score: 1

      Spreading fear, uncertainty, and doubt about AV1 is a tactic HEVC patent pools have started to use. Velos Media says it's a nice codec you've got there, it'd be a shame if something happened to it.

    7. Re:So, how long before... by OrangeTide · · Score: 2

      some obscure company (patent troll) claims this violates all their patents?

      if you're that paranoid then best stick with MPEG-2 and MP3 until the patents on AV1 and Opus expire.

      --
      “Common sense is not so common.” — Voltaire
    8. Re:So, how long before... by HermMunster · · Score: 1

      Adding x to y patent doesn't make it novel and thus would invalidate the combo x and y patent. Derivative works are not patentable.

      --
      You can lead a man with reason but you can't make him think.
    9. Re: So, how long before... by Anonymous Coward · · Score: 1

      Apple was not a founding member by they joined as a governing member some time ago.

    10. Re:So, how long before... by AvitarX · · Score: 1

      C'mon man, almost all of us here can count to 50.

      --
      Wow, sent an e-mail as suggested when clicking on "use classic" banner, and got a fast response that addressed my msg
    11. Re:So, how long before... by jellomizer · · Score: 1

      We get patent lawsuits on some of the worlds largest countries who take Patents very seriously. Find some obscure patent troll had made some lame patent in the past that no one would think of even bother looking for because it is so obvious that only a moron would try to Patent it and a moron patent official would approve it.

      --
      If something is so important that you feel the need to post it on the internet... It probably isn't that important.
    12. Re:So, how long before... by roca · · Score: 5, Informative

      It might happen, but it hasn't happened with VP9. It also hasn't happened with Opus.

      Furthermore the AV1 license is structured so that if you sue someone for using AV1, you lose your own rights to use AV1. Thus, only pure-troll entities will be able to initiate such lawsuits. That limitation didn't apply to previous codecs.

    13. Re:So, how long before... by gunner2028 · · Score: 1

      Not necessarily. If the inclusion of x is both novel and not obvious, then the second patent would be valid. However, the holder of the second patent would not be able to practice the second approach (with X and Y) without the consent (i.e., license) from the original patent holder (owner of Y).

      --
      Eloquent words can mask much mischief. Judge Mayer
    14. Re:So, how long before... by ELCouz · · Score: 1

      Oh boy...that's gonna take a while!

    15. Re:So, how long before... by Anonymous Coward · · Score: 0

      It doesn't really matter, because the issue at hand will eventually be settled in a court, where they tend to listen to absurd things like lawyers instead of logic and reason.

    16. Re:So, how long before... by TheRaven64 · · Score: 3, Interesting

      Furthermore the AV1 license is structured so that if you sue someone for using AV1, you lose your own rights to use AV1. Thus, only pure-troll entities will be able to initiate such lawsuits

      That's not a real problem. The normal way for such lawsuits is to spin out a company that does nothing other than own the patents and license them back to the original company. That company can then sue everyone, but doesn't do anything other than license patents so is immune to countersuits.

      --
      I am TheRaven on Soylent News
    17. Re:So, how long before... by TheRaven64 · · Score: 2

      Everything in your comment is incorrect. Please read a little bit about patent law before commenting on it in the future. Derivative works are part of copyright law and have no status in patent or trademark law. Most patents are additive in some way, providing improvements to existing inventions (many of the early ones were refinements on steam engine design, for example), and this property is one of the first things that you'll find in any patent law textbook.

      --
      I am TheRaven on Soylent News
  2. the next-generation of silicon by Anonymous Coward · · Score: 0

    meh we all gonna use germanium instead

  3. Decoding Woes by Anonymous Coward · · Score: 0

    This is awesome, but it's useless until decoder hardware is prevalent. Expect a year of waiting for deployment to make sense, and 3 before the majority of users can handle it. That said, death to h.254 and h.265.

    P.S. Please improve the webm standard to allow multiple audio and subtitle channels. Also add features to switch between these channels in the HTML5 video element. Multilingual videos are important!

    1. Re:Decoding Woes by Anonymous Coward · · Score: 1

      How is it useless? You can easily decode it via software.

    2. Re:Decoding Woes by Bert64 · · Score: 1

      Which requires a powerful and power hungry CPU, probably complete with active cooling...
      Mobile devices won't be able to do it, or won't do it for long before the battery dies.
      TVs and STBs won't be able to do it as they typically contain low power general purpose processors, one containing a powerful general purpose processor would require active cooling and be noisy - not what you want while trying to enjoy a movie.

      It will take a while before this will see much adoption, although its a welcome start.

      --
      http://spamdecoy.net - free throwaway anonymous email - avoid spam!
    3. Re:Decoding Woes by Anonymous Coward · · Score: 1

      There's more to life than PCs. Try decoding h.265 on a phone or tablet that doesn't support hardware decoding. On my three year old Sony tablet, playing back high definition h.265 movies in MX Player with software decoding, the frame rate is unwatchably low, and I hate to think what it does to the battery life. I have to make sure when selecting files for a trip, that I stick to h.264. There's no reason to think AV1 will be any easier to decode in software than h.265. Given that mobile is, you know, quite important, you've got a problem there. Not useless, but you've got to wait until the majority of hardware supports it before it can be widely used.

    4. Re:Decoding Woes by OrangeTide · · Score: 2

      If I'm watching movies on my i7 I don't really care if I'm using a large fraction of my CPU performance in software decode since I'm not really doing anything else with my computer. (I don't normally watch a movie while playing a game and typing up my thesis)

      For STB, you could probably still do software decode on a more powerful one. I haven't tried it yet, but Nvidia Shield might have enough grunt to do the job at 1080p. (I doubt 4K, but I don't have a 4K TV yet)

      --
      “Common sense is not so common.” — Voltaire
    5. Re:Decoding Woes by Anonymous Coward · · Score: 0

      Which requires a powerful and power hungry CPU

      Not by modern standards it doesn't. I just did a quick check. My GPU doesn't handle HEVC decoding, so it has to be done through software. On my five year old, 4th generation mobile i7 software decoding a 1080p HEVC video takes about 6-8% CPU time.

      I seriously doubt that AV1 will be any worse off.

    6. Re:Decoding Woes by Anonymous Coward · · Score: 0

      Software decoding h.265 video on my four year old LG G3 works great, so I don't know what you're talking about.

      Nobody wants to watch video on a tiny screen any way, so it's a moot point.

    7. Re:Decoding Woes by Anonymous Coward · · Score: 0

      You are completely wrong. Most videos in the world are currently watched on phone screens.

    8. Re:Decoding Woes by Anonymous Coward · · Score: 0

      [citation needed]

    9. Re:Decoding Woes by Anonymous Coward · · Score: 0

      On my desktop sure, on my laptop i disagree.
      It will also be a few years until it will even be supported on new cheap streaming devices such as Chromecast, AppleTV, Roku and Smart TVs.

    10. Re:Decoding Woes by Anonymous Coward · · Score: 0

      Bullshit, sorry. Your G3 has a Snapdragon 801, which supports hardware decoding of h.265 up to 1080p, one of the earlier chips to do so. You are using hardware decoding, not software.

      And I watch movies on my tablet on every flight; the screen is only slightly smaller that the cattle class seat-back screens, much better quality, and my movies don't get interrupted by the in-flight announcements.

    11. Re:Decoding Woes by Anonymous Coward · · Score: 0

      Which requires a powerful and power hungry CPU, probably complete with active cooling...

      Isn't progress great? Just a few minutes ago, it was "useless!" Now suddenly there are hundreds of millions of machines, already deployed all over the world, in the hands of end-users and developers alike, that can use it.

    12. Re:Decoding Woes by Anonymous Coward · · Score: 0

      Bullshit, sorry. Your G3 has a Snapdragon 801, which supports hardware decoding of h.265 up to 1080p, one of the earlier chips to do so. You are using hardware decoding, not software.

      Bullshit yourself. The MSM8974AC Snapdragon 801 in the G3 does NOT have h.265 hardware decoding, it has a SOFTWARE codec. You don't know what you are talking about.

      And I watch movies on my tablet on every flight

      YOU do. Most people don't.

  4. Unoptimized by Anonymous Coward · · Score: 1

    Judging from other open source software, that will be a show stopper. Having millions of eyes on the code does not automatically cause the owners of those eyes to give up their day job to hunker down and turn the code into something productive and efficient.

    1. Re:Unoptimized by afidel · · Score: 3, Insightful

      What are you talking about? The opensource implementations of MP3 and H264 quickly outpaced every commercial implementation, I would expect the same for this codec. What they won't be able to do is compete with embedded hardware implementations that will come but history has shown that the opensource version will be less efficient but more feature rich than those hardware implementations.

      --
      There are 4 boxes to use in the defense of liberty: soap, ballot, jury, ammo. Use in that order. Starting now.
    2. Re:Unoptimized by Anonymous Coward · · Score: 0

      Define quickly. I've been around for a long time, and the open source implementations of all the codecs were vastly inferior compared to their commercial counterparts for many, many years.

      Open source is good for 30 year old software, e.g. Unix, Lisp, Prolog, etc, but is hardly cutting edge.

    3. Re:Unoptimized by afidel · · Score: 1

      LAME was indisputably better than Fraunhofer by 2001. The project started in 1998, 3 years to beat the company that did most of the research behind the standard is pretty damn quickly.

      --
      There are 4 boxes to use in the defense of liberty: soap, ballot, jury, ammo. Use in that order. Starting now.
    4. Re:Unoptimized by arth1 · · Score: 2

      What are you talking about? The opensource implementations of MP3 and H264 quickly outpaced every commercial implementation,

      Really? I used the commercial Fraunhofer MP3 implementation for almost a decade, because the open source Lame was both more resource hungry and gave more artefacts. That's not my definition of "quickly".

    5. Re:Unoptimized by sexconker · · Score: 1

      LAME did this by infringing on patents and copyrighted code.

      It's called "Lame Ain't an MP3 Encoder" because of this. They hid behind the claim that they're only doing this for research and are only creating source code, not an encoder. Of course, we all know LAME is in fact an MP3 encoder. All you have to do is compile it or download a compiled binary from someone else who did that step for you.

      See Microsoft, DivX, and XviD for a similar situation in video.

    6. Re:Unoptimized by tepples · · Score: 1

      LAME was indisputably better than Fraunhofer by 2001.

      LAME did this by infringing on patents and copyrighted code.

      Grandparent said 2001. LAME had already removed all of ISO's copyrighted demo code by May 2000. The patents were an issue only because compression users hadn't yet begun to push toward royalty-free codecs. By that time, Xiph's Vorbis encoder was handily beating both LAME and Fraunhofer's MP3 encoder in rate-distortion performance.

    7. Re:Unoptimized by afidel · · Score: 1

      Yes, but the argument was that the opensource development model can't make a superior implementation quickly, that is demonstrably false and patents and copyright will not be an issue with this open royalty-free standard.

      --
      There are 4 boxes to use in the defense of liberty: soap, ballot, jury, ammo. Use in that order. Starting now.
    8. Re:Unoptimized by sexconker · · Score: 0, Troll

      The original point in this thread is that this is completely unoptimized, and being open source doesn't magically fix that.
      Someone pointed to LAME as being better than commercial solutions, but that's only true because got where it is by stealing and copying.

      Further, by the time LAME surpassed commercial solutions it was largely because those commercial solutions were done. No further spec changes, no further development, no further optimization. Instead, they were busy working on specs for the next generation of codecs.

      The same exact thing happened with MPEG 4 video.

      MPEG is shit, and the patents involved are a ridiculous mess and I'd like for almost all of them to be thrown out.
      But the simple fact is the open codecs have historically succeeded by stealing from the closed codecs and them hammering away on them long after the creators of the closed codecs had moved on.

      In the end, designing codecs isn't easy, nor is it free in terms of time/money (the only things that matter for getting shit done). However shitty MPEG is, you have to give the devil his due.

    9. Re:Unoptimized by sexconker · · Score: 0

      It's not demonstrably false. They haven't so far shown that they can do that. The major successes so far have all infringed on patents and stolen code, even if they later clean up the act to remove infringing bits.

      LAME, DivX ;-), XviD, x264, and x265 are the major successes of open codecs so far. (Though DivX ;-) became DivX, was bought by Fraunhofer, wasn't fully open/free, etc., its origins are still in the same camp.) All of these have their roots in the tainted swamp of code theft and patent infringement.

      I don't care either way. People have been saying h264 and h265 were unusable. Yet I've been using them without any issue.
      What I care about is the efficiency, performance (decode mainly, I'm willing to wait overnight for an encode), and compatibility.

    10. Re:Unoptimized by Anonymous Coward · · Score: 0

      You need to look up the definition of the word "stealing".

    11. Re:Unoptimized by Anonymous Coward · · Score: 0

      they are unusable because of its licensing. are you that dump?

    12. Re: Unoptimized by Anonymous Coward · · Score: 0

      Resource hungry? What were you using? A 486dx/50? Also, LAME was always better at the bitrates that quality audiophiles care about. If you are happy with 96Kbps joint stereo, thats another story.

    13. Re:Unoptimized by Anonymous Coward · · Score: 0

      What if the day job of many of those eyes is the open source code? Reference implementation is what you're referring to, surely? 3000 times slower was a figure that was tossed around only few months ago.

    14. Re: Unoptimized by arth1 · · Score: 1

      Also, LAME was always better at the bitrates that quality audiophiles care about.

      No, it wasn't. In the early days, lame was all about VBR, which no audiophile would touch with a conductor's pole. VBR sounds shitty, because of the quality changes being so readily detectible. A change back and forth between good quality and very good quality is more perceptible than a track that stays at mediocre quality.
      For 320 kbps, Fraunhofer had the upper hand, especially for encoding quality (you can tell whether an old MP3 uses FH or lame based on whether high hats sound like being stricken by a bag full of broken glass).
      For the other end of the spectrum, the very lowest bitrates in mono, Fraunhofer created smaller files, which was important to some, especially for things like 12 hour long audiobooks.

      The one thing lame excelled at in the early years was VBR, which was ok for the pop music crowd who wanted to fit more songs in limited space and didn't really are about sound quality, just loudness. It wasn't like you could make a Nickelback or Oasis album sound much worse, quality wise, than it already did.

    15. Re: Unoptimized by Anonymous Coward · · Score: 0

      Bullshit. LAME is superior in every single metric and under every single setting. It produces smaller files and better sound.

      You just don't know what the fuck you're doing, noob.

  5. Some caveats by Artem+S.+Tashkinov · · Score: 4, Informative

    As with VP9 earlier, the first reference AV1 encoder is absolutely slow: currently it's an order of magnitude slower than x265's veryslow preset (which is extremely slow to begin with).

    AV1 is not currently supported by anything under the sun except an alpha build of Firefox (where it struggles to decode even a 3Mbps video on powerful PCs).

    Most likely ffmpeg will include its own decoder (implementation) because ffmpeg and AV1 developers have contradicting views on coding styles. ffmpeg has its own VP9 decoder.

    Apple joined the alliance just a few months ago when the development was almost over, which means Apple most likely didn't really contribute to it at all.

    The spec is 619 freaking pages long.

    1. Re:Some caveats by Anonymous Coward · · Score: 4, Interesting

      As with VP9 earlier, the first reference AV1 encoder is absolutely slow: currently it's an order of magnitude slower than x265's veryslow preset (which is extremely slow to begin with).

      At 40% better efficiency than x265, slowness is a given and perfectly forgivable. For all intents and purposes it's like a next generation codec, but license free. Now it "just" needs the hardware to enable it as a viable choice.

      Apple joined the alliance just a few months ago when the development was almost over, which means Apple most likely didn't really contribute to it at all.

      I don't see it being a problem except maybe for Apple. The fact they joined shows they reckon its value and I guess it's more than enough "contribution" at this point.

    2. Re:Some caveats by Anonymous Coward · · Score: 0

      I disabled VP9 on Youtube for Firefox so can get normal h264. All those new codecs are sucking CPU, which is more important than some extra bandwidth on desktop computer.

    3. Re:Some caveats by TigerTime · · Score: 3, Informative

      Damn, give it some time. It was just released. When looking at things like this, you have to look at the backing and support it gets.

      Give it a year or so, and see where we're at. This codec is here to stay, and while the encoding speeds are slow now, it has an enormous backing to win in the end.

    4. Re:Some caveats by afidel · · Score: 2

      VP9 is partially hardware accelerated on Broadwell+, fully on Kaby Lake+, and fully with either major GPU platform with recent GPUs. If you've got legacy equipment and are trying to multitask while Youtube videos play then I guess the difference might matter, otherwise why would you care?

      --
      There are 4 boxes to use in the defense of liberty: soap, ballot, jury, ammo. Use in that order. Starting now.
    5. Re:Some caveats by Artem+S.+Tashkinov · · Score: 2

      VP9 is hardware accelerated in Firefox but only if you're on Windows 10 and have an appropriate CPU/GPU: Intel Skylake or better; NVIDIA Maxwell Gen2/Pascal; AMD Polaris/Vega ;-)

      I'm not aware of other web browsers but Chrome and Edge might support hardware decoding on Windows 10 as well.

      As for Linux it's all very sad - even H.264 is not hardware accelerated.

    6. Re:Some caveats by Anonymous Coward · · Score: 0

      At 40% better efficiency than x265, slowness is a given and perfectly forgivable

      If you don't mind keeping your system on 24/7 and just encoding in the background. x265 10bit on slow with some extra speedups and slowdowns to increase the dynamism of the coding (ssim-rd=1:aq-mode=3:amp=1:rect=1:limit-modes=1:early-skip=1:bframes=6) is what I like to use. I really hope the AV1 encoding gets as near to the h265 as possible as fast as possible at equivalent or better quality, as software VP9 is still much too slow to be used for me.

    7. Re:Some caveats by Anonymous Coward · · Score: 1

      Haswell or Radeon 7970 or xyz_hardware aren't exactly legacy equipment. These days "legacy" hardware can be an order of magnitude faster than brand new hardware, or the other way around, depending on how high end or cutting edge was what you bought five years ago, or depending on the hardware's power budget.
      In a way things are like they were in the 80s or early 90s : an Amiga 500 wasn't legacy in 1992, an IBM PC or Apple II or Commodore 64 wasn't legacy in 1987.

    8. Re:Some caveats by MachineShedFred · · Score: 3, Informative

      Who cares when Apple joined, as long as they did. That's a big pool of patents that they've owned for a long time that became available to the group, and some very deep pockets that can help defend (or at least won't sue).

      With Apple, Microsoft, Google, Intel, Nvidia, AMD on board, it's a done deal. In 18 months it will be difficult to find a shipping device that doesn't support AV1 at some level.

      Fuck MPEG-LA. Couldn't happen to a nicer bunch of assholes.

      --
      Slashdot still doesnâ(TM)t support Unicode after it was added to the HTML standard in 1997.
    9. Re:Some caveats by JesseMcDonald · · Score: 1

      As for Linux it's all very sad - even H.264 is not hardware accelerated.

      Hardware decoding of H.264 is supported under Linux through VA-API on Intel GMA 4500, Ironlake Graphics and newer, and AMD Radeon HD 4000 and newer. It is also supported through VDPAU on AMD Radeon HD 4000 and newer and nVidia GeForce 8 and newer. There are adapter libraries available in case you need to use a VA-API client with VDPAU drivers or vice-versa. Accelerated encoding is also supported on certain hardware.

      The above is based on the Hardware video acceleration page on the Arch Linux wiki, and my own experience with hardware decoding on Intel graphics hardware with the Debian VA-API drivers.

      If you're referring specifically to hardware H.264 decoding support in Firefox, AIUI hardware decoding support has been included in the last few versions but may be disabled by default, requiring some tweaks to the preferences.

      --
      "The state is that great fiction by which everyone tries to live at the expense of everyone else." - Bastiat
    10. Re:Some caveats by Artem+S.+Tashkinov · · Score: 1

      If you're referring specifically to hardware H.264 decoding support in Firefox, AIUI hardware decoding support has been included in the last few versions but may be disabled by default, requiring some tweaks to the preferences.

      I was talking specifically about web browsers (since the original poster was talking about the difficulties of playing VP9 content on youtube). I'm perfectly aware that Mplayer/ffmpeg has had HW decoding acceleration for many years already - in fact I use VDPAU all the time.

    11. Re:Some caveats by kriston · · Score: 1

      Does VP9 hardware acceleration automatically include WebM? I'm assuming so because their web site still mentions VP9 all over the place years after WebM came out.

      Example:
      https://www.webmproject.org/ha...

      --

      Kriston

    12. Re:Some caveats by kriston · · Score: 1

      Ummm, nevermind. I'm conflating containers and codecs.

      --

      Kriston

    13. Re:Some caveats by Anonymous Coward · · Score: 0

      Bravo. The first one that realized this by themselves :)

    14. Re:Some caveats by shaitand · · Score: 1

      "As with VP9 earlier, the first reference AV1 encoder is absolutely slow: currently it's an order of magnitude slower [doom9.org] than x265's veryslow preset (which is extremely slow to begin with). "

      Sure but that reference encoder isn't even optimized. People are going a little crazy assuming this will need dedicated hardware to become useful when it was designed to be easy to optimize and has not yet been optimized. Bitching because the brand new shiny and cool codec isn't as mature as the codecs of 5-6yrs ago is a little ridiculous.

  6. CPU encode/decode killer by Anonymous Coward · · Score: 0

    "It takes about 150 seconds on an off-the-shelf desktop computer to encode one second of video."

    1. Re:CPU encode/decode killer by MachineShedFred · · Score: 2

      crawl -> walk -> run

      I'm pretty sure Nvidia, Intel, and AMD have something to say about that.

      AOMedia has the math working, and a published spec. Now they go over the code and make it faster, and work with the hardware guys. With the general hate for MPEG-LA out there, I wouldn't be surprised if in three years we look back on H.264 the way we look at MPEG-2 today. Man, that was a great standard back in the day, but the files are HUGE compared to AC-1!

      --
      Slashdot still doesnâ(TM)t support Unicode after it was added to the HTML standard in 1997.
  7. DRM? by Anonymous Coward · · Score: 0

    Someone will kill it if it's not DRM

  8. MPEG by Anonymous Coward · · Score: 1

    How badly did they screw up for things like this to happen. Making the competitors (Amazon, Google, Apple, Netflix, etc) come together to make a replacement.

    1. Re:MPEG by Anonymous Coward · · Score: 4, Informative

      So badly that the chairman of MPEG says HEVC is unusable.

    2. Re:MPEG by Anonymous Coward · · Score: 0

      The web could have done with an open video codec 20 years ago, so MPEG managed to forestall the inevitable for two decades.

  9. sort of hardware decoding by DrYak · · Score: 4, Interesting

    This is awesome, but it's useless until decoder hardware is prevalent.

    The plan is that the initial quick deployment of it will rely on shader code, so decoding will be hardware accelerated, but GPGPU instead of dedicated hardware code.

    On the other hand, you have a bunch of hardware manufacturer on the board too (dedicated hardware manufacturer like Broadcom, GPU manufacturer AMD, ARM, Intel, Nvidia) and they have been taking part in the process, guiding selection of some technology (the reason why ANS was dropped in favor of Daala_ec, as it's more hardware friendly, etc.)
    They have probably already started testing hardware implementation while the development process was going on. So maybe AV1 spetialized decoding cores might show up faster than expected.

    --
    "Sufficiently advanced satire is indistinguishable from reality." - [Tips: 1DrYakQDKCQ6y52z6QbnkxHXAocMZJE61o ]
  10. h265 by DrYak · · Score: 4, Informative

    Which requires a powerful and power hungry CPU, probably complete with active cooling...
    Mobile devices won't be able to do it, or won't do it for long before the battery dies.

    Which is *also* the case with h265, mostly due to the patent minefield and high licensing costs causing lots of hardware manufacturer to backtrack on their intentions to feature dedicated h265 cores in their latest hardware.

    Which is the whole reason Daala, VP10 and the other pieces of what eventually combined into AV1 were started in the first place.
    Except for a few select phone (Apple's iPhone) lots of (cheaper) mobile devices haven't started getting real h265 decoding, neither.

    And again, AV-1 was designed to be GPGPU friendly.

    --
    "Sufficiently advanced satire is indistinguishable from reality." - [Tips: 1DrYakQDKCQ6y52z6QbnkxHXAocMZJE61o ]
    1. Re:h265 by Anonymous Coward · · Score: 0

      GPGPU friendly is probably useful for people with gaming hardware (perhaps including some midrange graphics cards of a few years ago) or very recent laptops.
      It will be interesting to see what goes on Raspberry Pi 2 and 3 - which I think supports GPGPU, but if it works at all that's because it's in a special situation with a ton of users making it the only well supported ARM hardware on Earth (maybe an exaggeration). There's decoding and decoding : I would want to figure out if it can decode 480p or 360p :) forget about 1080p or 2160p?

      Your average Android 5 phone, or dual/quad core Atom laptop, or Core 2 Duo desktop/laptop, or (...) either the GPU will be not powerful enough or incompatible with the OpenCL standard you ask of it?

    2. Re: h265 by Anonymous Coward · · Score: 0

      My Nvidia shield TV decodes h.265 just fine. The device is older than the h.265 standard. If it wasn't for the license fees much more hardware would support h.265.

  11. Preliminary support by DrYak · · Score: 3, Informative

    VLC has also preliminary AV1 support (since 3.0).
    G-Streamer has too (since 1.14)

    Bitmovin has started offering experimental AV1 cloud compression for quite some time.

    And given the long list of companies involved, more is going to come any moment soon.

    --
    "Sufficiently advanced satire is indistinguishable from reality." - [Tips: 1DrYakQDKCQ6y52z6QbnkxHXAocMZJE61o ]
  12. patent troll comes calling by Lead+Butthead · · Score: 1

    ... like say... RAMBUS?

    --
    ELOI, ELOI, LAMA SABACHTHANI!?
  13. Standards by ArhcAngel · · Score: 3, Funny

    How was this not the first post?

    --
    "A person is smart. People are dumb, panicky dangerous animals and you know it." - K
    1. Re:Standards by tepples · · Score: 1

      "14 competing standards"?

      I guess you could say AV1 came into being because HEVC was failing to compete in a licensing sense.

    2. Re:Standards by Anonymous Coward · · Score: 0

      Video codecs compete the same way as floppy drives compete with USB flash drives. Decades of difference in performance and usability. Likewise AV1 compresses video probably 100 times better than MPEG1 which was released 25 years ago and which doesn't support bitrates above 1.5Mbps. // b.

    3. Re:Standards by OrangeTide · · Score: 1

      Yea, no shit. It's a bit like arguing that we don't need geometry, trigonometry and Calculus because natural number arithmetic is the oldest standard for mathematics.

      --
      “Common sense is not so common.” — Voltaire
    4. Re:Standards by Anonymous Coward · · Score: 0

      It doesn't apply. When there is one standard for next-generation video compression and it's basically unusable because of the monetary cost and legal hassle of actually getting all the patent licensing you need, you don't have a standard at all.

      Now we do.

  14. Sure Linux has hardware accellerated h264 by Anonymous Coward · · Score: 0

    Just get a NVIDIA TX2. Linux/quad arm/gpu/hardware video encode and decode.

  15. GPGPU by DrYak · · Score: 1

    The plan of AOMedia was to shift the work to the GPU as soon as possible (think Vulkan/OpenCL compute shader)

    And given the names on the list (several hardware manufacturers), you can bet that dedicated hardware AV1 cores are going to come next after that, much sooner speed than you would otherwise expect.

    --
    "Sufficiently advanced satire is indistinguishable from reality." - [Tips: 1DrYakQDKCQ6y52z6QbnkxHXAocMZJE61o ]
  16. Web by DrYak · · Score: 1

    it's targetting web.
    on the web, DRM is handled at another level (EME - encrypted media extensions).
    video codecs are orthogonal to it.

    basically, content providers don't pay attention if AV1 supports DRM or not (it doesn't).
    What interests them is if the browser supports widevinecdm (it does if you browser can play netflix).

    --
    "Sufficiently advanced satire is indistinguishable from reality." - [Tips: 1DrYakQDKCQ6y52z6QbnkxHXAocMZJE61o ]
  17. HD4770 by Anonymous Coward · · Score: 0

    It was released in 2009 at 960 GFLOPS @ 85 watts @ 40nm. Capable of running up to 2x that with overclocking and a voltage mod. While in theory you can get an RX460/560 at a similiar pricepoint and 2-2.5x the performance, it is still a perfectly capable card for gaming and other purposes if the applications can work within its hardware constraints. Honestly the biggest issues today are the lack of OCL 1.0/1.1 emulation in Mesa and everything jumping to OGL 4.x/Vulkan 1.x as minimum for their renderers. As far as performance is concerned the card is still more than adequate unless you need more VRAM (Only had 512M 128bit GDDR5), OCL 1.2 support, or 2160p displays (it supports up to 2560x1600 with dual link DVI and had two DVI plus Component standard.)

    1. Re:HD4770 by Anonymous Coward · · Score: 0

      I switched from my 4850 to a 750ti when that launched due to buggy drivers (both FGLRX and open source drivers).
      FGLRX performed very in 3D games well but had horrible tearing when watching videos.
      Open source drivers back in the day didn't tear but performed very badly with random stutters in Source games.
      The open source driver probably performs much better now, but I just couldn't stand it any longer back then.
      Will go back to a AMD GPU when either I buy a 4K monitor, 2-3 year old games performs less than 30fps or the card completely dies on me.

  18. Founder of MPEG discussed this on his blog. by Anonymous Coward · · Score: 0

    They had reduced the patent burden, but hadn't gone far enough with their requirements for licensing in a fair manner. He personally is fine with MPEG dying if AOMedia is successful, because the mission goal of MPEG was basically to reach that point, in which case it is mission successful to him.

    1. Re:Founder of MPEG discussed this on his blog. by Anonymous Coward · · Score: 0

      He does have problems with MPEG dying. Companies and universities will be more hesitant to invest in video codec research because there won't be any financial gains from it. Due to all surviving codecs being free licenses. He predicted this field could stagnate with only incremental improvements here and there.

    2. Re:Founder of MPEG discussed this on his blog. by Anonymous Coward · · Score: 0

      Saving on bandwidth and storage space may be enough incentive to keep throwing resources at developing new codecs. Just because something is open and you can't sell a license to it doesn't mean there's no financial incentive to keep working on it.

    3. Re:Founder of MPEG discussed this on his blog. by shaitand · · Score: 1

      This:

      "Making the competitors (Amazon, Google, Apple, Netflix, etc) come together to make a replacement."

      Gives a very strong clue as to why free licensed solutions continue to get development. They just get developed by funding from people who actually need the solution rather than a middleman who wants to build it and license to all those people.

  19. Re:Open source doesn't _mean_ anything by OrangeTide · · Score: 2

    I find open source to be useful even in cases where it isn't Free Software. There was a time, in the olden days, when you bought software libraries for development that were distributed as a binary and header. These binary only distributions sometimes required royalties, but it was also common to have been a one time charge and royalty free. Either way it sucked because you could not see how it worked, modified it for your needs, or ported it to a different platform. Then this idea of open source hit the scene and started to change that. You still had to pay for it, and sometimes there were royalties, but at least you could adapt it to your tools and didn't have to wrestle with constantly changing calling conventions between different compilers.

    If all you care about is Free Software, then great. But I don't necessarily have to participate in your personal religious movement to find benefit from open source and meaning and distinction between the terms open source and Free Software.

    --
    “Common sense is not so common.” — Voltaire
  20. think it would never happens by Anonymous Coward · · Score: 0

    finally it's only 6 months late

  21. Re:Open source doesn't _mean_ anything by MachineShedFred · · Score: 1

    Myself, I go for the open sauce solution. Sometimes new jars are way too hard to open, and you have to bang them against the counter to break the seal, etc.

    --
    Slashdot still doesnâ(TM)t support Unicode after it was added to the HTML standard in 1997.
  22. Re:Open source doesn't _mean_ anything by technosaurus · · Score: 1

    Free software also means absolutely nothing. In fact it in the context that the Free Software Foundation uses it, it is the opposite of free as in freedom because it is about restrictions and obligations - the opposite of freedom.

  23. Re:Open source doesn't _mean_ anything by Anonymous Coward · · Score: 0

    You saying something about "open source" doesn't mean anything to anyone else. Stop talking as if you saying is meaningful to others - it isn't.

  24. Re:Open source doesn't _mean_ anything by Anonymous Coward · · Score: 0

    You know what's the state devoid of all rules and regulations - The completely "true" freedom? it's called anarchy.

  25. Re:Open source doesn't _mean_ anything by Anonymous Coward · · Score: 1

    You're half right. Free software copyleft licenses privilege one type of freedom over another.
    Whether you feel it as a restriction or a freedom depends on which part of the software ecosystem you find yourself in, and with which intentions.

  26. Re:Open source doesn't _mean_ anything by Anonymous Coward · · Score: 0

    Nnnnneeee... nope.

    Anarchy != law of the jungle.
    Anarchy -> non-hierarchical social organisation.

  27. Not actually released by Anonymous Coward · · Score: 0

    https://news.ycombinator.com/item?id=16699481

    Bitstream isn't frozen... stuff you encode with this won't necessarily decode correctly in the future.

  28. Huh by SamFooter · · Score: 1

    So I've been checking it out and I can't find anything more than what is described as 'decent" And even that's not all the time. https://droidinformer.org/Stor... This stuff reeks of the corporate empty shell.