International organisation for standardisation organisation internationale de normalisation

26.2Contributions

Session	Number	Title	Source
MPEG-V	m16379	Basic description languaues for Sensory Device Capabilities of MPEG-V Part2 Control Information	Sang-Kyun Kim Jin-Seo Kim Maeng-Sub Cho Bon-Ki Koo Yong Soo Joo
MPEG-V	m16380	Basic description languaues for Sensory Device Commands of MPEG-V Part2 Control Information	Sang-Kyun Kim Jin-Seo Kim Maeng-Sub Cho Bon-Ki Koo Yong Soo Joo
MPEG-V	m16381	Basic description languaues for User Sensory Preferences of MPEG-V Part2 Control Information	Sang-Kyun Kim Jin-Seo Kim Maeng-Sub Cho Bon-Ki Koo Yong Soo Joo
MPEG-V	m16360	Study on representation of characteristics for MPEG-V Sensory Devices	Shin-ya Hasegawa Yasuaki Tokumo Takuya Iwanami
MPEG-V	m16368	Sensory Device Capability Metadata	B.S. Choi SangHyun Joo
MPEG-V	m16385	User Sensory Preference Metadata	B. S. Choi Sang Hyun Joo

m16379,

Proposed schema for device capabilities aligned with sensory effects. Schema is consisted of Base attribute and specific attributes for each effect types

m16380,

Proposed schema for sensory device commands aligned with each sensory effect. Schema is consisted of Base attribute and specific attributes for each effect types.

m16381

Proposed schema for user sensory preferences aligned with each sensory effect. Schema is consisted of Base attribute and specific attributes for each effect types.

m16360

Proposed schema for device capabilities Base attributes include minimum intensity, preparation time, and used position in addition to previous contributions.

Proposed to include expected capability as a part of sensory effect metadata by using schema for device capability.
question about how to signal “preambles”

question about what is an appropriate schema of “preambles”

m16368

question about position : we don’t know propagation matrix of device. so, position cannot give meaningful information to RoSE engine unless there is universal physical law can be applied to this.

delayTime : the time difference between the time the device started and the time when the device reaches its maximum intensity  need to be harmonized with m16360

minIntensity : this does not needed for some device types. so, it will not be part of base attribute but specific attributes for some device types which need this.

some attributes need to improve.

try to keep consistency among different devices

use “device capability type” instead of “device type”
m16385

Similar to m16368