On Thu, May 24, 2012 at 1:47 PM, Martin Ziegler
zieg...@email.mathematik.uni-freiburg.de wrote:
mplayer said that the output device was pulse:
AO: [pulse]
Wenn I use mplayer with the option -ao alsa everything works fine. Thanks!
It might be interesting that the version of mplayer in the
tag 674145 important
retitle 674145 mplayer does not stop after playing a file with
pulseaudio backend, breaks playback of multiple files
stop
On Sat, May 26, 2012 at 12:55 AM, Uoti Urpala uoti.urp...@pp1.inet.fi wrote:
On Thu, 2012-05-24 at 13:47 +0200, Martin Ziegler wrote:
mplayer said that
On Thu, 2012-05-24 at 13:47 +0200, Martin Ziegler wrote:
mplayer said that the output device was pulse:
AO: [pulse]
Wenn I use mplayer with the option -ao alsa everything
works fine. Thanks!
This is most likely a Pulseaudio bug then.
It might be interesting that the version of mplayer
mplayer said that the output device was pulse:
AO: [pulse]
Wenn I use mplayer with the option -ao alsa everything
works fine. Thanks!
It might be interesting that the version of mplayer in the
package mplayer does not hit this bug. It works also with
the option -ao pulse.
Regards,
Martin
Package: mplayer2
Version: 2.0-554-gf63dbad-1
Severity: normal
mplayer AUDIOFILE
plays the file, but does not exit at the end. When several files are
given in the commandline, mplayer stops playing after the first file
and continues with the next file only after the return key is pressed.
Are you using Pulseaudio output (or ALSA redirected through Pulseaudio)?
My first guess is that you're hitting one of Pulseaudio's numerous bugs,
where it keeps falsely reporting that there's still a significant amount
of unplayed audio left; the player keeps waiting for the audio to finish
6 matches
Mail list logo
