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

[Richard F. Puk]

Hi, Efi –

 

One small problem with your attachment caused by an error in the X3D Interface Hierarchy:

 

ViewpointGroup is not derived for X3DViewpointNode. Instead, it is derived directly from X3DChildNode. This is because ViewpointGroup is a catalog of viewpoints rather than a viewpoint itself. We have created a Mantis issue to fix the spec.

 

If you have any questions, we can discuss them on Wednesday.

 

n  Dick

 

/******************************************

| Richard F. Puk, Ph.D., President

| Intelligraphics Incorporated

| 7644 Cortina Court

| Carlsbad, CA  92009-8206

| Tel: +1-760-753-9027  Mobile:  +1-760-809-9027

| Email:   <mailto:puk at igraphics.com> puk at igraphics.com

\****************************************** 

 

 

 

From: Eftychia Lakka [mailto:efilakka at gmail.com] 
Sent: Wednesday, June 24, 2020 5:22 AM
To: Don Brutzman
Cc: X3D Graphics public mailing list; Athanasios Malamos; Richard F. Puk
Subject: Re: X3D4 Audio and Sound progress, 17 JUN 2020

 

Dear all, 

 

please find attached the report from the Audio and Sound progress call on 17 June 2020.

 

Best regards, 

Efi Lakka

 

Στις Τετ, 17 Ιουν 2020 στις 8:20 μ.μ., ο/η Don Brutzman <brutzman at nps.edu> έγραψε:

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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20200629/9e22582b/attachment-0001.html>