Community Packages

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!
Tasklist

FS#31572 - [deadbeef] 0.5.5-2 fails to play mms://

Attached to Project: Community Packages
Opened by Dmitry V. Luciv (dluciv) - Sunday, 16 September 2012, 10:28 GMT
Last edited by Lukas Fleischer (lfleischer) - Friday, 21 September 2012, 06:10 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Lukas Fleischer (lfleischer)
Architecture i686
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

Fails to play mms:// streams. Just goes to next playlist item.

This can be probably related to specifics of building for Arch:
* deadbeef-devel-git from AUR behaves similarly;
* binary package (0.5.5-1) from deadbeef's oficial site works well.



Additional info:
* package version: 0.5.5-2

Steps to reproduce:
* try for exanple: mms://live.rfn.ru/radiorussia
This task depends upon

Closed by  Lukas Fleischer (lfleischer)
Friday, 21 September 2012, 06:10 GMT
Reason for closing:  Upstream
Additional comments about closing:  See last comment.
Comment by Alexey Yakovenko (waker) - Sunday, 16 September 2012, 19:50 GMT
this is caused by ffmpeg update to 0.11, which has serious changes in the API, and deadbeef 0.5.5 can't be made compatible with it.
deadbeef in git is not compatible either. to make things more difficult, ffmpeg-0.11 has removed the API for implementing custom URLprotocols, so it's not possible to hook-up deadbeef's mms plugin to ffmpeg WMA codec. it should still be possible to use ffmpeg's internal mms support, but that is still not implemented in deadbeef.

the official build on the deadbeef website is statically linked to the correct version of ffmpeg.

i don't see any way to fix this on package maintainer side, so perhaps you should just close the bug as "wontfix".

Loading...