- From: Jan Deinhard <jan.deinhard@gmail.com>
- Date: Wed, 13 Mar 2013 20:02:55 +0100
- To: "public-audio@w3.org" <public-audio@w3.org>
- Message-ID: <CAG=22kdhdd6ePHOOiMKifRvKYVQQ3RFkLQrqOSy76-kHdxsaKg@mail.gmail.com>
2013/3/13 Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com> > > Sounds like a reasonable approach to me. We want the audio output to be >> uninterrupted if the audio settings change during playback. Especially >> in cases where a user just plugs in headphones. But there are also >> situations where we can switch to a new context if we would get a >> notification for changed settings. During playback we could set a flag >> and create a new context as soon as possible. For example when the user >> stops playback. >> > > 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. > -Pierre > > You are right. Though I was referring to the situation I described in my original message. A MacBook connected to a Cinema Display. Initial audio output device is the display. Plugging in headphones to the MacBook causes a switch to the internal audio device which has a different sample rate. Jan
Received on Wednesday, 13 March 2013 19:04:12 UTC