04:33:29 <RRSAgent> RRSAgent has joined #sync
04:33:29 <RRSAgent> logging to http://www.w3.org/2015/10/28-sync-irc
04:33:33 <skim13> skim13 has joined #sync
04:33:39 <tidoust> RRSAgent, make logs public
04:33:39 <ats> ats has joined #sync
04:33:50 <tidoust> Meeting: Cross-device synchronization TPAC 2015 breakout
04:33:54 <tidoust> Chair: Francois
04:34:00 <nsakai> nsakai has joined #sync
04:34:01 <tidoust> RRSAgent, draft minutes
04:34:01 <RRSAgent> I have made the request to generate http://www.w3.org/2015/10/28-sync-minutes.html tidoust
04:34:29 <mkaki> mkaki has joined #sync
04:34:38 <mdadas> mdadas has joined #sync
04:35:31 <katsu> katsu has joined #sync
04:36:48 <akitsugu> akitsugu has joined #sync
04:37:05 <rus> rus has joined #sync
04:37:37 <satoshin> satoshin has joined #sync
04:37:59 <Dewa> Dewa has joined #sync
04:38:29 <padenot> padenot has joined #sync
04:38:35 <dom> dom has joined #sync
04:38:59 <mdadas> tidoust : François daoust W3C staff
04:39:05 <Roy> Roy has joined #sync
04:39:37 <mdadas> discussion about multi-device synchrionisation
04:39:47 <cpn> cpn has joined #sync
04:39:49 <mdadas> starting by a short presnetation and a demo
04:40:00 <mdadas> and then opening the floor for discussion
04:40:16 <mdadas> the work started in Multi-Device Timinig CG
04:40:41 <YusukeN> YusukeN has joined #sync
04:40:54 <nori> nori has joined #sync
04:41:48 <mdadas> UCs: shareed viewing, related companion cintent, Lip-sync, clean audio sound track, video wall, digital sgnage, silent dsco, ...
04:42:32 <mdadas> there more UCs as the cross device synchronisation can be applyeid more widely than to media context only
04:44:04 <mdadas> some orders of magnitude for synch are given to explain the different situations
04:44:34 <mdadas> for the synch, there is a need for a clock
04:45:11 <mdadas> a clock must be selected and other clocks refer to it
04:45:50 <mdadas> the clock synch can be don ein JS (but native support coud be better)
04:46:36 <dom> s/ ein/e in/
04:47:13 <mdadas> second thing needed is to share the timeline (distributed by the app) and to share updates to the reference timeline
04:47:33 <mdadas> this also can be achieved in JS
04:48:40 <mdadas> third thing needed is a way to inform the UA to use the reference timeline and to follow the same clock
04:49:10 <mdadas> mathieu hoffman: there is also an issue with the latency
04:49:26 <shinya> shinya has joined #sync
04:50:01 <mdadas> it is done by compensation of the estimated latency
04:51:19 <mdadas> rus: there is no need to synchronize all the media at the same time
04:52:57 <mdadas> sychronized media playback can also be achieved in JS
04:53:34 <mdadas> using skips and adjustemnets of playbackrate
04:54:30 <mdadas> rus: in MSE, there is a discussion on insertion of alternative content which has close concerns
04:55:42 <mdadas> the timing notion is needed in different works : MSE, web audio, ... hence it is important to have a common understanding of it
04:55:53 <mdadas> <DEMO>
04:56:31 <mdadas> see : http://kwz.me/MW
05:05:18 <mfoltzgoogle> mfoltzgoogle has joined #sync
05:05:49 <mdadas> the idea in this spec is to define the timing as a web resource
05:06:13 <mdadas> the timeline is defined as a time state vector
05:07:25 <mdadas> next is to define the timing provider object
05:07:58 <padenot> b 4
05:09:57 <mdadas> the timing provider does not achieve the sychro but only computes the skew
05:10:31 <mdadas> s/ skew/  clock skew
05:14:59 <mdadas> the timing object is defined
05:15:09 <Sangjo> Sangjo has joined #sync
05:15:33 <mdadas>  the timing oject is to be managed by a media element extension
05:16:48 <mdadas> this is different from a media controller as to allow to deal with the media object in a more flexible manner
05:18:27 <mdadas> the timed data is to allow the timed text independantly from the media element
05:19:11 <mdadas> teh question is if this is doable?
05:20:03 <mdadas> from discussion it seems that  it is complicated fro mthe spec persepective and it is even worst from impelemntation perspective
05:21:12 <mdadas> work on the same topic exists in other orgs (DVB, IEEE, IETF, MPEG, ....)
05:22:12 <mdadas> Roy Kawada: in digital signage, there is a need of synchronized screen (Tokyo Metro)
05:22:33 <mdadas> there is a list of UCs (see draft)
05:23:04 <mdadas> mfoltz: is this aiming to address multiple media on the same device also?
05:23:18 <mdadas> yes but no clear how to spec that
05:23:55 <mdadas> Mathieu: if you split the timing provider
05:24:07 <mdadas> in the single device case there no timing provider
05:25:17 <mdadas> mathieu: can you pass a specific time?
05:25:38 <mdadas> no, the time stamp is given based on the current time on the device
05:27:09 <mdadas> if you need to give a specific time, you will need to create a timing provider
05:28:18 <mdadas> mfoltz: how do you deal with buffering? and in case of real time media?
05:29:32 <mdadas> for the live case, you need to ensure the UA will keep the timeline as much as it can (how is not defined)
05:30:11 <mdadas> mathieu: it depends again on the UCs (buffering or not)
05:31:13 <Roy> s/Tokyo Metro/JR Shinagawa Station/
05:32:21 <mdadas> all participants are invted to join the community group and to contribute on the github
05:32:31 <tidoust> RRSAgent, draft minutes
05:32:31 <RRSAgent> I have made the request to generate http://www.w3.org/2015/10/28-sync-minutes.html tidoust
05:38:44 <cpn> cpn has joined #sync
05:39:57 <rus> rus has joined #sync
05:40:45 <mfoltzgoogle> mfoltzgoogle has joined #sync
05:41:12 <Dewa> Dewa has left #sync
05:41:51 <rus> rus has joined #sync
05:41:56 <satoshin> satoshin has joined #sync
05:42:11 <nori> nori has joined #sync
05:42:19 <Dewa> Dewa has joined #sync
05:42:29 <Dewa> Dewa has left #sync
05:43:22 <rus> rus has joined #sync
05:45:06 <rus> rus has left #sync
05:45:08 <rus> rus has joined #sync
05:45:10 <rus> rus has left #sync
05:45:33 <shinya> shinya has left #sync
05:45:41 <tidoust> tidoust has joined #sync
06:03:30 <mfoltzgoogle> mfoltzgoogle has joined #sync
07:04:13 <mfoltzgoogle> mfoltzgoogle has joined #sync
07:05:40 <tidoust> tidoust has joined #sync
07:07:48 <akitsugu> akitsugu has joined #sync
07:07:50 <cpn> cpn has joined #sync
07:13:38 <rus> rus has joined #sync
07:34:53 <Roy> Roy has joined #sync
08:16:50 <akitsugu> akitsugu has joined #sync
08:27:04 <cpn> cpn has joined #sync
08:27:12 <katashin> katashin has joined #sync
08:32:09 <rus> rus has joined #sync
08:59:28 <mfoltzgoogle> mfoltzgoogle has joined #sync
09:15:24 <rus> rus has joined #sync
09:17:43 <rus_> rus_ has joined #sync
09:44:06 <rus> rus has joined #sync
10:34:00 <rus> rus has joined #sync
11:27:08 <rus> rus has joined #sync
11:42:43 <rus> rus has joined #sync
11:58:27 <rus> rus has joined #sync
12:34:40 <rus> rus has joined #sync
13:00:02 <rus> rus has joined #sync
13:09:44 <Roy> Roy has joined #sync
13:23:51 <mfoltzgoogle> mfoltzgoogle has joined #sync
13:41:59 <rus> rus has joined #sync
14:07:23 <tidoust> tidoust has joined #sync
14:55:15 <tidoust> tidoust has joined #sync
15:31:20 <rus> rus has joined #sync
16:28:32 <Roy__> Roy__ has joined #sync
16:30:37 <rus> rus has joined #sync
16:52:56 <rus> rus has joined #sync
18:35:13 <rus> rus has joined #sync
19:13:38 <rus> rus has joined #sync
19:45:57 <rus> rus has joined #sync
20:29:58 <rus> rus has joined #sync
22:00:35 <Roy> Roy has joined #sync
22:00:36 <rus> rus has joined #sync
22:55:38 <Roy> Roy has joined #sync
23:27:26 <rus> rus has joined #sync
23:31:51 <rus_> rus_ has joined #sync
23:32:54 <akitsugu> akitsugu has joined #sync
23:51:30 <Roy> Roy has joined #sync