Re: MISC: Inlined Sound Support

oconnor ([email protected])
Sat, 15 Apr 1995 15:50:03 -0400 (EDT)


> How about this:
>
> PointSound {
> fields [ SFVec3f position, SFFloat radiusOfEffect, SFFloat volume,
> SFString url ]
>
> position 0 0 0
> radiusOfEffect 100.0
> volume 0.5
> url "http://iuma.com/Samples/HappyBirthday.aiff"
> }

In VRML 1.0 we have three different light nodes. Are we going to have
three different sound nodes? I don't think we need to. I also don't think
we need three different light nodes (a little late now...;) heres why:

DirectionalLight has ON, Intensity, Color, Direction,---------,--------,---
PointLight has ON, Intensity, Color,----------,Location ,--------,---
SpotLight has ON, Intensity, Color, Direction,Location,Dropoff,Cutoff

Why not just make one light node. And the attributes it doesn't use get
nulls (or 0 values if that works..)? I know this is late (seeing how 1.0
is out), and you may have already discussed this point. If we had one
light node, then we could have 1 sound node. And that sound node could
have:

Sound has On, Intensity(dB), URL, Direction, Location, Dropoff, Cutoff

Doesn't sound and light act nearly the same way? We have attributes in the
material node that affect light (shininess, transparency..etc) Why not
add in attributes to account for Sound (reflection, absorbtion)? Either
the server can account for this and actually tell the browser what he
hears and at what level(dB), or the browser can account for it...

I demand equal rights for sound waves (hehe). Sound and Light are equal!
Right-on brother!