GNOME Bugzilla – Bug 135101
shoutcast playback unreliable
Last modified: 2005-06-30 15:10:07 UTC
can not reliable play shoutcast streams using the following command line: $ gst-launch-0.7 gnomevfssrc=location=http://foobar ! mad ! osssink This works about 30% of the time. The remainder of the time audio plays for just a fraction of a second, then stops. Several stations were tried, including: http://64.236.34.97:80/stream/1040 http://64.62.253.214:8926 One thing I noticed, is that when it does not play, the number of iterations reported when gst-launch closes is much here than when it does play. For example, the following worked: $ gst-launch-0.7 gnomevfssrc location=http://64.62.253.214:8926 ! mad ! osssink RUNNING pipeline ... Caught interrupt. Execution ended after 9 iterations (sum 3002827000 ns, average 333647444 ns, min 8210000 ns, max 533901000 ns). The following did not work: $ gst-launch-0.7 gnomevfssrc location=http://64.62.253.214:8926 ! mad ! osssink RUNNING pipeline ... Caught interrupt. Execution ended after 72 iterations (sum 1729820000 ns, average 24025277 ns, min 7049000 ns, max 107753000 ns).
I can't reproduce this.
me neither, marking NEEDINFO
> I could reproduce it with http://64.236.34.97:80/stream/1040 just now. > > Any sort of debugging or other information which would be helpful? run the launch line with --gst-debug-level=5, and attach the output.
Created attachment 26288 [details] gst-debug-level=5 output $gst-launch-0.7 --gst-debug-level=5 gnomevfssrc location=http://64.236.34.97:80/stream/1040 ! mad ! osssink &> gst-log.txt
moving this from needinfo to open as we now have info. Could be that latest fixes has solved this so dcharno please test with latest gstreamer release if possible.
http://64.236.34.97:80/stream/1040 => works (a AOL streaming service) http://64.62.253.214:8926 => this hosts does not respond/is offline tried with alsasink, using provided gst-launch syntax, totem and rhythmbox (latest CVS for gstreamer and totem, latest release for rhythmbox)