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 144949 - support for two soundcards
support for two soundcards
Status: RESOLVED DUPLICATE of bug 141449
Product: GStreamer
Classification: Platform
Component: dont know
0.8.2
Other Linux
: Normal minor
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2004-06-24 22:32 UTC by Stefano
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.5/2.6



Description Stefano 2004-06-24 22:32:23 UTC
In gstreamer preference gnome panel enabling support for choiche primary and
secondary audio card. Actually many motherboard had an integrated soundcard in
the  chipset, so if anybody had also another profesional pci soundcard on the
system it  can select primary and secondary audio input/output.
Comment 1 Ronald Bultje 2004-06-24 23:54:17 UTC
Er, and how would applications use that? Applications can only use one sound
card really...

And GNOME Volume Control already detects all sound cards correctly.
Comment 2 Stefano 2004-06-25 01:33:49 UTC
I mean, selection the default gstreamer card output from the list of all
detected soundcards installed on the system instead that manually entering
somthing like:
"alsasink device=plughw:1" in the gnome gstreamer preferences guy. At the moment
isn't very well  
 usable for newbie gnome user and soundcards could be listed in the gui.
Comment 3 Ronald Bultje 2004-06-25 01:56:05 UTC
Oh, that, yes, we have a widget for that but I didn't have time to integrate
that into gstreamer-properties yet. It's in gst-rec (in GStreamer CVS) if you
want to look at it. There's already another bug report in gnome-media that
covers this.
Comment 4 Benjamin Otte (Company) 2004-07-04 14:03:29 UTC
That means it's a duplicate. :)

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