After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 346998 - Ogg Vorbis internet streams stop on song change
Ogg Vorbis internet streams stop on song change
Status: RESOLVED DUPLICATE of bug 320984
Product: GStreamer
Classification: Platform
Component: gst-plugins-base
0.10.8
Other Linux
: Normal normal
: NONE
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-07-08 18:47 UTC by Erik Grinaker
Modified: 2006-07-10 10:56 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14


Description Erik Grinaker 2006-07-08 18:47:15 UTC 
While playing a Ogg Vorbis internet radio stream (pick any on www.icecast.org), GStreamer will stop playing whenever the track changes. This used to work in older versions - I believe 0.10.4 was good.

You can test it with this pipeline (excuse the music choice):

gst-launch-0.10 gnomevfssrc location=http://la.campus.ltu.se:8000/stream.ogg.m3u ! decodebin ! audioconvert ! alsasink
Comment 1 Tim-Philipp Müller 2006-07-09 19:00:34 UTC 
This looks very much like bug #320984 (I'm surprised it worked before though - if it did maybe something has changed server-side?)


*** This bug has been marked as a duplicate of 320984 ***
Comment 2 Erik Grinaker 2006-07-10 07:21:30 UTC 
I'm certain this worked fine in older versions, and it's not related to server changes.

I'm working on an Internet radio player (Sputnik) based on GStreamer, and I use my own server with Ogg Vorbis streams for testing while developing it. Song changes weren't a problem until recently, I've played multi-song Vorbis streams for more than 8 hours continuously without problems.

I can try to downgrade to an older version and track down where the problem first appeared.
Comment 3 Tim-Philipp Müller 2006-07-10 10:56:26 UTC 
Grabbing the stream with wget and analyzing it with oggzinfo does suggest that it contains multiple chains though (which has never worked reliably in 0.10, see the other bug report)

> I can try to downgrade to an older version and track down where the problem
> first appeared.

That would be great :)