[x3d-public] X3D Audio meeting minutes, updated sound component, XML/java/python/turtle/validator updates

John Carlson yottzumm at gmail.com
Mon Oct 26 05:39:41 PDT 2020


Re:  ECMAScript 2020 and GraalVM

https://github.com/graalvm/graaljs

https://www.graalvm.org/

"GraalVM JavaScript is compatible with the ECMAScript 2020 specification
<http://www.ecma-international.org/ecma-262/11.0/index.html>. "

Based on OpenJDK 8 and 11

GraalVM may be a path forward for NetBeans?

Excellent!

John

On Mon, Oct 26, 2020 at 7:14 AM John Carlson <yottzumm at gmail.com> wrote:

> Re:  nashorn branch
>
> 1.  Suggest that John create a GraalVM build for X3DJSONLD.
>
> 2. Possibly look for another implementation of ECMAScript in Java (Rhino?)
>
> 3.  Suggest deprecation of branch as people move to OpenJDK 15
>
> Re: node branch
>
> 1.  Continue supporting node branch, update example filenames.
>
> 2.  Run tests and examine results.
>
> 3. Enhance X3dToNodeJS.xslt as needed. (Don)
>
> 4. Examine potential broken Java contracts as found with pyjnius.
>
> 5.  Upgrade node.js java module to go along with OpenJDK 15.
>
> Re: John’s health
>
> 1. Resumed relaxation has improved John’s RSI.
>
> 2. Suggest minimal typing, RFI on alternatives (Jeff Gray and Eclipse?),
> particularly a NetBeans solution if X3D-Edit continues down NetBeans path.
>
> 3. Also investigate Git Desktop or netbeans git.
>
> 4. Consider resuming fish oil, aspirin.
>
> John
>
> On Mon, Oct 26, 2020 at 12:02 AM Don Brutzman <brutzman at nps.edu> wrote:
>
>> 1. Thanks for the excellent meeting of the Audio and Sound team Friday.
>> Steady bashing is knocking this into steadily improving state.
>>
>> The refinements we discussed were applied to good effect, passing all X3D
>> infrastructure tests associated with X3DUOM.
>>
>> Synopsis changelog:
>>
>> X3D XML Schema update activity:
>> https://www.web3d.org/specifications/x3d-schema-changelog.txt
>>
>> 24 OCT 2020, brutzman, puk, athanasios, lakka, kamburelis, plesch
>> - (v4.0) rename ChannelSelector field channelNumber as channelSelection
>> for clarity
>> - (v4.0) AudioBufferSource includes boolean field 'loop'
>> - (v4.0) pitch moved from abstract type X3DTimeDependentNode to
>>           AudioClip, MovieTexture with no change to X3D3 functionality
>> - (v4.0) duration_changed moved from abstract type X3DSoundSourceNode to
>>           AudioClip, MovieTexture with no change to X3D3 functionality
>> - (v4.0) loop moved from abstract type X3DTimeDependentNode to
>>           TimeSensor, AudioClip, MovieTexture with no change to X3D3
>> functionality
>> - (v4.0) ListenerPoint not X3DBindableNode
>> - (v4.0) X3DLightNode shadowIntensity, shadows (enabled); X3DShapeNode
>> castShadow
>> - (v4.0) TextureProjectorPerspective renamed as TextureProjector,
>>           TextureProjectorParallel    remains as originally named
>> - (v4.0) Sound component audio graphs: all node types and nodes
>> - (v4.0) Shape component audio graphs: AcousticProperties
>> - (v4.0) PointProperties pointSizeAttenuation -> attenuation, type SFVec3f
>> - (v4.0) PointProperties omit colorMode, colorModeChoices
>> - (v4.0) revise default values for nearDistance/farDistance
>>
>> X3D4 XML Schema, XML DOCTYPE and X3DUOM sources and documentation all
>> updated, deployed and available at
>>
>> [1] X3D Specifications: Schema and DOCTYPE Validation
>>      https://www.web3d.org/specifications/
>>
>> Attached in follow-on message is PDF of github draft for your reviewing
>> convenience.  As before, have applied light-blue "editorsNote" CSS styling
>> to changes I've made.  These changes are quite detailed but reviewable.
>>
>> Following our weekly review this coming Wednesday, I hope to earn each of
>> your permissions to clean up this entire document by sorting fields and
>> removing strikeouts of our previous draft strategies.  No more "blue" after
>> that in preparation for next phase of complete document cleanup next month.
>>
>> ---
>>
>> 2. I've created an initial test scene AllAudioGraphNodes.x3d that has
>> been helpful for debugging.
>>
>> Attached, with a bit more work this example (and then your excerpted
>> examples Efi) will be getting pushed to
>>
>> [2.1] X3D for Advanced Modeling (X3D4AM) Examples Archive
>>        https://x3dgraphics.com/examples/X3dForAdvancedModeling
>>
>> https://x3dgraphics.com/examples/X3dForAdvancedModeling/AudioSpatialSound
>>
>> All audio tooltips also updated, which provides a number of further
>> checks on correctness and clarity.  That was a big pile of work, and
>> helpful for all of us as a ready reference to ensure that we have a common
>> understanding.  Incidentally those tooltips (describing each node and
>> field) also become embedded documentation for Java, Python and Turtle
>> libraries.
>>
>> [2] X3D4 Tooltips
>>      https://www.web3d.org/x3d/tooltips/X3dTooltips.html
>>
>> Sound component / audio-graph nodes of interest:
>>
>> Analyser
>> AudioBufferSource
>> AudioClip
>> AudioDestination
>> BiquadFilter
>> ChannelMerger
>> ChannelSelector
>> ChannelSplitter
>> Convolver
>> Delay
>> DynamicsCompressor
>> Gain
>> ListenerPoint
>> MicrophoneSource
>> MovieTexture
>> OscillatorSource
>> PeriodicWave
>> Sound
>> SpatialSound
>> StreamAudioDestination
>> StreamAudioSource
>> WaveShaper
>>
>> ---
>>
>> 3. Java X3DJSAIL built, passing tests and deployed.  Now testing under
>> new OpenJDK 15.0.1.  8)
>>
>> [3] X3D Java Scene Access Interface Library (X3DJSAIL)
>>
>> https://www.web3d.org/specifications/java/X3dJavaSceneAuthoringInterface.html
>>
>> (Sorry John but nashorn and jjs are past deprecation and completely gone
>> now, so we'll have to figure out another connection.)
>>
>> ---
>>
>> 4. Python x3d.py X3DPSAIL built, passing tests and deployed in Python
>> Packaging Index (PyPi).  Now testing under new Python 3.9.  8)
>>
>> [4.1] X3D Python Scene Access Interface Library (X3DPSAIL)
>>        https://www.web3d.org/x3d/stylesheets/python/python.html
>>
>> [4.2] PyPi Python package x3d
>>        https://pypi.org/project/x3d
>>
>> ---
>>
>> 5. X3D Ontology also updated, passing tests and deployed.
>>
>> [5.1] X3D Ontology for Semantic Web
>>        https://www.web3d.org/x3d/content/semantics/semantics.html
>>
>> Now includes papers and slideset for upcoming conference presentation.
>>
>> [5.2] X3D Ontology for Querying 3D Models on the Semantic Web, Don
>> Brutzman and Jakub Flotyński,
>>        Web3D 2020 Conference, Seoul Korea, 9-13 November 2020, with
>> accompanying presentation.
>>
>> https://www.web3d.org/x3d/content/semantics/documentation/papers/Web3D2020BrutzmanFlotynskiX3dOntology.pdf
>>
>> https://www.web3d.org/x3d/content/semantics/documentation/papers/Web3D2020BrutzmanFlotynskiX3dOntologyPresentation.pdf
>>
>> ---
>>
>> 6. X3D Validator was updated this morning, it will continue tracking
>> these improvements.
>>
>> [6] X3D Validator
>>      https://savage.nps.edu/X3dValidator
>>
>> ---
>>
>> So... a lot is coming together and converging on final X3D4.  Having good
>> quality X3D4 models should simplify other efforts.
>>
>> Have fun with X3D4 and audio graphs!  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/20201026/2b34dc80/attachment.html>


More information about the x3d-public mailing list