ken: telepresence use case in WebRTC
... invited my colleague, Toshiya Nakakura working on this topic
... how to address issues

toshi: engineer from NTT Com and a researcher at Keio Univ.
... WebRTC is a sophisticated mechanism
... would like to share use cases
... [Immersive Telepresence]
... what's that?
... enable the operaters\\\\\\\\\\\\\\
... (demo video)
... help an old lady
... offer a robot
... she felt as if she were there at the wedding ceremony
... deeply moved
... another use case
... (another demo video)
... we have many disasters in Japan
... dangerous to go there
... can control vehicle remotely
... from a safe place
... [Importance of haptic sensation]
... [What does the word "haptic information" mean?
... 3 kinds of basic information
... [To reproduce haptic sensation in remote place]
... simultaneous control
... operator's perception
... [Recognition of stiffness]
... experiment to stretch screen remotely
... if video delays
... people put more power
... due to the latency
... the point is how to send haptic information
... and videos synchronously
... the current spec
... two channels
... mediastream and datachannel
... mediastream can send video and audio
... media synch
... we can send it using this channel
... datacannel arbitrary binary
... [Required level of synchronization]
... how human being "feels"?
... surveyed psychophysics papers
... [TOJ (Temporal Order Judgment)]
... e.g., display vision 10ms earlier than haptics
... [Temporal Order Judgment]
... 50% point is Point of Subjective Simultaneity (PSS)
... [Temporal Order Judgment]
... the window between 25% and 75% is TWI
... temporal window of integration
... [peculiar phenomenon...]
... two factors affect perceived simultaneity
... activve motor control and visual motion feedback
... and another
... [Measured Value]
... measured value with visual motion feedback
... passive touch and active touch
... [my 1st implement to synchronize]
... (diagram)
... [evaluate with jitters]
... set 10 kinds of jitter settings
... [CDF]
... red and green results
... simple WebRTC and proposal
... [Recognition of stiffness]
... further survey needed
... [idea for synchronizing vision and haptics]
... proposed to define RTP format
... we can use some format
... [Proposal]
... media format discussed by IETF
... also W3C work on WebRTC NV
... need to check the detail
... note SOA 0ms is not same as PSS, so need calibration
... getUserMedia API handles only one specific device (e.g., camera)
... if we use 2 different cameras, need synchronization mechanisms
... possibly related to WebVR API
... [I need a help]
... need your help
... this research should cover many areas

kar: webrtc started next version work
... use case discussion still open

toshi: ok
... this is still at research level
... maybe a bit weak for use case proposal

kaz: would agree with Karthik
... you can brush up your use case and provide concrete description

eric: agree
... you can generalize a type of use cases

toshi: ok
... good to hear that

eric: important to have data as well

benoit: question about @1

toshi: different position when my head moved
... so time offset is important
... google chrome creates two streams

eric: that's probably caused by some lower down
... could be adjusted by the implementation of the browser
... would file a bug

kaz: need clarification for record
... which part was the question?

p22

(will be updated later; getUserMedia API... issue)

(issue with different offset starting positions)

ken: so not only related to WebRTC
... any other questions?

toshi: if you are interested, you can try the demo

ken: some proposal to address this issue as explained

(will generate the minutes offline later :( )

ken: some proposal by Prof. Minamizawa from Keio
... but other proposals could be applied

kaz: a TF within the MEIG exists, so you can join it. also you can create a CG if you want.

eric: synchronized metadata proposal being made this week
... specifically for WebRTC

ken: ok
... would like to talk about the details offline
... would appreciate your help

eric: you should make sure you're part of the discussion on WebRTC next version

ken: yes
... also liaison between the media group and the rtc group
... we have a lot of feedback here
... interested in the metadata synchronization discussion

toshi: tx for joining

[adjourned]