Resultados 1 a 5 de 5
  1. #1
    WHT-BR Top Member
    Data de Ingresso
    Dec 2010
    Posts
    17,200

    [EN] Third HEVC Patent Pool Launches With Ericsson, Panasonic, Qualcomm, Sharp & Sony

    Dan Rayburn
    May 30, 2017

    For content owners and broadcasters looking to adopt HEVC, two patent pools offered by MPEG LA and HEVC Advance have been offering licensing terms around HEVC patents for some time. But if dealing with two pools wasn’t already confusing enough, we now have a third pool that has entered the market. Launched in April, Velos Media has launched a new licensing platform that includes patents from Ericsson, Panasonic, Qualcomm Incorporated, Sharp and Sony.

    As all these patents pool claim, Velos Media says they are making it “easy and efficient” to license from the “innovators that have made many of the most important contributions to the HEVC standard.” Of course, they also say that their pool “reduces transaction costs and time to market”, that their terms are “reasonable”, with “rates that will encourage further adoption of the technology.” For a pool that tries to sound professional, their website is a joke. It contains no real details of any kind, such as which patents are covered in the pool, by which companies. Nor does it give any details on what the licensing terms are or whom exactly they cover.

    In their press release they make a mention of “device manufacturers” but give no other context of whom they are targeting. To make matters more confusing, Velos Media is being run by the Marconi Group, “an entity formed to create, launch and support new patent licensing platforms.” It’s clear Velos Media has no understanding of the market, doesn’t know the use cases and doesn’t realize the important of transparency when it comes to patent pools.

    http://blog.streamingmedia.com/2017/...tent-pool.html

  2. #2
    WHT-BR Top Member
    Data de Ingresso
    Dec 2010
    Posts
    17,200

    Why Apple’s HEVC Announcement Is A Big Step Forward For The Streaming Media Industry

    It seems HEVC has been prioritized by the industry as the next generation codec of choice

    Dan Rayburn
    June 8, 2017

    The battle for bandwidth is nothing new. As CE manufacturers push the bounds on display technologies, and with 360 and VR production companies demonstrating ever more creative content, the capacity of networks will be taxed to levels much greater than we see today. For this reason, the Apple announcement at their 2017 Worldwide Developers Conference that they are supporting HEVC in High Sierra (macOS) and iOS 11 is going to be a big deal for the streaming media industry. There is little doubt that we are going to need that big bandwidth reduction that HEVC can deliver.

    While HEVC has already been established on some level since Netflix, VUDU, Fandango Now, and Amazon Instant Video have been distributing HEVC encoded content, that’s all been to non-mobile devices to date. But what about the second screen, where more than 50% of viewing time is occurring? With this announcement, Apple set the de-facto standard for the premium codec on second screen devices. We know that H.264 is supported fully across the mobile device ecosystem and any codec, which is going to replace it must have a realistic path to being ubiquitous across devices and operating systems. That’s why the argument from some that VP9 will win on mobile, never made sense, as I don’t see any scenario where Apple would adopt a Google video codec. But prior to Monday morning June 5th, 2017, and the WWDC2017 HEVC announcement, no one could say for certain that this wouldn’t happen.

    We’ll likely never know what the considerations were for Apple to select HEVC over VP9. With VP9 supported only on Android devices while HEVC is supported on Apple as well as certain Android devices such as the Samsung Galaxy S8 and Galaxy Tab, streaming services now face a conundrum. Do they encode their entire library twice (HEVC and VP9) or only once (HEVC) to cover iOS devices and connected TVs? The decision is an obvious one. HEVC should receive the priority over VP9 as most services have too much content to maintain three libraries (H.264, HEVC, VP9). When you consider that HEVC decoding is available in software and hardware for Android, the choice to deploy HEVC as the next generation codec beyond H.264 seems an obvious one.

    With Beamr and other HEVC vendors supporting OTT streaming services in production since 2014, we are well down the road with a proven technology in HEVC. And as we heard from Joe Inzerillo, CTO of BAMTech during his keynote talk at Streaming Media East show, serious companies should not be wasting time with “free” technology that ultimately is unproven legally. Though Joe may have been thinking of VP9 when he made this statement, it could have also been referring to the Alliance for Open Media codec AV1 which has been receiving some press of late mainly for being “free.” My issue with AV1 is that the spec is not finalized so early proof of concepts can be nothing more than just that, proof of concepts that may never see production for at least 18-24 months if not longer. Then there is the issue of playback support for AV1 where to put it simply, there is none.

    What Apple delivers to the industry with adoption of HEVC is 1 billion active iOS devices across the globe, where consumer demand for video has never been higher. Until today, OTT services have been limited by only having access to an H.264 codec across the massive Apple device ecosystem. I predict that the first “user” of the HEVC capability will be Apple themselves, as they will likely re-encode their entire library including SD and HD videos to take advantage of the 40% bitrate reduction that HEVC can deliver over H.264, as Apple has claimed. Streaming services with apps in the app store, or those who deliver content for playback on iOS devices will need to be mindful that the consumer will be able to see the improved UX and bandwidth savings from iTunes, along with higher quality.

    I reached out to Beamr to get their take on the Apple HEVC news and Mark Donnigan, VP of marketing make three good point to me. The first point is that higher quality at lower bitrates will be a basic requirement to compete successfully in the OTT market. As Mark commented, “Beamr’s rationale for making this claim is that consumers are growing to expect ever higher quality video and entertainment services. Thus the service that can deliver the best quality with the least amount of bits (lowest bandwidth) is going to be noticed and in time preferred by consumers.” Beamr has been hitting their speed claim hard saying that they can deliver an 80% speed boost with Beamr 5 compared to x265, which removes the technical overhead of HEVC.

    Mark also suggested that, “there is no time to wait for integrating HEVC encoding into content owners video workflow. Though every vendor will make the time is of the essence claim, in this case, it’s possible that they aren’t stretching things. With iOS 11 and High Sierra public betas rolling out to developers in June, and to users this fall, video distributors who have not yet commissioned an HEVC encoding workflow don’t have a good reason to still be waiting.” It’s well known that outside of Netflix, VUDU, Amazon Instant Video and a small number of niche content distributors, HEVC is not in wide use today. However, active testing and evaluation of HEVC has been going on for several years now. Which means it’s possible that there are services closer to going live than some realize.

    Finally, Mark also correctly pointed out that Apple is clearly planning to support HDR with displays and content. With the announcement that the new iMac’s will sport a 500 nit display, 10-bit graphics support (needed for HDR) and will be powered by the 7th generation Intel Kaby Lake processor with Iris Pro GPU, Apple is raising the bar on consumer experience. Not every home may have an HDR capable TV, but with Apple pushing their display and device capabilities ever higher, consumers will grow to expect HDR content even on their iOS devices. Soon it will not be sufficient to treat the mobile device as a second class playback screen. As Mark told me, “Services who do not adopt HDR encoding capabilities (and HEVC is the mandatory codec for the HDR10 standard), will find their position in the market difficult to maintain.” Studies continue to show that higher resolution is difficult for consumers to see, but HDR can be appreciated by everyone regardless of screen size.

    Apple drives many trends in our industry, and history has shown that those who ignore them do so at their peril. Whether you operate a high-end service that differentiates based on video quality and user experience, or you operate a volume based service where delivery cost is a key factor, HEVC is here. With HEVC as the preferred codec supported by the TV manufactures, and adopted by some Android devices, and with Apple bringing on board up to 1 billion HEVC capable devices, it seems HEVC has been prioritized by the industry as the next generation codec of choice.

    http://blog.streamingmedia.com/2017/...a-bigdeal.html

    Na minha insignificante experiência, HEVC faz uso brutal de CPU em aplicativos como VLC, inviabilizando o uso em processadores lentium.

  3. #3
    WHT-BR Top Member
    Data de Ingresso
    Dec 2010
    Posts
    17,200

    off-topic: iOS 11 Will Bring More Privacy to Users

    William White
    Jun 8, 2017

    Apple is making changes in iOS 11 that will let users have more privacy from their apps, reports BGR. This change will make it so that all apps in iOS 11 will have a “While Using the App” option for location tracking. This stops apps from constantly tracking where a person is, even when not in use. Uber is one of the more popular apps that continues to track its users even when it isn’t in use, but this change will put a stop to that.

    http://investorplace.com/2017/06/app...-privacy-aapl/

  4. #4
    WHT-BR Top Member
    Data de Ingresso
    Dec 2010
    Posts
    17,200

    Apple Embraces HEVC: What Does it Mean for Encoding?

    At its Worldwide Developer Conference this week, Apple announced it would support HEVC/H.265 in High Sierra and iOS 11 in a combination of hardware and software decoding, depending on the device. Here are the details of how Apple will implement it.

    Jan Ozer
    June 8, 2017

    From a codec perspective, the key announcement at Apple's Worldwide Developer Conference (WWDC) 2017 was the inclusion of HEVC into HTTP Live Streaming (HLS). Streaming Media's Dan Rayburn covered the significance of that announcement to the market as a whole in his article, "Why Apple's HEVC Announcement Is A Big Step Forward For The Streaming Media Industry." You can tell from the title that Rayburn thinks it's a big deal, and I agree. In this article, I'll focus on exactly what Apple announced regarding HEVC and its implications from a technical perspective. I'll also discuss the new subtitle format supported in HLS, and a new image format that Apple launched.

    HEVC Support in High Sierra (macOS) and iOS 11

    I gathered much of the information presented below from WWDC Session 504, "Advances in HTTP Live Streaming," by Roger Pantos, the original author of the HLS specification, and Anil Katti, both AV Foundation engineers.

    Here's what I learned. First, Apple will support HEVC in High Sierra, the next MacOS, and iOS 11, and both will be available as free upgrades this fall. Figure 1 identifies all devices that will be compatible with iOS 11.


    Figure 1. iOS devices compatible with iOS 11

    As shown in Figure 2, Apple will support HEVC via a combination of hardware and software decoding, and you should expect software decoding to consume more power and shorten battery life. For example, tests on a Dell notebook performed by TechSpot found a 39% drop in battery life when playing HEVC without hardware support as compared to H.264 with hardware support. Until proven otherwise, I would expect similar decreases in battery life with Apple mobile devices and notebooks using software-only HEVC decode. On a positive note, on devices with HEVC and H.264 hardware support, the TechSpot article found very little difference in battery life when playing the two formats.


    Figure 2. Hardware vs. software support for HEVC in iOS 11 and MacOS

    Which devices does this impact? Looking at iPhones only, according to Wikipedia, the iPhone 5s uses the A7 CPU, the iPhone 6 and 6 Plus use the A8 CPU, so playback will be in software. The iPhone 6S models use the A9 CPU, while the iPhone 7 uses the A10 Fusion, which presumably will also include HEVC hardware-based decode. So, sending HEVC streams to the iPhone 5s, iPhone 6, and iPhone 6 Plus will likely significantly reduce their battery life; for newer devices, HEVC should have minimal effect.

    Though not listed on the slide, at 4:15 in the presentation, Pantos states that the Apple TV will also receive a software update that enables HEVC playback, which you can confirm at Apple's tvOS Guide.

    A different presentation, Session 515, the "HLS Authoring Update," noted that all software and hardware decoders support up to Main 10 Profile, Level 5.0, and the High Tier. This presentation also discusses many additional changes to the HLS specification and associated tools, and is worthwhile for anyone creating HLS content. Yet another presentation, "Introducing HEIF and HEVC" (Session 503), presented by Gavin Thomson and Athar Shah, details that beyond HLS, Apple's HEVC decoders can play HEVC encoded video in either a QuickTime or MP4 wrapper.

    Other HEVC Implementation Details

    Figure 3 covers several additional implementation details. First, and most important, HEVC must be packaged in the fragmented MP4 format Apple adopted when it added support in HLS for the Common Media Application Format (CMAF) at last year's WWDC. Second, Apple will continue to use CBC (cipher block chaining) encryption, which has been adopted by Google in Widevine, but not (so far) by Microsoft in PlayReady. So, while you can reuse your encoded fMP4 fragments for DASH and HLS, you'll still need two delivery payloads for encrypted content—one for CBC, and the other for Counter Mode (CTR) used in PlayReady.


    Figure 3. Other implementation details

    The rest of the slide deals with notification requirements for HEVC encoded content in the HLS manifest files, which is straightforward.

    Mixing HEVC and H.264 in a Master Playlist

    Figure 4 details how to combine HEVC and H.264 in a single HLS presentation defined by a master playlist files. As you can see, you can mix the two codecs in a single playlist just as you could include video encoded using different H.264 profiles. The key requirement is that you designate the codec as discussed above (and as you had to do when mixing H.264 profiles).

    Essentially, this means that the player will have to seamlessly switch from playing H.264 encoded video to HEVC encoded video; it will be interesting to see how smoothly this works, particularly on devices and computers using software decode.


    Figure 4. Mixing HEVC and H.264 in a Master Playlist

    Note that unlike HEVC, which must be fMP4, H.264 HLS content can be formatted as either fragmented MP4 files or MPEG-2 transport streams. This means that you don't have to transmux your streams to mix them with HEVC, a nice convenience factor. The last line details that Apple updated their HLS Authoring Guidelines for HEVC (the official document is called the HLS Authoring Specification for Apple Devices). Let's see what the updated guidelines look like.

    (continua)

  5. #5
    WHT-BR Top Member
    Data de Ingresso
    Dec 2010
    Posts
    17,200
    40 Percent? Who Said 40 Percent?

    Figure 5 shows the new encoding ladder, and it's interesting that the highest bitrate saving is 29% and never gets to the 40% number that Apple bounced around in multiple sessions. It's also interesting that Apple hasn't yet extended its guidelines beyond 1080p, despite the iPhone 7 and many other devices supporting 4K playback.


    Figure 5. The updated encoding ladder from the Apple HLS Authoring Specification

    No matter. You should be able to achieve 35-50% savings at 1080p resolution, and 30-40% savings at 720p. Beyond those resolutions, H.264 has never really been a good option, so comparisons are not useful.

    What About Subtitles?

    Apple also debuted support for IMSC1, which is a WC3 recommendation for TTML captions that are optimized for streaming delivery, and is the baseline subtitle format for CMAF. It's also mandatory for the Interoperable Master Format specification to which content publishers like Netflix are committed.

    According to the Apple documentation, the IMSC1 captions are carried as XML text inside fMP4 segments, and identified in the Master Playlist file. Note that IMSC1 captures are in addition to the WebVTT captions already supported by HLS, not instead of.

    What the Heck is HEIF?

    In the aforementioned presentation entitled "Introducing HEIF and HEVC," Apple also debuted an image format called the High Efficiency Image File Format, or HEIF, which is an image standard developed by the Moving Picture Experts Group (MPEG) for storage and sharing of images and image sequences. As you can see in the Figure 6, the HEIF format as used by Apple uses HEVC compression, which the presenters state provides up to 2X better compression than JPEG.


    Figure 6. Details about the new HEIF format

    Support for HEIF image decode looks a lot like HEVC decode; that is, in hardware for devices with the A9 chip and (presumably) higher, and software for all others. This raises two concerns. First, that HEIF decoders will be subject to royalties, though presumably, Apple has taken care of that for its own updates. Second, that HEIF images will be a proprietary format that you can't easily share or utilize. It may be that you'll first have to decode the image into JPEG with an Apple supplied or other decoder to use it outside the Apple ecosystem.

    About those Royalties

    According to multiple reports, Apple currently has about $250 billion in cash, so certainly it can afford any royalties associated with HEVC. Interestingly, Apple is listed as a licensee (and licensor) of the MPEG LA pool, but not as a licensee in the HEVC Advance pool. I checked with HEVC Advance, which confirmed that Apple was not currently a licensee, though they expect this to change when Apple actually issues the updates. The newest pool, from Velos Media, hasn't yet set terms.

    What am I Hearing from the Industry?

    As you would expect, the industry is very positive about the Apple move. Bitmovin already supports HEVC in HLS, and JW Player plans to once the updates are available and demand for the format begins.

    The one publisher I spoke with expressed concern about the costs of adding a completely new set of encodes to its CDN footprint, and shared it they probably would wait until iOS devices with hardware decode comprised a high percentage of all supported iOS devices.

    Related Articles


    While the x265 codec is making big strides in quality and file size, the major browsers are in no rush to support H.265. With interest in 4K growing, maybe it's up to Flash to save the day.

    Should you be delivering HEVC? It depends on what you're delivering and who you're trying to reach. Frost & Sullivan analyst Avni Rambhia breaks down the key issues of sticking with AVC vs. migrating to HEVC in this clip from Streaming Media East 2016.

    Speedy adoption of HEVC has been delayed by squabbles over licensing. Here, the developers of x265 propose steps to end the gridlock and move forward.

    Frost & Sullivan analyst Avni Rambhia explores the "three 'Rs'" of HEVC adoption: Revenue, Resolution, and thRoughput.

    Frost & Sullivan analyst Avni Rambhia identifies the key inhibiting factors that are impeding the widespread migration from AVC to HEVC.

    Frost & Sullivan analyst Avni Rambhia assesses the key factors content owners face today in determining whether to stick with AVC or move to HEVC.


    http://www.streamingmedia.com/Articl...ng-118735.aspx

Permissões de Postagem

  • Você não pode iniciar novos tópicos
  • Você não pode enviar respostas
  • Você não pode enviar anexos
  • Você não pode editar suas mensagens
  •