Red Hat Bugzilla – Bug 230069
Ekiga should use the "default" ALSA device
Last modified: 2007-11-30 17:11:58 EST
Description of problem:
I have a system with 2 sound cards:
Card 0: emu10k (SB Live Value)
Card 1: intel8x0 (nForce integrated sound device)
system-config-soundcard creates a /etc/asound.conf like:
#Generated by system-config-soundcard, do not edit by hand
This works fine for card 0, but accessing "plughw:1" (Ekiga does this) causes
alsa to try and open /dev/snd/pcmC1D3p (card 1, device 3) which does not exist.
Setting defaults.pcm.device to 0 manually solves the problem.
I'm not that familiar with the workings of ALSA, but it seems that
defaults.pcm.device is applied to both cards, but is only really relevent to the
default card. Each card should probably have it's own default device setting?
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Set up FC6 on a machine with both an emu10k and intel8x0 card
2. Try opening the "plughw:1" ALSA device
"aplay -D plughw:1 sound-sample.wav" fails to open the device (see attached strace)
Above commandline should successfully open sound card 1.
For some reason, default:1 seems to work, even though plughw:1 does not.
Created attachment 148792 [details]
Strace of aplay attempting to use plughw:1
Aha, I'll check it. Thanks for the report.
It isn't a bug in ALSA. All applications should use the "default" sound device,
not plughw. moved to ekiga.
I don't really understand. If you use the Ekiga configuration druid,
after having selected Alsa as the audio manager (page 6/10), in the
next page you can select, either the "default" or the individual
cards to use for audio input and output device. So the fact of
not using "default" is probably due to the device having been manually
selected at some point, and can be trivially fixed by rerunning the
druid (menu Edit > Configuration Druid), so I don't understand the problem.
If you still think there is a problem with Ekiga internals and not
about the specific configuration, please report this upstream:
- bugzilla.gnome.org, module Ekiga
There is an ekiga developper mailing-list too
For me this work, I can pick either the default as configured at the
Alsa level or the individual cards if I need to override.
The problem is that Ekiga addresses individual devices as "plughw:0",
"plughw:1", etc. when you select them from the drop-down list. It should be
using "default:0", "default:1", etc.
Unfortunately, even though the ALSA people agree with me, the upstream Ekiga
developers are convinced that what they are doing is correct, so there's a bit
of a stalemate situation. :(
Hum, okay. Honnestly I don't think it's worth trying to patch ekiga in our
release, I don't feel like it's a good place to raise/fix problem with upstream
decisions. So I'm tempted to close as WONTFIX,
Ok. Close it as WONTFIX for now. If I get time (seems unlikely in the near
future :( ) I will look at the latest Ekiga code and see if it's still doing the
same thing - if so I'll poke some people upstream. I understand Ekiga is going
to be getting some major reworking done for the next release anyway.
Yeah 3.0 will have an awful lot of changes. Best will be to check again with
Damien when back from vacations,