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 142211 - alsasink broken due to mixer device
alsasink broken due to mixer device
Status: RESOLVED FIXED
Product: GStreamer
Classification: Platform
Component: gst-plugins
git master
Other Linux
: Normal normal
: 0.8.2
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2004-05-09 18:12 UTC by Arwed v. Merkatz
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Arwed v. Merkatz 2004-05-09 18:12:02 UTC 
With cvs of 2004-05-09:
gst-launch-0.8 filesrc location="test.mkv" ! matroskademux name=demux ! { queue
! spider ! xvimagesink } { demux. ! queue ! spider ! audioscale !
audio/x-raw-int,rate=48000 ! alsasink device=dsp1 }

RUNNING pipeline ...
ALSA lib control.c:654:(snd_ctl_open_noupdate) Invalid CTL dsp1
ERROR            alsa(21563) gstalsamixer.c(153):gst_alsa_mixer_open:<alsasink0>
Cannot attach mixer to sound device `dsp1'.
ERROR: pipeline doesn't want to play.
Caught interrupt.

Relevant part of my ~/.asoundrc:
pcm.dsp1 {
  type hw
  card 0
  device 1
}
Comment 1 Ronald Bultje 2004-05-09 18:49:24 UTC 
OK, so this mixer part might cause some regressions. How do I get the relevant
mixer for a given device then? (And why are mixer-device-to-attach-to and
sound-device not the same?)
Comment 2 Arwed v. Merkatz 2004-05-10 07:41:37 UTC 
Ok, this seems to be a problem of the alsa configuration, adding this to my
.asoundrc fixes it:
ctl.dsp1 {
  type hw
  card 0
}
Comment 3 Ronald Bultje 2004-05-16 20:45:14 UTC 
Added some code to make sure that even though we don't attach to a mixer sanely,
we still continue (like OSS). Mixer-less devicing is allowed by ALSA.
Comment 4 Thomas Vander Stichele 2004-06-03 13:14:50 UTC 
ronald, is this fixed ? if so, resolve as such.  if not, change milestone to
HEAD.  thanks.
Comment 5 Ronald Bultje 2004-06-03 14:16:37 UTC 
Yes this is fixed.