New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ogg streams not playing #1299

Closed
vasyugan opened this Issue Oct 4, 2015 · 5 comments

Comments

4 participants
@vasyugan

vasyugan commented Oct 4, 2015

In Mopidy 1.1.x, Ogg audio streams are not playing at all. In Mopidy 1.0.x they play just fine.

This is one stream I tried:

http://dradio-ogg-dlf-l.akacast.akamaistream.net/7/629/135496/v1/gnl.akacast.akamaistream.net/dradio_ogg_dlf_l

This is all I find in the log file:

2015-10-04 14:52:18,425 INFO [1028:StreamBackend-9] urllib3.connectionpool: Starting new HTTP connection (1): dradio-ogg-dlf-l.akacast.akamaistream.net

Meanwhile CPU usage shoots up, and any attempt to play another file or stream or podcast after trying to play the ogg stream also fails until I restart mopidy.

The stream itself plays fine with gst-launch playbin uri=http://dradio-ogg-dlf-l.akacast.akamaistream.net/7/629/135496/v1/gnl.akacast.akamaistream.net/dradio_ogg_dlf_l so it's no a gstreamer issue

as noted above, downgrading to 1.0.x fixes this (and a number of other issues, which are also broken in 1.1.x currenly making it virtually unusable for me)

@adamcik adamcik added the C-bug label Oct 4, 2015

@adamcik

This comment has been minimized.

Member

adamcik commented Oct 4, 2015

https://github.com/mopidy/mopidy/blob/develop/mopidy/stream/actor.py#L126 incorrectly catches 'application/ogg' MIMEs so we trigger the playlist handling path. More fallout from our playlist handling changes.

We should add a if scan_result.playable: return uri to that code.

@adamcik adamcik added this to the v1.1.2 - Bugfixes milestone Oct 4, 2015

@jodal jodal self-assigned this Oct 4, 2015

@jodal

This comment has been minimized.

Member

jodal commented Oct 4, 2015

Fixed in release-1.1 branch by PR #1300.

@jodal jodal closed this Oct 4, 2015

@vasyugan

This comment has been minimized.

vasyugan commented Oct 5, 2015

Thanks! Looking forward to a released fix. For now I have gone back to 1.0.x, because there are just too many essential features which have stopped working altogether in 1.1.x, presumably all for the same reason (playlists not working from musicbox webclient, Ogg not playing, tunein.com stations not playing).

I use mopidy primarily as a podcast and webradio player, which due to these bugs is currently mostly impossible. Is 1.1.x a development branch? If so, maybe separate stable & development package repositories would make sense

@kingosticks

This comment has been minimized.

Member

kingosticks commented Oct 5, 2015

You are free to install directly from git. It's well documented.
On 5 Oct 2015 11:12, "vasyugan" notifications@github.com wrote:

Thanks! Looking forward to a released fix. For now I have gone back to
1.0.x, because there are just too many essential features which have
stopped working altogether in 1.1.x, presumably all for the same reason
(playlists not working from musicbox webclient, Ogg not playing,
tunein.com stations not playing).

I use mopidy primarily as a podcast and webradio player, which due to
these bugs is currently mostly impossible. Is 1.1.x a development branch?
If so, maybe separate stable & development package repositories would make
sense


Reply to this email directly or view it on GitHub
#1299 (comment).

@adamcik

This comment has been minimized.

Member

adamcik commented Oct 10, 2015

We try and keep the branch develop usable, and our releases even more so. 1.1.x does indeed have more issues that we would like related to the playlist handling. Which we sadly have had to rush as it was blocking migration to GStreamer 1.0 which we need to get done ASAP or our Debian packages get kicked out of the repos :(

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment