Closed GoogleCodeExporter closed 8 years ago
This: Using audio device: PulseAudio
Comes from your local configuration. Open up gnome-mplayer, select edit
preferences and change the audio device to something else. The default value is
"Default" as it comes shipped in my source package. You will also not that it
is using mplayer software volume control, which means that it is not trying to
talk to pulse, it is using an internal volume value. If it is hanging without
opening a file, something else is wrong.
Original comment by kdeko...@gmail.com
on 13 Feb 2012 at 2:18
tracked down the source of the problem.
i'd clean-built a prereq, gmtk (http://gmtk.googlecode.com/svn/trunk), with
config of:
./configure --with-alsa=yes --with-pulseaudio=no
make
make install
apparently, something hung around from prior install that'd had
"--with-pulseaudio=yes".
a complete uninstall, and manual delete of any/all *gmtk* files/dirs on disk,
then a clean re-install, as above seems to have done the trick -- in that it no
longer hangs.
In addition, changing GNOME Mplayer prefs -> Audio Ouput -> ALSA, although it
has no effect on the hand at all, does clear up the output at launch.
now,
gnome-mplayer --reallyverbose
GNOME MPlayer v1.0.6b1
gmtk v1.0.6b1
Running in single instance mode
Running with GIO support
Using audio device: ALSA
Using MPlayer Software Volume control
Using match: type='signal',interface='com.gnome.mplayer'
Using match: type='signal',interface='org.gnome.SettingsDaemon'
Using match: type='signal',interface='org.gnome.SettingsDaemon.MediaKeys'
Proxy connections and Command connected
and, back to normal operation.
thanks.
Original comment by pgnet.dev
on 13 Feb 2012 at 6:01
Original comment by kdeko...@gmail.com
on 20 Feb 2012 at 2:20
Original issue reported on code.google.com by
pgnet.dev
on 9 Feb 2012 at 7:02