GNOME Bugzilla – Bug 355658
"virtual" ALSA devices are not seen on ekiga's list
Last modified: 2010-01-25 09:16:32 UTC
Please describe the problem: Trying to connect ekiga to JACK, a new ALSA device "jackplug" is not visible inside ekiga's list. However, wengophone's list shows it, and in twinkle you can type in the ALSA name yourself. Steps to reproduce: 1. Edit your /etc/asound.conf (I'm on Debian unstable, maybe it's called .asoundrc at your place) like described in http://www.alsa-project.org/alsa-doc/doc-php/asoundrc.php#jackplug 2. Start ekiga. The "jackplug" device is not on the ALSA device list. 3. In wengophone (Classic or NG) it's available, and "aplay -D jackplug myfile" works, too. Actual results: Expected results: Device should be listed and available. Does this happen every time? Yes. Other information: Workaround: edit your ALSA configuration like http://alsa.opensrc.org/JACKPlugin so that your "default" device is routed to JACK. Then choose "default" in ekiga's list (always available when using ALSA).
Does libalsa make those virtual devices visible in the list of devices ? Because as far as I know, the ALSA plugin asks for the list to libalsa, so it won't invent them if they aren't there.
In fact, wengophone uses portaudio, not alsa directly. Here is the licence of portaudio : http://www.portaudio.com/license.html
If portaudio is free enough, we could have one plugin for portaudio. If portaudio knows that a newly defined device is available, it can only know that from 2 sources : - libasound: then we need to add support for that ASAP - reading .asoundrc: then we close the bug report because it sucks to implement it that way I have never found a way to have the list of redefined devices through libasound. But I'm sure it should be possible (perhaps in recent releases?). I just checked and it is possible using : snd_config_search( snd_config, "pcm", &topNode ) See http://portaudio.com/trac/browser/portaudio/branches/v19-devel/pa_linux_alsa/pa_linux_alsa.c?rev=972 Any taker for this bug?
I did have a look at wengophone's sources, which contain portaudio's : - portaudio has an alsa subsystem, which seems to detect devices like pwlib's ALSA plugin ; - portaudio has a jack subsystem, which I didn't study. So the question is : does wengophone really detect your jack device as-alsa, or does it detect it directly as-jack ?
I think wengophone detects the alsa-jack device as-alsa, because it's showing the name "jackplug" that I "invented" in my asound.conf.
Isn't this the same issue as in bug 340270?
More or less. Let's say that if we fix this bug report, you shouldn't need anymore to type anything in the combo box proposed in the other bug.
*** Bug 401373 has been marked as a duplicate of this bug. ***
*** Bug 352796 has been marked as a duplicate of this bug. ***
I see that sadly this issue seems to have died on the vine. Is there something else in the works to deal with this problem or has it just been put aside for now?
Arrived here from Bug #87702 in pwlib (ubuntu) Been trying to use Ekiga with my bluetooth headset (Acer voip phone). Cannot select headset in audio input/output settings even though it is apparently paired ok. This is on hardy heron.
Is this bug still valid?
(In reply to comment #12) > Is this bug still valid? Valid in what sense? It's certainly valid in as much as ekiga still does not make available virtual alsa devices. Maybe ekiga should just switch from using alsa to using pulseaudio anyway. Not sure how applicable that is or not.
gstreamer are generaly lagfree except creating the pipelines themselves
Eh, if you have gstreamer expertise, we have experimental gstreamer support, but it's not working correctly yet... any help would be appreciated!
Closing as notgnome and pushing upstream (ptlib), http://sourceforge.net/tracker/?func=detail&atid=989748&aid=2714555&group_id=204472, please comment on that page from now on.
Any suggestion on how to fix?
Yes : make the gstreamer code work.
From the corresponding upstream bug: "Due to limited time and restrictions on our access to the precise platform you are using, it would greatly assist us if you could work the problem and provide patches to fix the issue. Do you think you are able to do that?" Please help if you can.