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 10:26:01 +0000
To: public-audio@w3.org
Message-ID: <bug-17411-5429-uD59TZfSma@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17411

Marcus Geelnard (Opera) <mage@opera.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|FIXED                       |---

--- Comment #4 from Marcus Geelnard (Opera) <mage@opera.com> ---
(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).

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Tuesday, 4 December 2012 10:26:05 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:50:03 UTC