Slashdot Mirror


BBC Confirms 50% Bitrate Savings For H.265/HEVC Vs H.264/AVC (bbc.co.uk)

An anonymous reader writes: A research team from the BBC has done a series of tests to confirm earlier computations showing a ~50% savings in bit rate for H.265/HEVC compared to video using H.264/AVC at comparable quality. "The subjective tests used a carefully selected set of coded video sequences at four different picture sizes: UHD (3840x2160 and 4096x2048), 1080p (1920x1080), 720p (1280x720) and 480p (832x480), at frame rates of 30Hz, 50Hz, or 60Hz. The video content was chosen to represent diverse spatial and temporal characteristics, and then coded using HEVC and AVC standards at a wide span of bit rates producing a variety of quality levels." Here is the full published analysis. "The tests confirmed the significant compression efficiency improvements achieved in HEVC, verifying the results previously reported using objective quality metrics (PSNR based methods)." The team did not test against VP9, which is shaping up to be an impressive standard as well.

110 comments

  1. The only thing we need to know is: by Anonymous Coward · · Score: 1

    What is it's Weissman Score?

  2. And still unsupported just about everywhere by Anonymous Coward · · Score: 0

    Another win for the mobile browsers, I guess.

    1. Re:And still unsupported just about everywhere by Ritz_Just_Ritz · · Score: 2

      Now you can consume 4k video on your 3" screen (assuming anyone's mobile device has the grunt to decode it). :)

    2. Re:And still unsupported just about everywhere by alvinrod · · Score: 1

      Mobile devices typically contain physical hardware decoders built in to the SoC so that they don't have to use their CPU cores, which would be much less efficient or practically impossible in the days of slow, single core mobile devices.

      I recall from several years ago when Apple released iMovie for their iDevices, that they could encode videos more quickly than their high-end, vastly more expensive Intel-based computers simply because the dedicated hardware encoder in the SoC could beat the Intel CPUs.

    3. Re:And still unsupported just about everywhere by PRMan · · Score: 3, Insightful

      They contain hardware AVC decoders, not HEVC decoders. This is why YouTube now plays like crap on old netbooks unless you install a plugin that forces MP4 instead of VP9.

      --
      Peter predicted that you would "deliberately forget" creation 2000 years ago...
    4. Re:And still unsupported just about everywhere by Trongy · · Score: 0

      Flagship phones released last year should all have hardware HVEC decoders.

    5. Re:And still unsupported just about everywhere by DrXym · · Score: 1

      The answer is yes you can consume 4K video. And if you do and its encoded with HEVC, you take half the whack on your bandwidth cap. Of course I expect most people would be viewing videos encoded at lower resolutions and bitrates but the savings apply their too - if 4MBs HEVC can show an image subjectively the same as 7MBs AVC then it's a benefit. Not only do they use less bandwidth but they're less likely to suffer buffering issues, or step downs to lower bitrates.

    6. Re:And still unsupported just about everywhere by AK+Marc · · Score: 1

      My 2 year old phone will play 4k, with HEVC. Running bottom of the line hardware for 10 years gets you lots of things that won't work right by the time you finally get rid of it.

    7. Re:And still unsupported just about everywhere by AK+Marc · · Score: 1

      My 2 year old phone will play 4k, with HEVC. So yes, most higher-end new phones should be able to play 4k on their screen (5.5 in my case, your screen may vary).

  3. "comparing" video CODEC quality is very hard... by kbonin · · Score: 5, Interesting

    I've played in this space in a former position. Interesting lessons learned:
    - PSNR is nearly worthless: An image with almost the same score can look terrible. Not all the time, but enough of the time.
    - The only quantitative test I found that worked reliably was an old analog Tektronix PQA500 (lots of work to use for digital CODEC.)
    - Management didn't like the PQA data (it said our product was terrible), decided to use PSNR data (product is great!)
    - Customers fixed this discrepancy and product line failed spectacularly (due to video quality, surprise!)
    - I never could find any published information sufficient to recreate the Tek PQA algorithm.

    1. Re:"comparing" video CODEC quality is very hard... by Fwipp · · Score: 5, Informative

      Which, if you click through, is why the study performed subjective tests; by asking viewers to rate the quality of several videos at several bitrates on a 10-point scale in a series of tests. They found that PSNR systematically underestimated the perceived quality of H.265 (relative to H.264).

    2. Re:"comparing" video CODEC quality is very hard... by kbonin · · Score: 1

      I saw that in the paper, I was hoping someone might know something about Tek's old JND algorithm that's become known since then, or how it performs relative to SSIM or VQM in human subjective studies. Almost all the work in these spaces is patented or commercial...

    3. Re:"comparing" video CODEC quality is very hard... by SuricouRaven · · Score: 2

      Subjective quality perception is a very weird metric. If you add high-frequency random noise, people perceive it as a more detailed image - an optical illusion causing them to interpret small-scale noise artifacts according to their expectation according to surroundings.

    4. Re:"comparing" video CODEC quality is very hard... by Anonymous Coward · · Score: 0

      Subjective quality perception is a very weird metric. If you add high-frequency random noise, people perceive it as a more detailed image - an optical illusion causing them to interpret small-scale noise artifacts according to their expectation according to surroundings.

      I sense an arbitrage opportunity here. Develop a widget to plug in between an HDMI cable and your TV that adds random noise. Sell it as an HD-super-upscaler magic box. Laugh all the way to the bank.

    5. Re:"comparing" video CODEC quality is very hard... by tepples · · Score: 1

      Develop a widget to plug in between an HDMI cable and your TV that adds random noise.

      I don't see how that would conform to the compliance and robustness requirements of HDCP. Nor do I see a market for HDCP-incompatible gear.

    6. Re:"comparing" video CODEC quality is very hard... by Anonymous Coward · · Score: 0

      You can't see because your view is impeded by a massive army of streamers with more money than perception.

      -AC.Falos

    7. Re:"comparing" video CODEC quality is very hard... by JaredOfEuropa · · Score: 1

      Monster probably beat you to it...

      --
      If construction was anything like programming, an incorrectly fitted lock would bring down the entire building...
    8. Re:"comparing" video CODEC quality is very hard... by tepples · · Score: 1

      You can't see because your view is impeded by a massive army of streamers

      If you mean people who play video games and stream them, streamers will themselves be impeded by the coming crackdown by video game publishers on streaming the publishers' copyrighted intellectual property. It's already started with Nintendo, Capcom, Sega, and Blizzard at various points.

    9. Re:"comparing" video CODEC quality is very hard... by evilviper · · Score: 1

      PSNR is nearly worthless

      Yes it is. A million ways to fool it. However, SSIM is getting widespread usage, and highly regarded among all of those who hate PSNR.

      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
    10. Re:"comparing" video CODEC quality is very hard... by omnichad · · Score: 1

      How does random noise violate those requirements? If you're charging enough for the device, you can protect the output stream and still get it certified.

    11. Re:"comparing" video CODEC quality is very hard... by tepples · · Score: 1

      In practice, the fixed costs of a company joining a particular DRM scheme raise "charging enough for the device" to such a level that production of a low-volume video processor intended to measurably degrade objective picture quality would likely be unprofitable.

    12. Re:"comparing" video CODEC quality is very hard... by omnichad · · Score: 1

      What on earth does that have to do with compliance and robustness? That's just unprofitable, not non-compliant.

  4. Re:Unbiased source? by Anonymous Coward · · Score: 0

    Except it's not a for-profit company so who exactly is gaining from this "huge financial stake"? You could just as easily argue they could fluff the results in favour of H.264 in order to strengthen their claim for more funding.

  5. Re:Unbiased source? by ledow · · Score: 4, Interesting

    Name another media company that went out of their way to develop a patent-free media codec that was independent and competitive with other codecs of the time? (Google Dirac)

    The BBC are publicly-funded, and under immense pressure to justify their funding at the moment - there's talk of scrapping the TV licence, and with it the BBC. They receive no advertising revenue in the UK at all. They only get some foreign revenue from sale of media (not even their own codecs or patents), and that goes to their commercial arm which isn't funding stuff like this.

    There's no profit in them evaluating codecs, only if they then go out and build their own hardware that uses it. They didn't manage to do that with Dirac either, so why they would with this I have no idea.

    All they want to know is what's best to push through iPlayer and store in their archive.

  6. Re:Unbiased source? by NatasRevol · · Score: 4, Insightful

    Not-for-profit does not mean not-with-costs.

    --
    There are two types of people in the world: Those who crave closure
  7. Beefy hardware required by Anonymous Coward · · Score: 0

    You need some serious hardware to play H.265 video without bringing your CPUs to their knees.

    1. Re:Beefy hardware required by viperidaenz · · Score: 0

      Or a GPU with h265 acceleration, which is getting quite common these days.
      My phone, released in 2014, has no trouble with 1080p H.265 HEVC. The Adreno 330 GPU does it all without the CPU breaking a sweat.

    2. Re:Beefy hardware required by wisnoskij · · Score: 1

      It plays fine on all tablets I have tried it on, and it plays on some of the little 40 dollar pcs they make now.

      --
      Troll is not a replacement for I disagree.
    3. Re:Beefy hardware required by PRMan · · Score: 1

      But not on any 2013 or earlier machine at all.

      --
      Peter predicted that you would "deliberately forget" creation 2000 years ago...
  8. vs H.264 yes by SirMasterboy · · Score: 5, Informative

    50% bitrate reduction vs H.264 sure, but not vs x264 which is the current gold standard for HQ video compression.

    It's like comparing a new audio codec to the original fraunhofer MP3 encoder. LAME on the other hand is a significantly better MP3 encoder like x264 is a better H.264 encoder.

    My own compression testing between HEVC and x264 show that at verty low bitrates, yes HEVC is better, but only at bitrates below what I would normally use and what I would consider "quality" encodes.

    When you compare say a 10GB x264 encode of a full-length BluRay film, even 8GB for the HEVC does not provide an equal or superior copy.

    1. Re:vs H.264 yes by Anonymous Coward · · Score: 0, Troll

      How is virginity?

    2. Re:vs H.264 yes by SuricouRaven · · Score: 1

      So if a crude HEVC encoder is equivalent to a very refined h264 encoder, what might a refined HEVC encoder be able to achieve given enough development?

    3. Re: vs H.264 yes by SirMasterboy · · Score: 1

      Absolutely.

      I have high hopes for the x265 project (development already underway) in the future.

    4. Re:vs H.264 yes by dinfinity · · Score: 2

      Additional info as to which encoders they used:
      "HEVC HM Reference Software Codebase, Version 12.1. [Online]. Available: http://hevc.hhi.fraunhofer.de/... "
      "AVC JM Reference Software Codebase, Version 18.5. [Online]. Available: http://iphome.hhi.de/suehring/... "

      Also, my experience with x265 encodes have been that (dark) low detail areas tend to look terrible, whereas everything else looks extremely good given the bitrate (be it high or low). I remember reading that this was a known (and non-trivial) issue in the x265 implementation at the time.

    5. Re:vs H.264 yes by Gaygirlie · · Score: 1

      50% bitrate reduction vs H.264 sure, but not vs x264 which is the current gold standard for HQ video compression.

      You are comparing apples and oranges. x264 is an encoder, H.264 is a codec. There is a x265 encoder for HEVC, just as there is x264 for H.264. The rest of your post is just rambling when you don't even understand the topic you are talking about.

    6. Re:vs H.264 yes by SirMasterboy · · Score: 1

      I was referring to an H.264 reference encoder...

      Also I mentioned x265 in another comment. At this point x265 is hardly better than an HEVC reference encoder. Something you would know if you actually knew what you were talking about and have actually used these encoders and done lots of testing and comparisons.

      How is describing my results from my own encoding comparisons rambling?

    7. Re:vs H.264 yes by Gaygirlie · · Score: 2

      You can't just compare a specific encoder against a video codec, such a comparison makes zero sense whatsoever. If you want to make a comparison then compare an encoder to an encoder or codec to a codec. There are already several HEVC-encoders out there, for example, both software-based and hardware-based, and it's ignorant to lump them all together.

    8. Re:vs H.264 yes by Anonymous Coward · · Score: 0

      Better for the species, ironically. Especially judging by this exchange.

    9. Re:vs H.264 yes by SirMasterboy · · Score: 1

      I think it's safe to assume that the article is talking about reference encoders. The HEVC consortium set out to reduce bit-rate by 50% at equal quality for the HEVC standard and for reference H.264 vs reference HEVC they came out pretty close to that goal.

      I was merely pointing out that if you instead compare a reference HEVC encoder or even the current "best" HEVC encoder compared to the best H.264 encoder (x264), the different in quality is negligible so far, especially for bitrates that actually yield a high quality encode (that isn't soft or smoothed out) like HEVC tends to do at lower bitrates.

    10. Re:vs H.264 yes by Goaway · · Score: 1

      I think it's safe to assume that the article is talking about reference encoders.

      Why would that be safe to assume? That is a useless comparison, and not one that would interest the BBC in the slightest.

      What is far more safe to assume is that it is a comparison between their current h.264 encoding setup vs. whatever h.265 coded they would use in practice. Neither would be the reference codec.

    11. Re:vs H.264 yes by SirMasterboy · · Score: 1

      What is far more safe to assume is that it is a comparison between their current h.264 encoding setup vs. whatever h.265 coded they would use in practice.

      I don't find that more safe to assume because if they were comparing any HEVC encoder to a non-reference H.264 encoder, i.e. a newer, higher quality H.264 encoder then their claims of 50% reduction in bitrate would not be possible.

      Nobody in the encoder community has posted any sorts of encoder results with such a reduction in bitrate. What has BBC done that is so incredibly special to achieve what nobody else has?

      I find it much more likely that they are comparing to a reference H.264 encoder as that would at least make their results possible, conformable, and repeatable in the first place.

      Also, any HEVC encoder implementation produces results so close to a reference encoder that you might as well consider them all reference at this point. I've tested several myself. But H.264 on the other hand, reference vs. the best is quite a large gap.

    12. Re:vs H.264 yes by Anonymous Coward · · Score: 0

      fade to blip

  9. Is it still patented? by Anonymous Coward · · Score: 0

    If so then we still can't use it.

  10. The study doesn't show that, really. by Anonymous Coward · · Score: 0

    The only conclusion that can be drawn from this study is that for encoding at fixed quantization, the JM v18.5 AVC reference encoder is objectively and subjectively worse than the HM v12.1 HEVC reference encoder.
    Raise your hand if you've ever used the reference encoder for either.

  11. Half the data is ten times as good by Anonymous Coward · · Score: 2, Funny

    That means it'll take half the time to bittorrent Doctor Who episodes. :-)

    1. Re:Half the data is ten times as good by Anonymous Coward · · Score: 0

      Ironically enough, I think the BBC would be totally fine with this since it saves them bandwidth.

    2. Re:Half the data is ten times as good by kamapuaa · · Score: 1

      I thought bittorrent was mostly used for Linux distributions?

      --
      Slashdot: providing anti-social weirdos a soapbox, since 1997.
    3. Re:Half the data is ten times as good by Anonymous Coward · · Score: 0

      I thought bittorrent traffic was mostly dwarfed by video streamers regardless?

      s/bittorrent/all

      Which actually brings us full circle, where shareholders oink eagerly at the thought of providing half the bitrate to users who can't* taste the difference.

      *at a statistically significant rate of financial detriment

  12. Re:Unbiased source? by AmiMoJo · · Score: 1

    The benefit for them is that they can reduce costs by reducing the bitrate, and claim not to have reduced picture quality. They have done it before - when HD broadcasts started they were around 18Mb/sec IIRC, but were later reduced to less than half that (average per channel, they actually balance about 18Mb/sec between two channels in a kind of VBR system). They claimed that the picture didn't suffer but it very clearly did, and it's now rather poor.

    They are under immense financial pressure, and reducing bitrate (and picture quality) allows them to save something else, someone else's job.

    --
    const int one = 65536; (Silvermoon, Texture.cs)
    SJW, n: "Someone I don't like, and by the way I'm a fuckwit" - AC
  13. Your So What moment by Curunir_wolf · · Score: 0, Flamebait

    So what? Who cares? It doesn't matter.

    H.265 is simply far too encumbered by "IP" costs and licensing restrictions to be of any use whatsoever. Sure, there are places (like the douchebags at BBC) who will decide to use it, but rational folks should run from it like the bubonic plague. Especially folks that create content. If you create something that uses H.265 as the master source, your copyright is worthless, because you content is now encumbered inside of format that requires you to pay fees if you want to extract it, convert it, distribute it, or even view it. "It can't really be that bad," you say. Sure, you can buy equipment and software that will do that for you, but part of your cost is the partial fee that the manufacturer is paying for licensing.

    Someone have a chat with the BBC about putting resources into VP9 instead. It will save them and everyone else a lot of money, pain, lawyer fees and headaches into the future.

    --
    "Somebody has to do something. It's just incredibly pathetic it has to be us."
    --- Jerry Garcia
    1. Re:Your So What moment by SuricouRaven · · Score: 1

      Pirates will be eager to adopt though. Patents are no issue for them, but bitrate is.

    2. Re:Your So What moment by Anonymous Coward · · Score: 0

      Yes, the old morbid joke, where paying customers suffer the strangleholds most, which barely affect pirates anyway.

      Yet... I'm accustomed to that only affecting commoners though, so I am experiencing weird feelings. It could be "Misery loves company" perhaps.

  14. Re:Unbiased source? by cheater512 · · Score: 1

    Erm you do realise that this isn't actually a quality reduction?

    If you read up on HEVC, you'll notice it's a completely separate codec to AVC that was designed specifically to hit 50% better (higher quality same bitrate or same quality at half bitrate). AVC was the benchmark codec that it was being compared to.
    So the BBC is just confirming that they hit that mark.
    https://en.wikipedia.org/wiki/...

  15. Re:Unbiased source? by Curunir_wolf · · Score: 1, Insightful

    Name another media company that went out of their way to develop a patent-free media codec that was independent and competitive with other codecs of the time? (Google Dirac)

    There is nothing royalty-free about HEVC.

    --
    "Somebody has to do something. It's just incredibly pathetic it has to be us."
    --- Jerry Garcia
  16. Re:Unbiased source? by Anonymous Coward · · Score: 0

    Your paranoia is showing. The BBC reported the real difference between these codecs, and your first thought is that they're biased. How can you engage with the world at all while this far gone?

  17. Re:Unbiased source? by wisnoskij · · Score: 1

    Umm, all the employees and in particular the leaders who draw multiple million dollar salaries?

    --
    Troll is not a replacement for I disagree.
  18. I have done my own comparisons by Sivar · · Score: 4, Interesting

    I have done my own comparisons of AVC (using x264, single-thread, veryslow preset) and HEVC (using x265, disabling wavefront processing because it slightly reduces quality, veryslow preset). All 1080p video, significant because HEVC is supposed to scale to 4K better than AVC.

    My conclusions:

    1) x265 takes FAR longer to encode, but we knew that. Understandable.
    2) When "low in bits", x265 blurs images rather than making them look blocky. This sometimes looks better but to me often looks worse.
    3) x265 seems to force a denoise filter. Video is far easier to encode efficiently when denoised, so I figure this is part of the data savings. It's a bit of a cheat, however, because I can get far smaller file sizes by running a denoise filter myself for x264-encoded video.

    I looked closely, for example, at Captain America the Blu-ray. Much of the detail of, e.g. car leather and grass and tree leaves is lost in an x265 encode, even at about the same overall data rate as x265/

    x265 supports "--tune grain", roughly analogous to "--tune film" for x264, but it makes the video vastly larger -- often larger than x264's version, and it often looks worse. It does a better job of keeping grain, however.

    My experience is very similar to many others' in forums. I had committed to switching my encoding to HEVC, but the results of my tests showed it is not ready for prime time. Some may not mind blurry ("soft" is probably a better word) video, or video that looks like it has been through a denoise filter, but I do.

    This is not to say that x265 is junk. I am sure it will mature over time just like x264 had to over time. x264 started out as being not all that much better than divx, the previous generation.

    --
    Computer Science is no more about computers than astronomy is about telescopes. --E. W. Dijkstra
    1. Re:I have done my own comparisons by Sivar · · Score: 1

      Forgot to add: I was using recent builds (about a month back) of x265.
      Whenever a comparison is made, the x265 folks always say that the latest versions are much improved over whatever was used in the comparison. They may be, but they still need some work based on my tests.

      --
      Computer Science is no more about computers than astronomy is about telescopes. --E. W. Dijkstra
    2. Re:I have done my own comparisons by Anonymous Coward · · Score: 0

      I assume you mean -tune grain in x264 as well for preserving grain?
      --tune film reduces grain unless the nonexistent documentation of x264 is wrong.

      grain: for grainy (or really foggy) source material where the grain should be kept and is not filtered out before encoding (see: https://en.wikipedia.org/wiki/Film_grain); the movie 300 is a good example of a grains source

      If you're using tune film to keep grain it might explain why it's not being kept very well in your encodes.

    3. Re:I have done my own comparisons by hairyfeet · · Score: 1

      Since you have been experimenting with this I have a question, what encoder do you use? Is there any encoders for H.265 that are user friendly, IE not just a CLI string o' doom?

      Because I have users that are converting all their DVDs/BDs to their media tanks (HTPCs are rather popular here) and if this new codec can cut a couple GB off per video? That adds up pretty quickly. But my users need simple and easy, plenty of those for H.264 but I haven't seen any yet for the new codec.

      --
      ACs don't waste your time replying, your posts are never seen by me.
    4. Re:I have done my own comparisons by wisnoskij · · Score: 1

      I don't understand how people produce decent encoding (using any format). But, they do exist. Download anything you like from a reputable pirate group, the x265 encoded videos simply come out significantly smaller with a similar quality. I do not pretend to be an videophile, but these groups are. And they use x265 and it comes out SIGNIFIGANTLY smaller than x264 every time.

      --
      Troll is not a replacement for I disagree.
    5. Re:I have done my own comparisons by Anonymous Coward · · Score: 2, Informative

      HandBrake has x265 built in.

      https://handbrake.fr/

      It has some quirks though. It's GUI based, but some of the defaults are plain stupid. Someone wanting "simple" is at risk of getting "inferior" instead.

      If you want to devote the time to learning the quirks, you can export a preset for your users once you've got the settings right.

      I made a simple preset to get you (and anyone else) started. MKV container, no cropping/resizing, no filters, default x265 settings (which you'll need to play with), untouched audio (passthru), no subtitles, no guarantees it'll even work.

      http://pastebin.com/61YyQNkv

      Download it and change the extension to .plist before importing from the Preset menu. Even though it says Apple in there, it was created on the Windows build.

      If a change you make undoes itself after the first encode, change it back, save the change as a new preset, load the new preset and see if your change stuck.

    6. Re:I have done my own comparisons by log0 · · Score: 1

      Just noticed hairyfeet's sig. Oh well.

      Decided to unmask myself because nobody will see it anyway.

    7. Re:I have done my own comparisons by DigiShaman · · Score: 1

      Don't forget the nightly builds too. https://handbrake.fr/nightly.p...

      --
      Life is not for the lazy.
    8. Re:I have done my own comparisons by BillKaos · · Score: 1

      I would be great if you could try with recent VP9, which is said to be close to x265.

    9. Re:I have done my own comparisons by Anonymous Coward · · Score: 0

      I got your back, was worth a +1

      (now anon because I modded :))

    10. Re:I have done my own comparisons by Bengie · · Score: 1

      2) When "low in bits", x265 blurs images rather than making them look blocky. This sometimes looks better but to me often looks worse.

      Blocking is because of a limited amount of information to display data. Blurring is about adding noise. Noise is annoying.

    11. Re:I have done my own comparisons by Sivar · · Score: 1

      I always use Staxrip
      https://github.com/stax76/stax...

      --
      Computer Science is no more about computers than astronomy is about telescopes. --E. W. Dijkstra
    12. Re:I have done my own comparisons by Sivar · · Score: 1

      This is because release groups are completely, utterly clueless about video. The file size is set ahead of time. Most groups set e.g. "8GB for 1080p movie", "4GB for a 720p movie" etc. in x264. Historically speaking, these pre-selected sizes were designed to fit on different media types, such as CD, single-layer DVD, dual-layer DVD.
      Few people use DVDs anymore, but most groups still make files far larger than they need to be.

      I rarely download pre-made videos because of this, so haven't downloaded any encoded in h.265, but I suspect they simply chose a smaller pre-set size.

      The correct, non-stupid thing to do is to set the quality and let the movie be however large it needs to be, usually under 4GB. This allows more easily encoded video, like CGI films (Toy Story, etc.) to be small while very difficult films (anything with a lot of noise and movement, like war films) are large but don't look terrible.

      --
      Computer Science is no more about computers than astronomy is about telescopes. --E. W. Dijkstra
    13. Re:I have done my own comparisons by wisnoskij · · Score: 1

      I have never seen a competent current group do that. They all encode based on quality, some full length movies come out 200M, others 900M+. Based on the content. They all come out looking good, and for 265, all come out significantly smaller than their 264 counterparts.
      I used to do a lot of 480, horrible quality, but the smallest file size you could find anywhere. Now groups using 265 come out with smaller files in 720. Crystal clear, amazing video, at less then the smallest worst quality used to provide.

      --
      Troll is not a replacement for I disagree.
  19. Sigh by Anonymous Coward · · Score: 0

    What would they know? If you spell BBC in Siryllic you get PRAVDA. Which means 'lying toady lapdogs'.

    No commercial pressure, no magic of the market, they just mak things up.

    P.S. Vote Trump
    --
    roman_mir

  20. Re:Unbiased source? by Darinbob · · Score: 1

    But if no quality reduction it is also a benefit to the user. Why stick to a patent encumbered standard when there's an alternative, just because someone is making money (which will happen with either standard)?

  21. Re:Unbiased source? by tlhIngan · · Score: 5, Informative

    The benefit for them is that they can reduce costs by reducing the bitrate, and claim not to have reduced picture quality. They have done it before - when HD broadcasts started they were around 18Mb/sec IIRC, but were later reduced to less than half that (average per channel, they actually balance about 18Mb/sec between two channels in a kind of VBR system). They claimed that the picture didn't suffer but it very clearly did, and it's now rather poor.

    They are under immense financial pressure, and reducing bitrate (and picture quality) allows them to save something else, someone else's job.

    The problem is, HEVC is expensive. While the MPEG-LA made h.264 the way it is by making streaming free (if the viewer doesn't pay) and offering caps to the maximum license fees, thereby encouraging big users (Cisco, Apple, Microsoft, Netflix, etc) to switch to h.264 and merely pay the cap every year

    Of course, MPEG-LA wanted to encourage the switch to HEVC by offering the same terms, and several patentholders balked which is why they pulled out of the MPEG-LA pool and created the HEVC Alliance which licenses without a cap, without free streaming (they want some money per HEVC stream), meaning the money you save in bandwidth might go straight to licensing fees.

    And I'm sure the BBC streams under h.264 were basically cost-free since the streams were available at no charge (granted, you paid with your TV license, but the MPEG-LA doesn't count that), so switching will create costs.

  22. Takes mucho effort by Anonymous Coward · · Score: 0

    Cannot be done in anything close to real-time, not with anything close to these results. The thing about this is, patent-holders are tired of having to "give h264 away for free" and are doing a GWX, and any cost. Suck. It. In. and Swallow.

    Notice how NO PLACE gets slashdotted anymore?

  23. Re:Unbiased source? by Anonymous Coward · · Score: 0

    Your paranoia is showing. The BBC reported the real difference between these codecs, and your first thought is that they're biased. How can you engage with the world at all while this far gone?

    s/BBC/Fox/g

    And your response would then be?

  24. The encoding community seems to disagree by AbRASiON · · Score: 2

    I've read many many posts indicating that for low bitrate stuff, 265 is doing very well but for the higher end stuff, it's only marginally better than 265 (more like 25%)
    That's an approximation, I don't recall the exact figure, but I do recall it being significantly less than 50%

    This is pretty disappointing, perhaps other tweaks and improvements will be eeked out over time, but as it stands, I can't see a 3TB movies folder being recompressed to 1.5TB with the same quality at this point in time.
    (I know that would be lossy to lossy and stupid, that's not the intention of the post)

    1. Re:The encoding community seems to disagree by AHuxley · · Score: 0

      It really depends what the end game is for the codec that has to be paid for or designed is.
      Addition of an extra channel in the space of one existing channel . Great for more branded content on existing bandwidth or spectrum.
      Two times the nation building UK content to limit the impact of foreign broadcasting having an impact on traditional UK news and documentaries.
      The role of video over IP considering the limitations of infrastructure going to most towns, cities, villages and its ability to support per device or room selected, streaming HD content. Many devices, screens now support on demand content and real bandwidth limits to that location is an issue.
      Getting more TV out to more people that they want anytime at the slow end of broadband would be useful.
      Limited national networking considerations vs paying a lot for an advanced codec.
      Create a codec in house and face the legal challenges of US codec standards expecting generational export dividends on their sale been rejected by unfair UK competition.
      Buy a US backed codec and have to pay per device, per seat, per user, as a nation... every year..all year.
      Thats UK funding wasted on an imported codec that could have gone to creative content on new channels via a free codec.
      Or the US gov demands the UK buy into its free market product under a trade deal clause. The codec owners rejoice and enjoy another revenue stream is secured for years.

      --
      Domestic spying is now "Benign Information Gathering"
  25. Re: Unbiased source? by Anonymous Coward · · Score: 1

    There seems to be this misconception that because the bbc is publicly funded it seeks to do everything "in the public interest " and generally doesn't behave like any other large corporation.

    The truth as I see it at least is that there are a lot of highly paid media types with one eye on their careers who justify every decision using exactly the same metrics as the rest of the industry. The bbc news website is turning into a clickbait riddled buzz feed clone exactly because they judge success in terms of uniques and audience retention as if they were selling ads. TV programs are similarly judged on audience share rather than quality. This led to a major climb down a few months ago when someone sufficiently senior pointed out that spending 10's of millions trying to compete directly with ITVs Saturday evening prime time offering was probably not an effective use of what is essentially public money.

    Similarly the website has come under fire for having a huge and poorly defined scope, along with costing a fortune to run. Being able to point at these figures and saying "but look what we saved on bandwidth!" Is either going to justify someone's continued employment or allow them to push through their 8k@120hz resume padding vanity project.

  26. Re:Unbiased source? by steveha · · Score: 4, Interesting

    Right. This is why I think VP9 actually could win and become the new standard (replacing H.264).

    H.265 and VP9 seem like they are definitely in the same ballpark on quality. And H.265 is heavily encumbered with patents; you have to pay royalties, and you never know what the royalties might cost in five years. VP9, on the other hand, is simply free: no royalties, no restrictions on what you may do with the video.

    Even if VP9 takes a lot more CPU time to encode, and even if H.265 is slightly better than VP9, not having to pay royalties (not even having to keep track of what you do with the video!) is such a huge benefit. It seems like a no-brainer.

    And Google will be making sure that all the Android phones at least will have good hardware support for VP9 decoding. VP8 never had a chance against H.264 because the hardware support wasn't there, and large companies were content to pay the capped fees as you noted.

    All that's left is possible legal FUD around VP9, but even that seems pretty cut-and-dried to me. MPEG-LA tried for something like a year to find patents to put into their patent pool to extract royalties from VP8, and in the end Google gave them a one-time payment of (to Google) a relatively small amount of money. Thanks to that one-time payment we know MPEG-LA won't ever come after anyone for using a VP8-derived codec, and I have no reason to think anyone would be able to prevail in court if they try it.

    Given all of the above, it seems to me that VP9 is the obvious choice for the new video standard, and I kind of wonder why anyone is still interested in using H.265 and paying the royalties.

    --
    lf(1): it's like ls(1) but sorts filenames by extension, tersely
  27. Subjective Tests by Anonymous Coward · · Score: 0

    Otherwise known as "complete bullshit."

  28. Re:Unbiased source? by Anonymous Coward · · Score: 0

    Name another media company that went out of their way to develop a patent-free media codec that was independent and competitive with other codecs of the time?

    All the companies involved with the Alliance for Open Media and NetVC.

  29. It's just middle-out. by jpellino · · Score: 2

    Lawyer up.

    --
    "Win treats sysadmins better than users. Mac treats users better than sysadmins. Linux treats everyone like sysadmins."
  30. Re:Unbiased source? by Anonymous Coward · · Score: 0

    You think they just get paid by what's left over from funding after expenses?

  31. Re:Unbiased source? by wisnoskij · · Score: 1

    Do you think that is how normal for profit enterprises work????

    --
    Troll is not a replacement for I disagree.
  32. You can't prove a negative by tepples · · Score: 2

    Because the set of subsisting patents is so large that you can't prove a negative. It costs a substantial chunk of change to deploy set-top decoder hardware for a new data format. Once hardware implementing a decoder for an allegedly royalty-free format has been shipped out, patent holders can come out of the woodwork and claim that their patents apply to the new format. With a patented format, on the other hand, it's more efficient for a patent holder to just join the existing patent pool.

  33. Re:Unbiased source? by WorBlux · · Score: 1

    There's also Daala in the pipline, which uses entirely new compression techniques that are not patent encumbered.

  34. Re: Unbiased source? by Anonymous Coward · · Score: 0

    "How can Fox engage the world when its that far gone?" :)

  35. Re:Unbiased source? by Anonymous Coward · · Score: 0

    The BBC are publicly-funded, and under immense pressure to justify their funding at the moment - there's talk of scrapping the TV licence, and with it the BBC.

    That's complete bollox, mate. It's been that way since the 1970s, and they only change is that they get more money to expand into areas they have no need to bother with. They have dozens of staff just responding to twitter for fuck's sake! Then there are the teams that reformat reddit fluff and red-top speculation and celebrity worship. This is the crap that needs cutting, and it needs cutting immediately.

    The next step will be to close the iplayer loop-hole and ensure those not paying the TV tax have to start paying.

    Like all large organisations, they do one thing, and that's expand. They are not a private business, they are not on the stock exchange and do not have a board and shareholder to respond to. It's about time they were pulled into line and all those filler jobs cut.

    Furthermore, their IT people are morons. Their content is delivered through flash, not open formats, and they force OS upgrades to continue to access programming we've paid for, just because they're a bunch of Apple zealots and want to force people to buy new fucking devices.

  36. Influence of software in the displays by marcolz · · Score: 1

    I don't see any mention of how motion compensation and other "smart" features of the display devices influenced the perceived quality. Software in these devices may work in both positive and negative ways.

    1. Re:Influence of software in the displays by wonkey_monkey · · Score: 1

      I don't see any mention of how motion compensation and other "smart" features of the display devices influenced the perceived quality.

      Probably because the BBC are smart enough to use professional monitors without any of that crap.

      And even if they did, as long as the settings are the same for both showings, it shouldn't be a big problem.

      --
      systemd is Roko's Basilisk.
    2. Re:Influence of software in the displays by marcolz · · Score: 1

      As listed in the test setup, they used TV sets (although really expensive ones) for the (U)HD setups. The Pioneer PDP-5000EX for instance has Pure Drive 2 software on it that I am not sure you can even disable. The software has MPEG noise reduction... It should at least be listed in the paper how to reproduce their setup, if they fiddled with the TV's settings.

  37. Re:Unbiased source? by Anonymous Coward · · Score: 0

    H.265 vs VP9 seems like BetaMax vs VHS. H.265 may be better but by being more expensive its adoption may well be lower which would give VP9 the clear shot at the title. Best doesn't always win.

  38. Re:Unbiased source? by Anonymous Coward · · Score: 0

    Yeah, I heard this same bullshit about Theora/VP8.

  39. Re:Unbiased source? by DigiShaman · · Score: 1

    Is there something intrinsic with all these codecs that Intel Quick Sync can do in hardware (CPU instruction set)? Or does the actual CODEC have to be baked in hardware?

    Wikipedia did mention something that I wasn't aware of, but makes sense in hindsight: "Quick Sync, like other hardware accelerated video encoding technologies, gives lower quality results than with CPU only encoders. Speed is prioritized over quality.[6]".

    I'm guessing people looking for the best quality won't be using Quick Sync after all, or rather haven't. This must be for the average person whom takes video with a cell phone, edits it on a computer, and posts to FB or YouTube.

    --
    Life is not for the lazy.
  40. Re:Unbiased source? by Anonymous Coward · · Score: 0

    He's not talking about HVEC, he's talking about something completely different but similar. Essentially saying they've lied in the past about the same topic and they cannot be trusted when talking about visual quality.

  41. Re:Unbiased source? by Big+Hairy+Ian · · Score: 1

    You are aware the current DG is a Director of HSBC, a Tory party doner and a personal friend of David Cameron. I don't trust the BBC to tell me the time anymore

    --

    Build a Man a Fire, and He'll Be Warm for a Day. Set a Man on Fire, and He'll Be Warm for the Rest of His Life.

  42. Re:Unbiased source? by omnichad · · Score: 1

    Switching from MPEG-2 to H.264 really is about a 50% savings. If your video looks bad at 18Mbps MPEG-2, you need better hardware. It won't look great, it's almost as much as the ATSC standard. It's not as bad as satellite TV that allocates less than 5Mbps H.264 to HD channels.

    None of it's anything compared to the 20Mbps+ H.264 used on Blu-Ray.

  43. Whatever by Anonymous Coward · · Score: 0

    I prefer to watch my videos on vinyl.

  44. Re:Unbiased source? by Crowd+Computing · · Score: 1

    All that's left is possible legal FUD around VP9, but even that seems pretty cut-and-dried to me. MPEG-LA tried for something like a year to find patents to put into their patent pool to extract royalties from VP8, and in the end Google gave them a one-time payment [osnews.com] of (to Google) a relatively small amount of money.

    If I recall correctly Google also held some important media-related patents from its Motorola purchase that allowed Google to just basically cross-license the H264 patents, the small fee being for the much greater number of patents held by the MPEG-LA. These patents are besides the cellphone-related patents that Google wasn't able to enforce because they fell into the FRAND category of essential industry patents.

  45. Re:Unbiased source? by Hognoxious · · Score: 1

    a Tory party doner

    It went to Eton and then it was eaten?

    --
    Confucius say, "Find worm in apple - bad. Find half a worm - worse."
  46. I wouldn't be surprised if it banned modification by tepples · · Score: 1

    I haven't read the HDCP agreement myself, but I wouldn't be surprised if it forbade modification of the video signal.

    Even if this is not forbidden, a DRM scheme operates on the principle that implementations are assumed noncompliant until proven compliant. The fixed costs of an equipment producer joining a DRM scheme include the cost of an audit (possibly probabilistic) of the compliance of the equipment producer's product on behalf of the scheme's maintainer. So even if it were compliant, whether a device is compliant or not does not matter if the prospective manufacturer cannot draw enough investors to make the device exist in the first place.

  47. Re:I wouldn't be surprised if it banned modificati by omnichad · · Score: 1

    I haven't read the HDCP agreement myself, but I wouldn't be surprised if it forbade modification of the video signal.

    You can definitely modify the video signal - http://support.xbox.com/en-US/...

    Looks like there are HDCP certification services that will test your device for under $5000 (Simplay Labs). I assume they would be liable if the device was actually non-compliant.

  48. Re: Unbiased source? by Anonymous Coward · · Score: 0

    Skewered

  49. Re: Unbiased source? by Tough+Love · · Score: 1

    The truth as I see it at least is that there are a lot of highly paid media types with one eye on their careers who justify every decision using exactly the same metrics as the rest of the industry.

    Two eyes.

    --
    When all you have is a hammer, every problem starts to look like a thumb.
  50. Re:Unbiased source? by Tough+Love · · Score: 1

    the money you save in bandwidth might go straight to licensing fees

    +1 Nailed it. And since bandwidth always increases while license fees usually do not decease, the deal gets worse the longer you play this game.

    --
    When all you have is a hammer, every problem starts to look like a thumb.
  51. Re:Unbiased source? by dave420 · · Score: 1

    What does that have to do with Dirac?

  52. Re:Unbiased source? by Anonymous Coward · · Score: 0

    I once wrote an H.261 video codec. Much more primitive than the current stuff but it gives me an idea.

    There is a lot you can do to accelerate a video coder without baking the whole thing into hardware. For decode, a fast Inverse Discrete Cosine Transform (IDCT) done by a DSP chip or whatever would really take a lot of load off the CPU. H.261 is mostly IDCT plus video "mixing" to paint new, decoded image pieces over old ones in the reference buffer, and filtering. I just looked at the Wikipedia page for H.265 and it seems that it also has additional filtering modes and can use Discrete Sine Transform (and I couldn't tell you why you would use both DCT and DST, sorry).

    You should be able to use the stream processors in a graphics accelerator to speed up decoding of any kind of video, even H.265. Per Wikipedia, H.265 was deliberately designed to be parallel decodable, so even just splitting the work to multiple processors of any kind should be a speedup.

    For a better answer than this one, ask someone who is more up to date than me. Sorry I can't give a better answer, but I waited a few days and nobody else stepped up.

    You could ask this question on StackOverflow and it seems like you could get a good answer there. It's not even opinion-based so it should still be permitted even though SO is really getting anal about which questions will be smacked down and closed.