TV Challenges

Topics to discuss:

  • Fragmentation across devices
  • Changes that are coming as more TVs? support HTML5?, Android TV, native apps on TV, etc.
  • Game consoles and fragmentation, release process (where gaming process gets applied to OTT apps)
  • Content protection, telemetry
  • Captions and pulling down TV issues
  • Open Screen Protocol - open protocol for discovery, connection, authentication under Presentation API, Remote Playback APIs?
  • Where are things going for app ecosystem on TVs?, how will HbbTV?/ATSC use HTML5?
  • How to bring TV experience to mobile devices & connected devices
  • Difficulties playing back on TVs? - EME/MSE are behind on TVs?, stability on TV ecosystem is a pain
  • Is there any standardization going on as XBox? and OTT devices become more popular, is there anything we can do
  • How are people using second screen?
  • Challenges in traditional broadcast TV workflows, how can web tools help?
  • How can the web community help prevent fragmentation?
  • CTA Wave: Goal is to make HTML5? the web standard on TVs?; broadcasters want HTML5? to be performant

CTA WAVE notes

  • There is a community interest in making HTML5? a strong TV standard in CTA-WAVE including test cases for implementation
  • HbbTV? 'companion device' demos at IBC included both sending a URL to the TV for playback, as well as sending media from the TV to the device
  • In Australian market HbbTV? has a lot of interest - used for FreeView?+ - but most of those experiences are sending a simple URL on the screen that you have to click through. Most in production HbbTV? applications drive a deeper web experience on the TV itself
  • Unclear whether there will be HbbTV? 3.0
  • ATSC rejected HbbTV? as the interaction layer and went with HTML5? instead = This is done with EME/MSE so it's device dependent; the TV is a type-1 player and you can't change certain things
  • Goals of CTA Wave (1) Prepare content for TVs? (2) What should TV manufacturer put in browser (3) What are media performance requirements (best practices) = Note: "browser" means the entire application layer for the TV
  • There is interest in CTA Wave to help drive W3C? standards for TV remote control - this is the Web & TV Interest Group (just put out a draft standard for this) = The Web Media API Community created a subset of standards for TVs? which include media APIs? and a subset of HTML5? standards for rendering = HbbTV? and ATSC are also participating in WAVE and there is a goal to harmonize the requirements between the standards
  • Is HDR being added? = CTA WAVE is looking at Media Capabilities API to help discovery of this capability on the TV, also looking at file format support
  • CTA WAVE is run under CTA which has an IPR declaration - they do specify MPEG containers (common file format is CMAF which is an MPEG container)
  • Non-goal: Make sure what works on the TV works on the desktop browser = e.g. Remote controls. Also IPR for TVs? is not the same as for the web.
  • CTA WAVE is inheriting the privacy and security that comes with W3C? standards as they are applied
  • What APIs? are included with CTA WAVE, Service Workers? IndexedDB?? (Will thinks yes, will follow up) = Note that tests for local storage consistency are key here = With 2017 version of standard, all four browsers need to be implementing in order to be included
  • Local storage on TV platforms - access is minimal to local storage - also testing
  • What is lag time between spec and TVs?? (2017 spec will likely hit 2019 TVs?; working on a 1-year gap over time)
  • There is no CTA Wave logo program (but some companies are interested in supporting this)
  • Updates? CTA Wave is pitching ability to update browser independent of firmware updates. This is still under discussion, only online updates (not OTA)
  • Wave looks at HLS and DASH equally; tests are done against media segments (not a particular playlist/manifest). Does not expect native support in TVs? (but not prohibiting it either).
  • Content spec is different than HTML5? spec. Content spec allows a Type-1 implementation (ie: Apple will natively support HLS and not use MSE to do it)
  • Note: CTA WAVE is not only focused on TVs?, also consumer electronics (set top boxes, watches, etc.)

What does the future look like?

  • Broadcaster: Don't really now. Right now trying to get users from broadcast streams into more OTT experiences = e.g. catch-up services popping up on-screen 1-hour before new episode
  • Longer term: Looking at interactive experiences, how to add additional content (e.g. Big Brother is on the air, 24/7 air online would be available as well)
  • In some cases these multi-screen experiences are budgeted as a subset of digital (at least in the US)
  • But in some markets (e.g. UK) - BT Sport is a good example of a media company that carved out top-level budget for EUFA finals to do multi-screen experiences
  • To bring a new streaming service on a TV is a pain, then the UX is not great
  • Will Roku, Chromecast, etc. be aggregators of streaming services?
  • OTT + Broadcast is going up (cord cutting) -- YT TV, Hulu TV are offering TV equivalency with DVR options

Open Screen Protocol

  • Aiming to have a open source standard underneath Presentation and Remote Playback APIs? for discovery, authentication, connection
  • VLC has integrated with MDNS
  • There are open source libraries for managing different connection types (Cast, etc.)
  • CBS interested in ability to track beaconing

How can W3C? APIs? help TV workflows?

  • Connection API (e.g. OSP) can help, CTA WAVE can help

Game Consoles

  • XBox1? Universal Windows - there are different ways to ship to these
  • The old systems are harder to deal with - Wii U, old PlayStations? are phasing out w/ users
  • Some old encoding profiles for Xbox 360 don't work (end up limiting to 720p; old media specs don't work)
  • Publishers moving to only support newer systems
  • Game consoles don't have the same HW contraints as TVs?

Other notes

  • TV updates are in the low %s - most TVs? are not connected to the Internet