W3C home > Mailing lists > Public > public-web-and-tv@w3.org > August 2011

Re: [HOME_NETWORK_TF] Extending ISSUE-22 (LipSyncTimeSynchronisation) to video content

From: Matt Hammond <matt.hammond@rd.bbc.co.uk>
Date: Mon, 15 Aug 2011 14:00:06 +0100
To: "Giuseppe Pascale" <giuseppep@opera.com>
Cc: "public-web-and-tv@w3.org" <public-web-and-tv@w3.org>
Message-ID: <op.vz9aegmtmko9fo@r44116>
Hi Giuseppe, I have been thinking along similar lines.

Your wording suggestion seems very sensible. I have also forwarded some  
suggestions for requirements for this issue to the list that make a  
similar attempt - although the email does not seem to have come through  
yet. Having just checked, perhaps this is because my email was sent from a  
slightly different email address? I will resend.

It is important to ensure that the requirements still capture the ability  
to provide more general synchronisation for non AV content (e.g. the  
HTML/JS driven slideshow example described in the scenario) ... but I  
believe that will still be captured by requiremnts derived from ISSUE-21  
(less precise time synchronisation).



On Mon, 15 Aug 2011 13:52:45 +0100, Giuseppe Pascale <giuseppep@opera.com>  

> Matt, all,
> while compiling the list of requirement for the Use cases approved so  
> far (that I hope to finish by today so people can take a look and  
> comment on it), I was thinking if we should extend ISSUE-22 to actually  
> cover sync of both audio and video. The use case could be to have an  
> additional video synchronized with the main video (for example a video  
> with sign language synchronized with a newscast). The requirement could  
> be something like
> "User agents should provide a means for application to playback  
> additional audio/video tracks that are precisely synchronized with  
> content being played on a home network content player."
> Thoughts?
> /g

| Matt Hammond
| Research Engineer, BBC R&D, Centre House, London
| http://www.bbc.co.uk/rd/
Received on Monday, 15 August 2011 13:00:54 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:57:07 UTC