- From: Martin Thomson <martin.thomson@gmail.com>
- Date: Fri, 22 Feb 2013 15:02:17 -0800
- To: "stephane.cazeaux@orange.com" <stephane.cazeaux@orange.com>
- Cc: "public-media-capture@w3.org" <public-media-capture@w3.org>
This is something that I raised a while back. On windows, it's possible to select default (general) audio devices and different default communication audio devices. This produced interesting effects. I believe that Chromium was using the communication device for input. There is no easy answer for implementations. That said, I believe that it's an implementation issue. On 22 February 2013 09:42, <stephane.cazeaux@orange.com> wrote: > Hi all, > > > > The thread below is discussing of an issue about how is selected the output > device for a received media stream. Unless I am wrong, this is currently a > browser decision, which is especially an issue for audio where a user may > have several output devices. > > > > What do people on this list think about developing standards for media > output device selection? > > > > Stephane. > > > > De : stephane.cazeaux@orange.com [mailto:stephane.cazeaux@orange.com] > Envoyé : vendredi 8 février 2013 23:02 > À : public-webrtc@w3.org > Objet : RE: Audio device selection > > > > > > > > De : Harald Alvestrand [mailto:harald@alvestrand.no] > Envoyé : vendredi 8 février 2013 22:28 > À : CAZEAUX Stephane OLNC/OLPS > Cc : public-webrtc@w3.org > Objet : Re: Audio device selection > > > > On 02/08/2013 08:53 PM, stephane.cazeaux@orange.com wrote: > > Hi all > > > > I am wondering if something is not missing in audio device selection for > some communication case. > > > Well, first off, this is a media capture matter, so should go to > public-media-capture@w3.org.... > > [SC] I am not sure of that. Here I am dealing with how is rendered the audio > received from the network. > > > > Regarding to audio device selection, the media capture scenario document > (https://dvcs.w3.org/hg/dap/raw-file/tip/media-stream-capture/scenarios.html) > talks of the case where the user selects between a microphone device plugged > to the audio jack, or the microphone of a webcam. But there is another > common case: the user has a microphone in the audio jack and a usb headset > (speaker+microphone). To me, in this case: > > - When the user selects the microphone device in the audio jack, he > will most likely want to hear the remote party in the speakers of the > computer > > - When the user selects the USB headset device, he will most likely > want to hear the remote party in the headset > > > "Most likely" isn't the same as "always". > > [SC] I did not say « always » > > > I regularly use a headset with a broken microphone; in those cases, I need > to select the camera microphone (because that's the one that gives the best > sound). > > [SC] Well, on my side, I am always using usb devices, and expect to be able > to switch between a usb headset and usb speaker phone > > > I think it is better that the API present those as independent choices. > > [SC] That’s exactly what my « most likely » meant: let the user choose. But > I don’t see in the specification how the choice will be given to the user. > > > > > > But with some tests based on Chrome 24, the audio is always played through > the OS default audio device, even if I select a usb headset as audio capture > device (which is of course not the OS default device). > > AFAIK, this is explained by the fact that on one hand the media capture API > enables the selection of the capture device only. On the other hand, audio > HTML tag uses the default rendering device of the system. I could not find > any document talking of audio rendering device selection. > > > Chrome 24 doesn't have input microphone selection yet. > > Please don't judge the specification by the state of the implementation. > > [SC] That was not my intent, but just an illustration. > > > > > > Any thought about this? Did I miss something? > > > > > > Stéphane. > > > > > >
Received on Friday, 22 February 2013 23:02:45 UTC