- From: Jerome Etienne <jerome.etienne@gmail.com>
- Date: Tue, 13 Mar 2012 15:00:17 +0100
- To: public-audio@w3.org
- Message-ID: <CAN_PVv4YPqQTjc8JviFHoPm3XQkLu1uKF-0TZX+YHsof3nNc5Q@mail.gmail.com>
Hi, While experimenting with webaudio api[1], i hit some issues which triggered questions. I am new to this mailing list, so im not sure it is the proper forum. If it isnt, feel free to reroute me :) 1. How to handle page visibility ? When the page isnt visible, what is the recomended behavior ? should i set the volume to 0 ? something else ? Currently i do nothing special, but it has glitches. The positional audio isnt updated. And i hear "clicks" in the audio when the browser is busy on some other pages (implementation issue related to scheduling?) 2. How to handle 'gimbal lock' with positional audio ? When the sound is exactly on top of the listener, it is heard as if it was from the left, then from the right. At first sight, it seems close to a gimbal lock[2] issue. Is this diagnostic correct ? How to handle this ? Should i ignore it and say 'well it is rare enougth, nobody will notice' ? is that an issue in my code or in the browser implementation ? 3. When using audiopannernode, coneOuterAngle seems to be ignored. Let me explain. When i change .coneInnerAngle and .coneOuterGain, they have the effect i expect. But no matter which value i put in .coneOuterAngle, the outter cone seems to be the max possible. According my understand, there are 3 states. "inside innerCone", "inside outerCone" and "totally outside". Is that correct ? when the listener is "totally outside", im under the impression no sound should be heard, correct ? Lots of questions on various subjects :) Please, let me know what you think. Jerome [1] https://dvcs.w3.org/hg/audio/raw-file/tip/webaudio/specification.html [2] http://en.wikipedia.org/wiki/Gimbal_lock
Received on Tuesday, 13 March 2012 14:00:51 UTC