>Lots of interesting stuff deleted (I know very little about sound in virtual
>worlds-- one general comment: a lot of the issues you raise are really
>quality of browser issues; smart browsers will try to simulate virtual sound
>in virtual environments more realistically...).
Yes. What we need to figure out are what nodes we need to best define sound,
and leave everything else to browser designers.
>If a sound isn't looped, we'd have to somehow define what makes it start.
> That won't be answered until we've defined a general mechanism for
>interaction and behaviors in the virtual world.
It seems to me that we need to distinguish between interactive and
non-interactive behaviors. Spinning logos, timed sounds, animation-on-a-path
and even a time-sequenced 3D model reenacting the Kennedy assassination
(potentially right down to animated waving arms of crowd members) can all be
implemented without any interactive features whatsoever.
The more difficult part is defining an extensible architecture for
interactive behavior, that will start with the basics (click on a drawer to
open it) but allow elaborate extensions as well (objects that retransmit
sounds to other areas, glass panes that shatter properly when an avatar
throws a baseball through it).
Are there any proposals out there that I've missed describing how to handle
these problems?
--Andy
[email protected]
P.S. Sorry if this is premature without 1.0 being finalized (what's
happening with MIME types and text nodes?). I'm just discussing all this
because I don't have a browser to play with. :)