GNOME Bugzilla – Bug 447022
trying to play internet radio station gives "couldn't start playback (null)"
Last modified: 2008-07-13 11:36:41 UTC
Please describe the problem: Currently with the latest Rhythmbox on Ubuntu Gutsy, I often can't play internet radio stations. When I open Rhythmbox and double click an internet radio station I added myself, nothing happens. If I press the "play" button after I've double-clicked a station, I often get the error message "Can't start playback (null)". However, the radio stations which are added to Rhythmbox by default, the three HBR1.com radio stations and Virgin Radio Classic Rock, always work all the time. The strange thing is that if I play one of the default radio station first, and then switch to one of the radio stations I added myself (http://www.etn.fm/ and http://www.di.fm/, which don't work if I try to play them first) they then do work. I'm reasonably sure that the problems related to playing back streams from DI.fm and ETN.fm are not related to the streams themselves, but to Rhythmbox, because Banshee has no problems playing them back. Steps to reproduce: Actual results: Expected results: Does this happen every time? Other information: Functionality for internet radio is terribly bugged in Rhythmbox, making it unusable for an internet radio user like me. This is not the only problem, there's also bugs like bug #374242 and bug #396409 which are many interruptions and buffering during internet radio playback. Please fix the functionality concerning internet radio, because currently I have to ditch Rhythmbox, which has the potential to be good application, for Banshee, which does a better job at internet radio.
Today I tried playing some internet radio streams again with the latest Rhythmbox of Ubuntu's development branch. I tried adding the AAC stream of ETN.fm, which gave me the same error message, but the MP3 stream worked fine. I thought that GStreamer shouldn't have a problem with AAC, but I'm not sure whether this is caused by Rhythmbox or GStreamer. Because playing back the MP3 stream seemed to work fine, I'm closing this bug. Not sure if I should choose FIXED or OBSOLETE.
Great, thanks for following up on that bug.