[x3d-public] mediaDeviceID accessType ought to be inputOutput

[Brutzman, Donald (Don) (CIV)]

Discussion today with Thanos and Efi on usage:

a. Author might define anything, e.g. mediaDeviceID="Bose Speakers" as input value,
b. Browser is free to ignore initial settings like this,
c. Browser or operating system handles selections, according to end-user direction,
d. Browser reports actual device value selected as an output,
e. A local Script (html or X3D) might subsequently override the value.

We are generally silent about these input/output device ID possibilities, letting the Web Audio API define functionality.

Editorial correction:
change
   "The mediaDeviceID field is a unique identifier for the represented device."
to
   "The mediaDeviceID field is a unique identifier for the active device."

v/r Don

From: Brutzman, Donald (Don) (CIV)
Sent: Sunday, August 1, 2021 5:41 PM
To: 'athanasios.malamos at gmail.com' <athanasios.malamos at gmail.com>; Eftychia Lakka <efilakka at gmail.com>; maria.mary.papadaki at gmail.com; Richard F. Puk (puk at igraphics.com) <puk at igraphics.com>
Cc: x3d-public at web3d.org; Brutzman, Donald (Don) (CIV) <brutzman at nps.edu>
Subject: mediaDeviceID accessType ought to be inputOutput

A common field signature in Sound component appears to be incorrect:

  SFString [out] mediaDeviceID

This field is not device output stream but rather identification, which an author may need to set or get. Thus accessType inputOutput [in out] is more appropriate.

Examples include

  *   16.3.2 X3DSoundDestinationNode
  *   https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-CD1/Part01/components/sound.html#X3DSoundDestinationNode

We also need to ensure that the prose definition for mediaDeviceID appears in abstract types.  From 16.4.3 AudioDestination:
"The mediaDeviceID field corresponds to the ID parameter functionality defined in W3C Web Audio API [W3C-WebAudio]<https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-CD1/Part01/references.html#W3C-WebAudio>"

Once decided, this is easily fixed and then changes can be applied.  Please advise if you agree, thanks for considering the problem.

Tracking the issue as Mantis 1369,

  *   https://www.web3d.org/member-only/mantis/view.php?id=1369

all the best, Don
--
Don Brutzman  Naval Postgraduate School, Code USW/Br       brutzman at nps.edu<mailto:brutzman at nps.edu>
Watkins 270,  MOVES Institute, Monterey CA 93943-5000 USA   +1.831.656.2149
X3D graphics, virtual worlds, navy robotics http://faculty.nps.edu/brutzman

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20210804/10a0973e/attachment-0001.html>