Bug 56577 - playback of an audio file in mplayer2 with ao=pulse does not finish
Summary: playback of an audio file in mplayer2 with ao=pulse does not finish
Status: RESOLVED MOVED
Alias: None
Product: PulseAudio
Classification: Unclassified
Component: core (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: pulseaudio-bugs
QA Contact: pulseaudio-bugs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-10-30 09:36 UTC by purification
Modified: 2018-07-30 10:31 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:


Attachments

Description purification 2012-10-30 09:36:45 UTC
After switching mplayer2 config from ao=alsa to ao=pulse, sometimes playback of an audio file would stop at the end of file, without ever ending or going to next track. Manually seeking forward or back unfreezes it but it happens all the time.

pulseaudio version: 2.0-6
mplayer2 version: 2.0-554-gf63dbad-1+b1

Packages are from debian sid amd64
Comment 1 Paul Menzel 2012-10-30 09:42:34 UTC
1. The upstream MPlayer2 developer brought this discussion up on the mailing list [1][2].

2. A workaround was applied to MPlayer 2 upstream [2].

3. In the Debian BTS, this issue is assigned to MPlayer 2 and was assigned the number #674145 [4].

[1] http://lists.freedesktop.org/archives/pulseaudio-discuss/2012-July/thread.html#14302
[2] http://lists.freedesktop.org/archives/pulseaudio-discuss/2012-August/thread.html
    (Search for Uoti.)
[3] http://git.mplayer2.org/mplayer2/commit/?id=de435ed56eafee040fe286151e51b94c144badc7
[4] http://bugs.debian.org/674145
Comment 2 GitLab Migration User 2018-07-30 10:31:41 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/487.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.