>I like all this except for the "radiusOfEffect" field. The volume field
>should suffice. Knowing the volume, using a falloff based on attenuation
>at sea level or something, and deciding how quiet the sound has to be to
>cut it off, the browser can compute a culling cube. The radius would be
>useful if you're trying to simulate sound transmission on another planet
>but I don't think we need that right now...
I think the point of "radiusOfEffect" was to make it easy for browsers to see
if they needed to process a sound or not. In a large model, that could be quite
a help--in a model of the White House, there might be sounds in the West
Wing that you definitely wouldn't want to process in the East Wing.
My more general question about sound is what it means to include a sound when
VRML doesn't have interactivity or any sense of "time" yet. Looping,
background sounds would make sense--otherwise the sound would (I guess) go
off once when the model was started and not again. Am I missing something?
--Andy
[email protected]