Hi, I logged into a full gnome-session to try out your example. First, I started by using test-speakers to confirm that my sound had become muted since pulseaudio started. Then I installed the following to run your example: gstreamer0.10-base-plugins gstreamer0.10-good-plugins gstreamer0.10-good gstreamer0.10-ugly-plugins gstreamer0.10-ugly Then I tried your examples. I'm afraid I did not get the same behaviour as you. My system did not play any audiable sound for either alsasink or the pulsesink. Only when I had done "alsactl init 0", could I hear the mp3 given to gstreamer. Note I can also repeat the same test but instead of doing "alsactl init 0", I can get the sound back by going into alsamixer unmuting the master channel and raising the volume on the master channel (where it is set to 0). Thanks, Frank On 4 June 2012 21:27, Ajay Garg <ajaygargnsit at gmail.com> wrote: > Hi all. > > I am not sure, if you are facing the same problem which bugged me a week > back (though I am unsure if this is a problem, or a feature), but here it > goes like this :: > > > I noted that for the very first time, the pulseaudio sink volume is muted. > So, I noted that when I did something like > ????????????????????? "gst-launch filesrc location=/path/to/mp3" ! mad ! > alsasink" > I could hear the sound. > > However, when I did > ????????????????????? "gst-launch filesrc location=/path/to/mp3 ! mad ! > pulsesink" > I could not hear the sound. > > > So, I launched "pavucontrol", unmuted the sound in "Output Devices" section, > and volia . I could hear sounds from thereon using "pulsesink" (and > "alsasink:, of course). > > > Is this the same case as yours..? > > > Regards, > Ajay > > On Mon, Jun 4, 2012 at 10:53 PM, Frank Wilson <fajwilson at gmail.com> wrote: >> >> Hi, >> >> I have noticed that the master channel volume is set to zero and muted >> when I login to gnome3 on my arch linux vm. >> >> After looking at various things such as storing and restoring alsa >> settings, I determined the volume settings get changed when pulseaudio >> starts. >> >> To fully isolate the cause I did a test with a bare non-graphical >> login (no gnome session, no login manager, no other sound program). >> >> Here is the session log: >> >> [frank at flint ~]$ date >> Mon Jun ?4 18:03:26 BST 2012 >> [frank at flint ~]$ alsactl init 0 # reset my card, just to be sure >> Found hardware: "ICH" "SigmaTel STAC9700,83,84" "AC97a:83847600" >> "0x8086" "0x0000" >> Hardware is initialized using a generic method >> [frank at flint ~]$ speaker-test >> >> <<<<< CAN HEAR SOUND >>>>> >> >> [frank at flint ~]$ amixer -c0 > amixer.org >> [frank at flint ~]$ pulseaudio --start -vvvvv >> I: [pulseaudio] main.c: Daemon startup successful. >> [frank at flint ~]$ speaker-test >> >> <<<<< CANNOT HEAR SOUND! >>>> >> >> [frank at flint ~]$ amixer -c0 > amixer.pulse >> >> I attach amixer.org, amixer.pulse and pulse_syslog.log.gz (the >> relevant portion of my syslog file, where pulseaudio has logged its >> stuff). >> >> Could anybody explain what is causing the problem and how I should go >> about fixing it? >> >> Thanks, >> >> Frank >> >> _______________________________________________ >> pulseaudio-discuss mailing list >> pulseaudio-discuss at lists.freedesktop.org >> http://lists.freedesktop.org/mailman/listinfo/pulseaudio-discuss >> > > > _______________________________________________ > pulseaudio-discuss mailing list > pulseaudio-discuss at lists.freedesktop.org > http://lists.freedesktop.org/mailman/listinfo/pulseaudio-discuss >
