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 628045 - No sound while a file is played.
No sound while a file is played.
Status: RESOLVED INVALID
Product: GStreamer
Classification: Platform
Component: dont know
0.10.30
Other Linux
: Normal normal
: NONE
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2010-08-26 16:45 UTC by Markus Elfring
Modified: 2010-09-16 12:55 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Markus Elfring 2010-08-26 16:45:18 UTC
The following command does not generate any sounds at the moment while the program "mplayer" works as expected with the specified audio (Vorbis) file.

elfring@Sonne:~> LANG=C gst-launch-0.10 playbin uri=file:///usr/share/sounds/gnome/default/alerts/bark.ogg
Setting pipeline to PAUSED ...
Pipeline is PREROLLING ...
Pipeline is PREROLLED ...
Setting pipeline to PLAYING ...
New clock: GstPulseSinkClock
Got EOS from element "playbin0".
Execution ended after 647739106 ns.
Setting pipeline to PAUSED ...
Setting pipeline to READY ...
Setting pipeline to NULL ...
Freeing pipeline ...
Comment 1 Stefan Sauer (gstreamer, gtkdoc dev) 2010-09-15 15:29:19 UTC
Does any of this works:

gst-launch-0.10 audiotestsrc ! autoaudiosink
gst-launch-0.10 audiotestsrc ! alsasink

gst-launch-0.10 playbin2
uri=file:///usr/share/sounds/gnome/default/alerts/bark.ogg

gst-launch-0.10 playbin2
uri=file:///usr/share/sounds/gnome/default/alerts/bark.ogg audio-sink=alsasink


what sink have you choosen in gstreamer-properties?
Comment 2 Markus Elfring 2010-09-15 17:53:55 UTC
(In reply to comment #1)
> Does any of this works:

I do not hear any sounds from the suggested commands.


> what sink have you choosen in gstreamer-properties?

The application "Multimedia Systems Selector" shows the following audio settings.
Default Output
   Plugin: Autodetect

Default Input
   Plugin: ALSA
Comment 3 Stefan Sauer (gstreamer, gtkdoc dev) 2010-09-15 20:31:13 UTC
Then it is not the file. In case you run PulseAudio you could check the volumes there (gnome-volume-control or pavucontrol).
Comment 4 Markus Elfring 2010-09-15 21:24:43 UTC
(In reply to comment #3)

I'm stumped, I am so sorry.

The command "gnome-volume-control" uncovered that the volume was unexpectedly muted.
Comment 5 Tim-Philipp Müller 2010-09-15 21:35:59 UTC
Great, thanks for the update.
Comment 6 Markus Elfring 2010-09-16 08:28:21 UTC
By the way:
There are also other open issues involved.

1. I need to revive the sound driver by the command "rcalsasound restart" at the moment. Otherwise, the device seems to be busy or already allocated.
2. The sound settings must be occasionally unmuted by the programs "gnome-volume-control" and/or "kmix" a couple of times.
Comment 7 Stefan Sauer (gstreamer, gtkdoc dev) 2010-09-16 12:55:04 UTC
I believe there stability issues in your driver. A userspace app should not be able to kill your sound-driver. When the driver is realoaded it seems to load the mixer defaults and those seem to be muted. Check if you can save unmoted defaults with e.g. alsamixer.

It would be good to continue the discussion e.g. with the alsa people, as I think its not related to gstreamer (luckily) :)