W3C home > Mailing lists > Public > public-web-and-tv@w3.org > April 2020

Re: [media-and-entertainment] Use case description: responsive grafics synced with video (#35)

From: Ingar Arntzen via GitHub <sysbot+gh@w3.org>
Date: Tue, 21 Apr 2020 07:34:39 +0000
To: public-web-and-tv@w3.org
Message-ID: <issue_comment.created-617007780-1587454478-sysbot+gh@w3.org>

> Thank's a lot for this info. It seems the main purpose of this framework is to provide synchronization between different devices, based on a worldclock, correct? That would of course work locally as well, I'll take a closer look at it.

@pthopesch  Not exactly right - but close :).

The main purpose is to provide a local media clock/controls for the Web (a.k.a timingobject) that is an *independent* mediator between timed things, and designed for precise synchronization. 

The html5 media clock/controls which is typically used for this fails on both these accounts. 

Once you have a timingobject as shared concept for media clock/controls, you can have different timed things be precisely synchronized simply by connecting them to the same timingobject. Real easy.

The inter-device sync is merely a secondary benefit (yet substantial!), as the timing object can additionally mediate between timed things on other web pages and/or other devices.

Note: this approach works well if you have time data delivered out-of-band. If data is delivered in-band, I'm not sure if you can escape the datacue/texttrack system, and you are effectively stuck with the video as your media clock. This is yet another reason to avoid in-band transfer of timed data, in my opinion.  


GitHub Notification of comment by ingararntzen
Please view or discuss this issue at https://github.com/w3c/media-and-entertainment/issues/35#issuecomment-617007780 using your GitHub account
Received on Tuesday, 21 April 2020 07:34:41 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 21 April 2020 07:34:41 UTC