Re: [me-media-timed-events] Document timing requirements for different use cases

Some discussion in https://www.w3.org/2018/02/01-me-minutes.html:

> **Igarashi**: In terms of frame-accurate eventing, as Francois said I don't see any specific requirement. Ad insertion won't be achieved at the app level, it's more at the system or rendering level.
> ... Some broadcasters maybe want to synchronise web content with the media, e.g., information about a soccer player during a game.
> ... I see these as rarer applications. Accuracy to only about 100 ms is needed, not frame accuracy, for broadcast systems.
> **Giri**: The W3C specs don't guarantee 100 ms accuracy, something that HbbTV complained about.
> ... There are other issues than UA latency that result in missing cues. Hence the MPEG work, which should take some of the uncertainty out of processig the events.
> ... Frame accuracy isn't critical, but 500 ms isn't good either.
> **Igarashi**: I think 300 ms is enough in most cases.

-- 
GitHub Notification of comment by chrisn
Please view or discuss this issue at https://github.com/w3c/me-media-timed-events/issues/22#issuecomment-439459112 using your GitHub account

Received on Friday, 16 November 2018 17:02:47 UTC