Le mercredi 19 septembre 2007 à 16:14 +0200, Sebastian Hesselbarth a écrit : > >> : Perhaps you should try on their mailing list... The problem is > probably > >> : related to pulseaudio itself... > >> > >> Maybe. > >> > >> The main question probably is whether ekiga ALSA plugin > >> supports reading and using the .asoundrc configuration at all. Because > > > >Of course, it is transparent. As long as you use the Default device, it > >will use whatever configuration comes with the Default device. > > > >> so far it seems ekiga tries to access the ALSA device directly > >> no matter what is written in .asoundrc. Using "ls -ltu" I have found > >> that ekiga does not reread .asoundrc even when "Detect devices" > >> button in the Audio Devices dialog is pressed. > > > >It is transparent, and handled by libasound. > > First of all, sorry for breaking the reply chain but I just subscribed > to the list. > > Unfortunately, it seems that pwlib's device discovery does not use > asoundrc. I tried ekiga today on a machine without any audio device but > pulseaudio and alsa redirection to pa. > > Same result: ekiga does not find any audio devices but > aplay/gstreamer/.. do. >
As I mentionned earlier in this thread, if you remap the default device in .asoundrc and use it in Ekiga, it works. -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ NOVACOM : http://www.novacom.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:[EMAIL PROTECTED] _______________________________________________ ekiga-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/ekiga-list
