[x3d-public] X3D agenda 1 May 2020: X3D4 Audio and Sound Component

[Don Brutzman]

Friday 1 May 2020, 0800-0930 pacific, X3D Working Group continues its regular weekly efforts on building X3D4 specification.

Feedback on Mantis issues remains welcome. Dick and I continue to make progress with 6 more editorial changes resolved this week.

* Mantis: View Issues
   https://www.web3d.org/member-only/mantis/view_all_bug_page.php

This week we are continuing development efforts on Audio and Sound Component contributions by Efi Lakka and Thanos Malamos.  Efi's recent modifications to PR9 for shape.html and sound.html have been integrated online in github.  For members:

* https://github.com/Web3DConsortium/X3D/tree/master/ISO-IEC19775/ISO-IEC19775-1/ISO-IEC19775-1v4.0/ISO-IEC19775-1v4-WD1/Part01/components

* Mantis 1267: Strategies to Improve X3Dv4 Audio and Sound Component
   https://www.web3d.org/member-only/mantis/view.php?id=1267

Slides from last meeting now attached at

* X3D4 Implementations
   https://www.web3d.org/x3dv4-implementations
   X3dSoundPresentationSynopsis_CallMeeting17_04_2020.pdf

Important addition: acoustic properties have been proposed for Shape component.  For a variety of reasons, we think that the relevant fields are better added as an AcousticProperties node, rather than further individual fields under Material.  This would appear as under Appearance as an acousticProperties field (similar to how LineProperties, PointProperties and TextureProperties are handled).

AcousticProperties seems like the correct name for this node (rather than SoundProperties) because of it's relationship to geometry in a world, rather than sound generation per se.

* Wiktionary: Acoustics
   https://en.wiktionary.org/wiki/acoustics
   "1. The physical quality of a space for conveying sound."

Dick and I had the following questions to pose during the meeting.

a.       Merge of AudioNode with X3DSoundSourceNode, or rename as X3DAudioNode?
b.       Change name of AudioParam to AudioParameters
c.       Please add revision date to first page of slide sets
d.       Are all the “Effects” really the list of filters in which case we may need an X3DAudioFilterNode
e.       We need to discuss the hierarchy of Audio nodes
f.       Please add numbers to the slides
g.       Current architecture disallows inheriting a node interface from a concrete node so we may need an X3DAudioContextNode abstract node type and concrete nodes to flesh it out.
h.       Latency hint string or double precision decision, or both?
i.       AudioNode inherits from a concrete node type (see g above)

Also needed:
- link to example models for demonstration and comparison with evolving specification interfaces.
- start list of feedback comments for W3C Audio working group.

==================================

Zoom room coordinates are now linked via the Web3D Calendar.

* https://www.web3d.org/calendar/month

* https://www.web3d.org/calendar/x3d-graphics-working-group/2019-09-13t150000-2019-09-13t163000-2019-09-20t150000-2019-09

Thanks for all inputs and attendance.

all the best, Don
-- 
Don Brutzman  Naval Postgraduate School, Code USW/Br       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