On Tue, 21 Feb 2012, Clemens Ladisch wrote:
> No; it appears that Skype reads the list of devices from the configuration
> file.
OK, it's not a kernel driver, but anyway, skype uses both the kernel
drivers (from /proc) and the alsa config file, and it seems abnormal
that other programs,
Pierre Frenkiel wrote:
> On Tue, 21 Feb 2012, Clemens Ladisch wrote:
>> I don't know how Skype works.
> here are some informations I got from experience:
>- if I link .asoundrc.asoundconf to .asoundrc.headset
> my headset is available is the skype sound devices (and works)
>- if remo
On Tue, 21 Feb 2012, Clemens Ladisch wrote:
> I don't know how Skype works.
here are some informations I got from experience:
- if I link .asoundrc.asoundconf to .asoundrc.headset
my headset is available is the skype sound devices (and works)
- if remove this link, the headset is
Pierre Frenkiel wrote:
> Why does Skype see this device (i.e. it is the the list of
> available output devices), and alsamixer does not?
I don't know how Skype works.
The bluetooth audio device is not an ALSA kernel driver; it's created
by an alsa-lib plugin that goes through the kernel's gen
On Tue, 21 Feb 2012, Clemens Ladisch wrote:
> This file defines a device named "bluetooth".
> I'd guess that Skype has been configure to use that device (if present).
> The other files probably redefine the "default" device.
Sorry, but that doesn't answer my question:
Why does Skype see th
Pierre Frenkiel wrote:
>if I do
> ln -fs .asoundrc.asoundconf.headset .asoundrc.asoundconf
>the sound is sent to my bluetooth headset only from skype.
>For the other programs, it goes to the SB-live card.
>
> Here is the content of .asoundrc.headset
>
hi everybody,
( I already sent this question to the debian-users list, but got no
explanation. I hope to get one with this more specialized list...)
I'm trying to use a bluetooth headset, and curiously, it works only
for Skype(at least for the speaker, not for the microphone),
and not for any oth
