GNOME Bugzilla – Bug 345449
[icydemux] Internet radio hangs when connecting to radio.livesets.com
Last modified: 2006-11-04 10:22:41 UTC
Streaming just hangs when I connect to livesets radio [1]. Why and how it does this is not really sure to me, but it seems only the playerengine hangs, not the UI. The only odd thing about the stream seems to be this: ICY Info: StreamTitle='[LIVE]Smartek - Elements of Techno (Kleve, Ger)[LIVE]';StreamUrl='http://www.peterechoplex.com'; Is this a banshee issue or a gstreamer issue? [1]: http://www.livesets.com
It's a gstreamer issue: ruben@tokyo:~ $ gst-launch-0.10 playbin uri=http://stream.livesets.com:8000/Setting pipeline to PAUSED ... Pipeline is PREROLLING ... And that's where it hangs.
With gstreamer cvs (roughly up to date), this has id3demux recursively typefinding the contents as id3.
Culprit seems to be icydemux clearing buffer stamps of the first buffer somehow, which leads id3demux to not read the tags and typefind the input buffer again, hence the recursion. Needs fixing in both I guess.
Should be fixed now: 2006-09-14 Tim-Philipp Müller <tim at centricular dot net> * gst/icydemux/gsticydemux.c: (gst_icydemux_reset), (gst_icydemux_typefind_or_forward): * gst/icydemux/gsticydemux.h: When we merge/collect multiple incoming buffers for typefinding purposes, keep an initial 0 offset on the first outgoing buffer as well (otherwise id3demux won't work right). Fixes #345449. Also Make buffer metadata writable before setting buffer caps. * tests/check/elements/icydemux.c: (typefind_succeed), (cleanup_icydemux), (push_data), (GST_START_TEST), (icydemux_suite): Small test case for the above. 2006-09-14 Tim-Philipp Müller <tim at centricular dot net> * gst/apetag/gsttagdemux.c: (gst_tag_demux_chain_parse_tag): * gst/id3demux/gstid3demux.c: (gst_id3demux_chain): Don't interpret a first buffer with an offset of NONE as 'from the middle of the stream', but only a first buffer that has a valid buffer offset that's non-zero (see #345449). (you can still get recursion if upstream puts a valid non-zero offset on the first buffer though, but that would be an upstream element bug then IMHO).
*** Bug 370401 has been marked as a duplicate of this bug. ***