W3C home > Mailing lists > Public > public-audio@w3.org > July to September 2013

[web-audio-api] There should be notification when the destination output changed (#27)

From: Olivier Thereaux <notifications@github.com>
Date: Wed, 11 Sep 2013 07:27:44 -0700
To: WebAudio/web-audio-api <web-audio-api@noreply.github.com>
Message-ID: <WebAudio/web-audio-api/issues/27@github.com>
> Originally reported on W3C Bugzilla [ISSUE-21345](https://www.w3.org/Bugs/Public/show_bug.cgi?id=21345) Wed, 20 Mar 2013 06:04:34 GMT
> Reported by Wei James
> Assigned to 

When changing accessories, the max number of channels can change, which has an impact on virtualization and 3D positioning, you wouldn't use the same settings and algorithms when switching from headset to speakers.

In case you are switching from local speakers to headphones, you are really sending the same stream to the same low-level driver, and the switch is typically handled in the audio codec hardware. You will have continuity of the playback by construction, and the only time you'd need to reconfigure the graph is if you have any sort of 3D positioning.
But if the new output is HDMI, Bluetooth A2DP, USB, there will be a delay and volume ramps when switching, and it'd be perfectly acceptable to stop and reconfigure without any impact to user experience. It'd be interesting to capture this difference in the notification.

---
Reply to this email directly or view it on GitHub:
https://github.com/WebAudio/web-audio-api/issues/27
Received on Wednesday, 11 September 2013 14:28:12 UTC

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