{"id":170,"date":"2016-04-25T11:57:41","date_gmt":"2016-04-25T11:57:41","guid":{"rendered":"https:\/\/www.w3.org\/community\/webtiming\/?p=170"},"modified":"2016-04-25T12:01:28","modified_gmt":"2016-04-25T12:01:28","slug":"timing-object-at-nabshow-2016","status":"publish","type":"post","link":"https:\/\/www.w3.org\/community\/webtiming\/2016\/04\/25\/timing-object-at-nabshow-2016\/","title":{"rendered":"Timing Object at NABShow 2016"},"content":{"rendered":"

Nj\u00e5l and I are just back from NABShow 2016, 16-21 April in Las Vegas where MediaScape partners Norut and Vicomtech promoted the timing object and the W3C Multi-device Timing Community Group. <\/span><\/p>\n\"Nj\u00e5l<\/a> Nj\u00e5l Borch at Timing Object booth – NABShow 2016\n

You may find our main leaflet here :\u00a0Timing object in a nutshell<\/a><\/p>\n\"Multi-device<\/a> Multi-device sync\n

Our setup in the Futures Park booth was fairly simple; four different laptop devices and two smart phones. \u00a0As you can see in the picture we used the laptops to present a selection of HTML5 videos being synchronized across the different screens (using Shared Motion and the MediaSync library). Two laptops were cabled, two on WiFi. We used Firefox and Chrome browsers. One smart phone was used for controls (play, pause time-shifting the timing objects as well as switching between videos). Another smart phone was used to present the audio of the video. We also brought two pairs of headphones, one connected to a laptop computer and one connected to the smart phone. This way, by using both headphones together, our audience could verify echoless sync between smartphone and laptop computer. We also made sure to reload the Web-browsers to demonstrate how quickly sync is regained – fractions second as long as video data is available. The demos ran in perfect synchrony for four consecutive days, without as much as a glitch. That\u2019s impressive – especially considering the poor networking conditions in the NAB exhibition hall!<\/span><\/p>\n

Reactions to the demonstrations were overwhelmingly positive. Many people expressed excitement that there was an initiative aiming at improved support for timing on the Web platform. People were also taken aback by the quality of the synchronization as well as the prospect of doing this globally. Some people were curious about use cases, whereas others immediately recognized the need for timing and synchronization in various broadcasting applications, be it live streaming, ad-insertion, tiled screen setups, timed UGC, collaborative viewing, remote control or what not. We mentioned concrete use cases such as secondary device applications, alternative audio tracks on secondary devices (accessibility etc). We also presented more high level value promises such as timing-consistency in UX and the important role of timing with respect to integration and interoperability between heterogeneous media systems. Finally, we had some very concrete interests from very central players. We\u2019ll let you know when interests materialize.<\/span><\/p>\n

So, a big thanks to Norut, Vicomtech and MediaScape for an excellent show at NAB!<\/span>
\nNext major event up for the Multi-device Timing CG will likely be a F2F in Lisbon at TPAC 2016 in september. <\/span><\/p>\n

Best regards,\u00a0Ingar<\/p>\n","protected":false},"excerpt":{"rendered":"

Nj\u00e5l and I are just back from NABShow 2016, 16-21 April in Las Vegas where MediaScape partners Norut and Vicomtech promoted the timing object and the W3C Multi-device Timing Community Group. You may find our main leaflet here :\u00a0Timing object … Continue reading →<\/span><\/a><\/p>\n","protected":false},"author":7427,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_s2mail":"yes","footnotes":""},"categories":[2],"tags":[],"class_list":["post-170","post","type-post","status-publish","format-standard","hentry","category-announcements"],"_links":{"self":[{"href":"https:\/\/www.w3.org\/community\/webtiming\/wp-json\/wp\/v2\/posts\/170","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.w3.org\/community\/webtiming\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.w3.org\/community\/webtiming\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.w3.org\/community\/webtiming\/wp-json\/wp\/v2\/users\/7427"}],"replies":[{"embeddable":true,"href":"https:\/\/www.w3.org\/community\/webtiming\/wp-json\/wp\/v2\/comments?post=170"}],"version-history":[{"count":2,"href":"https:\/\/www.w3.org\/community\/webtiming\/wp-json\/wp\/v2\/posts\/170\/revisions"}],"predecessor-version":[{"id":173,"href":"https:\/\/www.w3.org\/community\/webtiming\/wp-json\/wp\/v2\/posts\/170\/revisions\/173"}],"wp:attachment":[{"href":"https:\/\/www.w3.org\/community\/webtiming\/wp-json\/wp\/v2\/media?parent=170"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.w3.org\/community\/webtiming\/wp-json\/wp\/v2\/categories?post=170"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.w3.org\/community\/webtiming\/wp-json\/wp\/v2\/tags?post=170"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}