Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#40726 - [mpd] Stuttering and sluggish playback in 0.18.11-1
Attached to Project:
Arch Linux
Opened by Sam (samlockart) - Friday, 06 June 2014, 03:26 GMT
Last edited by Gaetan Bisson (vesath) - Monday, 09 June 2014, 08:01 GMT
Opened by Sam (samlockart) - Friday, 06 June 2014, 03:26 GMT
Last edited by Gaetan Bisson (vesath) - Monday, 09 June 2014, 08:01 GMT
|
DetailsDescription:
After updating to 0.18.11-1 on my 3.14.5-1-ARCH desktop I suffered from occasional stuttering during playback (regardless of file format/location), resuming playback took 3 - 5 seconds. Changing to mpd-git from the AUR has fixed all of my problems and playback is perfect once again. I'm not certain what caused this. Additional info: * Package version = mpd 0.18.11-1 * Depends on: libao 1.2.0-1 ffmpeg 1:2.2.3-1 libmodplug 0.8.8.5-1 audiofile 0.3.6-2 libshout 1:2.3.1-2 libmad 0.15.1b-7 curl 7.37.0-1 faad2 2.7-4 sqlite 3.8.4.3-2 jack 0.124.1-1 wavpack 4.70.0-2 avahi 0.6.31-12 libid3tag 0.15.1b-8 yajl 2.1.0-1 libmpdclient 2.9-1 Steps to reproduce: Not certain. I same issues were experienced through both ALSA/Pulse, difference file formats. S.M.A.R.T. reports a healthy drive and changing to the git version seems to have cleared up any issues. |
This task depends upon
- identify the upstream commit that fixed this issue (there have been less than 40 commits since 0.18.11, so bisecting should be fast), then convince me to include it in our package;
- convince upstream to make a new release.
Anyhow, since you are the one affected by this bug, it would be nice if you could identify the upstream commit that fixed it, if any, or report the bug upstream otherwise.
My mistake.