Google’s contradictions are killing CMAF and screwing everyone , including its own users

Spread the love
  • 9
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •  

Spread the love9        Or why you won’t get 4K quality on Netflix content using Chrome anytime soon. I’ve tracked CMAF development before [1], and how the whole industry went through so much effort into creating a common format which would be compatible with every single device out there. Yes, manifests would be different between HLS and DASH, but the underlying streamed content would be shared between all devices. In order for people to understand how we got that far, we need to understand that it took Microsoft’s willingness to allow applications and devices using Playready 3 or below to become incompatible with content encrypted …

Codec wars – Apple drops the hammer on VP9, chooses H.265 and takes a decision for the industry

Spread the love
  • 94
  •  
  •  
  •  
  •  
  • 1
  •  
  • 4
  •  

Spread the love94    1 4 It seems funny, but this year’s Apple’s WWDC was one of the most import yet, but not due to something said during the 2017’s Keynote. Instead, this low profile presentation will have far reaching implications over the next 8 to 10 years on the video delivery industry, from Google to Netflix. As Apple decided to use H.265 and WebVTT, the whole industry will be forced to follow suit. The story started back in May 2010 when Google acquired On2 technologies, and specifically all the related IP to the VP8 video codec. Google was not happy with having to …