[x3d-public] X3D4 Audio and Sound progress, 17 JUN 2020

[Joseph D Williams]

HI, I’m not sure how much of this audio replaces or enhances existing, just recalling the current NIST-derived audio examples in archives and hoping we can plan some comparable and extended tests.

https://www.web3d.org/x3d/content/examples/ConformanceNist/Sounds/AudioClip/index.html

https://www.web3d.org/x3d/content/examples/ConformanceNist/Sounds/Sound/index.html

Thanks,
Joe


From: Don Brutzman
Sent: Wednesday, June 17, 2020 10:21 AM
To: X3D Graphics public mailing list
Cc: Efi Lakka; Athanasios Malamos
Subject: [x3d-public] X3D4 Audio and Sound progress, 17 JUN 2020

Attendees: Efi Lakka, Thanos Malamos, Dick Puk, Don Brutzman

No Web3D member-only information is included in these minutes.

1. Refined structure for object model.

Great progress, we are converging nicely.

Efi will distribute updated document.  Thank you!

We discussed Microphone node.  We think it best fits as MicrophoneSource as an X3DSoundSourceNode, with no direct need of X3DSensorNode.


2. Discussed "sound effects" nodes.  Observed that names like "AnalyserNode, OscillatorNode, ChannelSplitterNode etc. are the WebAudio API names, the suffix "Node" would not be part of the X3D names (because "Node" indicates abstract types).

Wondering if all of the sound effects could have a parent X3DSoundEffectsNode.  Conjectured:

+- X3DTimeDependentNode -+- X3DSoundEffectsNode -+- SoundEffectsGroup (containing the following as an audio graph) or
                                                  +- SoundProcessingGroup (or something)
                                                  +- Analyzer
                                                  +- Oscillator
                                                  +- ChannelSplitter
                                                  +- etc.
3. Next steps.

a. For consideration... much of the structure for sound-effects node composition can be "side-stepped" if we allow support for WebAudioApi javascript source as a way to describe audio graph.  If accepted, this would be connected via /url/ field for SpatialSound node.  It also would confirm whether all spatialized inputs/outputs are available in SpatialSound node.  This is an option (not a requirement) that might provide comparisons and clarity regarding whether node-defined audio graphs in X3D have the same expressive power.

b. Further thought on whether/how to include SoundEffects nodes, building on past work.  Primary topic for next week.

c. Dick and Don will update X3D4 draft specification organization to match the current structure in the document, establishing placeholders for agreed-upon nodes.  We will try to keep up with incremental progress.

Our next goal is to have a preliminary releasable draft X3D4 Specification by 30 JUN 2020, anticipating public release of draft for SIGGRAPH 2020.

We will try to meet Wednesday 0900 pacific (1900 EET Eastern European Time for Crete) in order to not collide with Web3D User Experience (Web3DUX) working group meeting.

"What say??" ... Have fun with X3D audio and sound!  8)

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

_______________________________________________
x3d-public mailing list
x3d-public at web3d.org
http://web3d.org/mailman/listinfo/x3d-public_web3d.org

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20200617/7736851f/attachment.html>