W3C home > Mailing lists > Public > public-audio@w3.org > October to December 2012

[Bug 17411] (AudioPannerNodeUnits): AudioPannerNode units are underspecified

From: <bugzilla@jessica.w3.org>
Date: Tue, 04 Dec 2012 18:34:46 +0000
To: public-audio@w3.org
Message-ID: <bug-17411-5429-No9vAt6A6z@http.www.w3.org/Bugs/Public/>

--- Comment #5 from Chris Rogers <crogers@google.com> ---
(In reply to comment #4)
> (In reply to comment #3)
> > Sorry Marcus, I wasn't clear about that part.  The doppler effect uses the
> > .speedOfSound attribute in conjunction with the velocity vectors for both
> > the AudioPannerNode and the AudioListener.  These velocity vectors are in
> > meters/second and are independent of the units used for position and
> > orientation.  This is taken directly from the OpenAL specification.
> I still don't understand why we need to have a unit at all (I see nothing in
> the algorithm that depends on actual units). Could it not be unit-less, and
> work just as it is? It would be confusing (IMO) to force the usage of m/s
> for some vectors, and then let people use whatever they want (e.g. inches or
> miles) for other vectors.
> I'd personally prefer an all-or-nothing solution: either all vectors are in
> m and m/s, or they are all in [custom] and [custom]/s, or possibly even
> [custom_length] and [custom_length]/[custom_time] (like miles/h).

I'm just taking this interpretation from the OpenAL specification.  But you're
right, we could just say that .speedOfSound is the speed in arbitrary units
which are also used by the velocity vectors.  These units are independent of
the units used for position and orientation vectors.

How does that sound?

You are receiving this mail because:
You are on the CC list for the bug.
Received on Tuesday, 4 December 2012 18:34:48 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:03:14 UTC