[x3d-public] X3D agenda 2 OCT 2020: shadows, audio concepts

[cbullard at hiwaay.net]

In music land we call a set of components from input to output with  
processors in between a "desk" or "mixer".

I doubt they are formal enough for Dick, but that is common parlance.   
Because I may not grasp the working group's intentions adequately, it  
may be those terms only apply when a combination of the X3D sound  
components are put in an assembly (a group of X3D components assembled  
under a controller (such as a sound board, movie remote control etc,)).

Watching this thread with baited breath.  Exciting to see these kinds  
of capabilities on the horizon.  Making slow but steady process with  
my X3D media control components.   It would be nice if we could get  
some feedback from members who make the X3D browsers.   In olden days  
we worked here on the public list with them to get feedback on  
projects.  It seems the case today is we (content makers) gather on  
different FB pages and there is little to no feedback for the most  
part particularly from the vendors.   BitMgt is a stone cold gray face  
which is tragic considering how many are developing for the BS Contact  
engine using vivaty and noteoad still (it all still works).   That is  
the finest compliment to be paid to the X3D cabal:  unlike almost all  
of the competition from the 90s on, X3D/VRML is still standing and it  
all still works.  The classic core is solid and the new nodes are  
behaving well (just now experimenting with the layer nodes).

Good job, folks.  You were the right people to take on the helm of 3D  
on The Web.  You improve the tech AND protect the content.  The life  
cycle argument was and is right:  we choose X3D because it is the  
safest bet with regards to content being viable into the future  
without serious retooling.   Success!

len

Quoting Don Brutzman <brutzman at nps.edu>:

> Definition for review:
>
>> We need an X3D definition for "audio graph" term.  Suggested draft:
>>
>> * An /audio graph/ is a collection of nodes structured to process  
>> audio inputs and outputs
>>   in a manner that is constrained to match the structure allowed by  
>> the Web Audio API.
>>
>> We have defined all of the new nodes (beyond Sound, Spatial Sound  
>> and AudioClip) to match the terms and capabilities of Web Audio API.
>>
>> This means a collection of the new nodes, that together can create  
>> and process sound, produce a result that needs to inputs for our  
>> Sound and SpatialSound nodes.  In combination, the output is  
>> similar to a computational version of a simple AudioClip node.  It  
>> is a source, computationally created, whereas the AudioClip is a  
>> prerecorded version.
>
> Audio and sound concept summary:
>
>> ========================================
>> Basic stages for flow of sound, from source to destination:
>>
>> a. Sources of sound (perhaps an audio file or MicrophoneSource,  
>> perhaps signal processing of channels in audio graph),
>>
>> b. X3D Sound or SpatialSound node (defining location direction and  
>> characteristics of expected sound production in virtual 3D space),
>>
>> c. Propagation (attenuation model, may be modified by  
>> AcousticProperties based on surrounding geometry),
>>
>> d. Reception point (avatar "ears" or recordable listening point at  
>> some location and direction, that "hears" result, with left-right  
>> pan and spatialization).
>> ========================================
>
> ---
>
> Be there or be square!  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