After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 352796 - fine grained sound device selection
fine grained sound device selection
Status: RESOLVED DUPLICATE of bug 355658
Product: ekiga
Classification: Applications
Component: general
2.0.x
Other All
: Low enhancement
: ---
Assigned To: Ekiga maintainers
Ekiga maintainers
Depends on:
Blocks:
 
 
Reported: 2006-08-25 07:22 UTC by Łukasz Stelmach
Modified: 2007-07-23 07:54 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14



Description Łukasz Stelmach 2006-08-25 07:22:56 UTC
Multi-channel soundcards are quite popular today. Not only quite advanced SB cards support several stereo channels but even cheap built-in on-board devices do. It should be possible to choose not only soundcard but also specific ALSA pcm devivce with standard ALSA syntax, e.g. cards.pcm.rear:1. This means sound is routed to to the rear speakers of the second soundcard. When I don't watch a movie rear speakers are not used so I can plug my headphones there and use ekiga while still listening to music through the front speakers. 

Other information:
Comment 1 Ben Jencks 2007-07-06 19:50:57 UTC
I'd like to second this, for a slightly different reason. I'm using a bluetooth headset, with the newer, fully userspace `headsetd' from http://bluetooth-alsa.sourceforge.net/build.html

As documented on that page, Ekiga doesn't let you choose from all ALSA pcm devices available, so I'm using the hack provided that adds "Bluetooth Headset" to the menu, corresponding to ALSA device 'headset'. If I could simply enter the device, this would be unnecessary.
Comment 2 Ben Jencks 2007-07-23 07:51:55 UTC
This is the same as Bug #355658, which has more information in it.
Comment 3 Snark 2007-07-23 07:54:22 UTC
Ok, then marking as duplicate.

*** This bug has been marked as a duplicate of 355658 ***