21345 2013-03-20 06:04:34 +0000 There should be notification when the destination output changed 2014-10-28 17:17:24 +0000 1 1 1 Unclassified AudioWG Web Audio API unspecified PC Windows NT CLOSED WONTFIX P2 normal TBD 1 james.wei crogers ehsan public-audio oldest_to_newest 84707 0 james.wei 2013-03-20 06:04:34 +0000 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. 85763 1 james.wei 2013-04-09 01:03:38 +0000 one proposal: enum OutputType { “speakers”, “headset” }; interface AudioDestinationChangeEvent : Event { readonly attribute double float sampleRate; readonly attribute unsigned long maxChannelCount readonly attribute OutputType outputType; }; 85767 2 ehsan 2013-04-09 01:46:10 +0000 Why would we expose the sample rate in this way? Also, I assume that you're planning to extend OutputType in the future, right? 85852 3 james.wei 2013-04-10 08:29:02 +0000 (In reply to comment #2) > Why would we expose the sample rate in this way? > > Also, I assume that you're planning to extend OutputType in the future, > right? yes, OutputType should be extendable. for sample rate, do you have any idea for output change? 86191 4 ehsan 2013-04-15 01:45:12 +0000 Why should the web application change about the sampling rate change? Is it not reasonable to expect the implementation to handle any resampling if needed? 113931 5 olivier.thereaux 2014-10-28 17:14:33 +0000 Web Audio API issues have been migrated to Github. See https://github.com/WebAudio/web-audio-api/issues 114077 6 olivier.thereaux 2014-10-28 17:17:24 +0000 Closing. See https://github.com/WebAudio/web-audio-api/issues for up to date list of issues for the Web Audio API.